GAIA Logo
PricingDocs
GAIA Logo
  1. Home
  2. Marketplace
  3. Capabilities
66a32476-8781-471f-b263-0f24dcb06646 Icon

Manufact

Manage and deploy custom MCP's

Category
Capabilities
Aryan
Created by
Aryan
Users
0
Published
about 2 months ago

What you can do with GAIA + Manufact

GAIA connects to Manufact via MCP (Model Context Protocol) and exposes every action as a natural-language command. Tell GAIA what you want and it handles the rest, automatically.

  • Deploy new MCP servers directly from your command
  • Monitor organization member invitations and access
  • Retrieve real-time runtime logs for active deployments
  • Update server configurations without manual intervention
  • Stop or redeploy services based on performance metrics

Available Tools (20)

List Organizations

List organizations the authenticated user can access. Returns minimal rows (id, name, slug, role). This is the source of truth for `organizationId`, which every other tool in this server requires. Use get_organization_stats for counts and list_organization_members for the member roster.

Get Organization Stats

Get summary stats for an organization: server count, deployment count, gateway tool-call count, and distinct session count. Does not return the server roster — use list_servers for that.

Invite Org Member

Send an invitation to join an organization with a specified role.

List Org Invitations

List pending invitations for an organization.

Cancel Org Invitation

Cancel a pending invitation.

List Servers

List MCP servers in an organization as compact rows (id, slug, name, status, tags). Uses native offset pagination. This is the source of truth for `serverId`; use sort and pagination to inspect the roster. Use get_server for full details including repo, get_server_domain for the main domain, and list_deployments (pass serverId) for history.

Get Server

Get core details for one MCP server (id, slug, name, description, tags, status, latestDeploymentStatus, activeDeploymentId, repoFullName, productionBranch, deploymentCount). Does not include the full deployment history, domains, or internal provider config — use list_deployments (pass serverId) and get_server_domain for those.

Update Server

Update an existing server's deploy configuration (start command, build command, port, Dockerfile path, root dir) and/or metadata (name, description, tags, production branch). Deploy-config fields are merged into the server's existing config — only the fields you pass are changed, the rest are preserved. Config changes do not take effect until the next deployment, so pass `redeploy: true` to trigger one immediately (or call the `redeploy` tool afterwards). Common use: fix a broken start command (e.g. set `startCommand` to a uvicorn ASGI command for a Python MCP server) and redeploy.

Get Server Domain

Get the main custom domain and verification status for a server (domain, verified, status, sslStatus, cnameTarget, verificationErrors). Note: the main server domain lives on the server — preview domains live on individual deployments.

List Deployments

List deployments as compact rows (id, name, status, serverId, gitBranch, createdAt). Paginated server-side; pass `serverId` to scope to a single server's deployments and optional `status` to filter. This is the source of truth for `deploymentId`; filter by `status` (e.g. 'failed') to narrow down when the user describes a deployment rather than naming it. Use get_deployment for details, get_deployment_build_logs/get_deployment_runtime_logs for logs.

Get Deployment

Get full details for one deployment: core fields (id, status, serverId, domain, port, timestamps, error, mcpUrl), git commit info, and source config (repo, branch, rootDir, runtime, buildCommand, startCommand). Use get_deployment_build_logs / get_deployment_runtime_logs for log streams.

Redeploy

Trigger a new deployment of an existing Cloud server by serverId. Use this only when the user identified a specific existing Cloud server. For deploying a GitHub repo or the current project, use deploy instead.

Deploy

Deploy a GitHub repository to Manufact Cloud. Use this when the user asks to deploy the current repo/project. Before calling, infer repoFullName from the local git remote when possible. The tool checks whether the repo is already connected to a Cloud server in the organization: if yes, it redeploys that server; if no, it creates a new GitHub-backed server and starts the initial deployment. This tool does not accept serverId; use redeploy for a known existing server.

Stop Deployment

Stop a running deployment. Takes the deployment offline; to bring the server back up, call the redeploy tool to trigger a new deployment for an existing server.

Get Deployment Runtime Logs

Get runtime logs for a deployment. Defaults to the most recent 100 lines — pass `lines` (1-5000) to change the tail size. Pass `query` to filter the fetched tail to lines containing a substring (case-insensitive) — useful for finding specific errors or messages without pulling huge tails.

Get Deployment Build Logs

Get build logs for a deployment. Defaults to the last 100 lines — pass `lines` (1-5000) to change the tail size, or pass `offset` (character-offset pagination) to resume streaming an in-flight build from a previous call's `nextOffset`. `lines` takes precedence over `offset` if both are set.

Get Observability Overview

Observability overview for one server: totalEvents, successEvents, errorEvents, avgDuration (ms), avgRequestSize, avgResponseSize aggregated over a time window. Use list_server_events for the underlying request stream, and get_server_tool_breakdown / get_server_client_breakdown for per-tool and per-client splits.

List Server Events

Gateway request log for a server, cursor-paginated (newest first). Each row includes method, path, status code, duration, client name/version, country, and error details when present. Uses cursor pagination, not offset: call again with cursorTime set to the previous response's nextCursor to page back further in time.

Get Server Client Breakdown

Breakdown of which MCP clients are connecting to a server (clientName, clientVersion, protocol, sessionCount, requestCount) plus a timeline of request counts per client per bucket. Pair with get_server_tool_breakdown to see which tools those clients are calling.

Get Server Tool Breakdown

Breakdown of tool/resource/prompt calls on a server over the last 24 hours, bucketed hourly. Returns aggregated per-method totals with per-bucket counts. Use get_server_client_breakdown for the who, and list_server_events for the raw call stream.

How it works

Set up your Manufact automation in three simple steps, no code required.

  1. 1

    Connect your Manufact account

    Authorize GAIA to access your Manufact organization via the mcp.manufact.com domain.

  2. 2

    Issue plain-English commands

    Tell GAIA to deploy a specific server or check the status of your current organization members.

  3. 3

    GAIA executes the workflow

    GAIA interacts with the Manufact API to manage your deployments and server settings in the background.

Frequently asked questions

Everything you need to know about the GAIA Manufact integration.

Yes, GAIA uses the deploy tool to initiate new server instances based on your specific requirements.



GAIA connects Manufact with your entire stack

Manufact is just one piece of the puzzle. GAIA integrates with 50+ tools across capabilities, communication, productivity, and more, letting you build cross-tool automations in plain English without writing a single line of code.

Browse all integrations
Product
DownloadUse CasesMarketplaceBotsPricingRoadmap
Resources
DocumentationBlogRelease NotesStatusRequest a Feature
Company
AboutManifestoContactBranding
Legal
Terms of UsePrivacy Policy
The Experience Company
Discord IconTwitter IconGithub IconWhatsapp IconYoutube IconLinkedin Icon