Manufact

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 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.

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

List pending invitations for an organization.

Cancel a pending invitation.

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 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 an existing server's deploy configuration (start command, build command, port, Dockerfile path, root dir), auto-deploy triggers (watch paths, deploy branch patterns, wait for CI), 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 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 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 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.

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.