Manufact Cloud MCP Server

What is Manufact Cloud MCP Server?

The Manufact Cloud MCP server is Manufact's official hosted endpoint for managing Manufact Cloud from an AI client: deploy MCP servers from GitHub, read build and runtime logs, check analytics and manage your organization through MCP tools.

Manufact is the company behind the open-source mcp-use SDK and Manufact Cloud, a hosting platform for MCP servers and MCP Apps with auto-deploys from GitHub, preview deploys, custom domains, a cloud inspector, publishing checks and analytics. The Manufact Cloud MCP server exposes that platform (organizations, servers, deployments, logs and observability) so you can operate it from Cursor, Claude or any other MCP client. It is built with mcp-use and hosted on Manufact Cloud itself.

How to use Manufact Cloud MCP Server?

The endpoint uses the Streamable HTTP transport:

https://mcp.manufact.com/mcp

You need a Manufact Cloud account. Authentication is OAuth: on first connection your client runs the standard MCP OAuth flow and you log in with your Manufact account in the browser. If you are new to Manufact, the browser opens the onboarding wizard so you can pick a first task before returning to the client. Tools then act with your own permissions, the same role-based access you have in the dashboard. No API key or header is needed.

Claude Code

claude mcp add --transport http manufact-cloud https://mcp.manufact.com/mcp

Run /mcp in Claude Code and choose the server to sign in.

Claude Desktop / claude.ai

Add a custom connector in Claude's connector settings and enter https://mcp.manufact.com/mcp as the URL. Claude opens the Manufact sign-in page in your browser when you connect.

Cursor

Manufact documents this standard remote configuration, which goes in ~/.cursor/mcp.json or a project's .cursor/mcp.json:

{
  "mcpServers": {
    "manufact-cloud": {
      "url": "https://mcp.manufact.com/mcp"
    }
  }
}

VS Code

Add it to .vscode/mcp.json:

{
  "servers": {
    "manufact-cloud": {
      "type": "http",
      "url": "https://mcp.manufact.com/mcp"
    }
  }
}

Key features of Manufact Cloud MCP Server

• Official server from Manufact, the team behind the mcp-use framework, hosted on Manufact Cloud.
• OAuth sign-in with your Manufact account; tools use the same role-based access as the dashboard.
• Deploy a GitHub repository to Manufact Cloud, redeploy an existing server or stop a running deployment.
• Read build logs and runtime logs, with substring filtering, to debug failed or misbehaving deployments.
• Server analytics for traffic, clients, tools, health, countries and error logs, using the same data and plan retention as the dashboard's Analytics tab.
• Server configuration and custom domain status checks.
• Organization management, including member invitations.
• Composable, minimal-tool design: each tool returns a narrow projection, and IDs chain from organizations to servers to deployments to logs. A manufact://info resource describes the catalog and this flow.

Use cases of Manufact Cloud MCP Server

Manufact's docs give these as example prompts:

• Deploying from chat: "Deploy this repo to Manufact Cloud" or "Redeploy my-server from the main branch."
• Debugging a release: "Why did the latest deployment of my-server fail?" or "Show runtime logs filtered for errors."
• Monitoring usage: "How much traffic did my-server get this week?" or "Which clients call it most?"
• Changing configuration: "Change the start command and redeploy" or "Is my custom domain verified?"
• Managing the team: "Invite jane@example.com to my org as admin."

A typical agent session starts with list_organizations, which Manufact describes as the entry point for every session, then chains through servers and deployments to the logs it needs.

Troubleshooting Manufact Cloud MCP Server

• The client keeps asking you to sign in: the server requires OAuth. Finish the browser login with your Manufact account; access tokens last 7 days and refresh tokens 90 days, and Manufact grants offline_access automatically so clients receive a refresh token.
• An action is refused: tools run with your dashboard role. Ask an organization admin for the needed role.
• The agent cannot find a server or deployment: start with list_organizations to get the organization ID, then list servers and deployments, as the docs describe.