# Manufact MCP server (/mcp)



Manufact Cloud is itself controllable over MCP. The official **Manufact Cloud MCP server** exposes the platform, organizations, servers, deployments, logs, and observability, as MCP tools, so you can manage everything from Cursor, Claude, or any other MCP client.

```text
https://mcp.manufact.com/mcp
```

## Connecting [#connecting]

Add the server to your client with the standard remote MCP configuration:

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

The transport is Streamable HTTP. Authentication uses **OAuth**: on first connection your client runs the standard MCP OAuth flow and you log in with your Manufact Cloud account. Tools then act with your own permissions, the same role-based access you have in the dashboard.

Access tokens last **7 days** and refresh tokens last **90 days** (each refresh extends the window). Manufact automatically grants the `offline_access` scope so clients receive a refresh token even when they omit it from the authorization request.

## What you can do [#what-you-can-do]

|               | Example prompts                                                                             |
| ------------- | ------------------------------------------------------------------------------------------- |
| **Deploy**    | "Deploy this repo to Manufact Cloud", "Redeploy my-server from the main branch"             |
| **Debug**     | "Why did the latest deployment of my-server fail?", "Show runtime logs filtered for errors" |
| **Monitor**   | "How much traffic did my-server get this week?", "Which clients call it most?"              |
| **Configure** | "Change the start command and redeploy", "Is my custom domain verified?"                    |
| **Team**      | "Invite [jane@example.com](mailto:jane@example.com) to my org as admin"                     |

Each of the 20 tools has its own reference page in the sidebar, grouped by area. Start with [`list_organizations`](/mcp/list-organizations), the entry point for every session.

## Design [#design]

The server follows a **composable, minimal-tool** design: each tool returns a narrow, allowlisted projection, and IDs chain across tools.

```text
list_organizations → organizationId
  → list_servers → serverId
    → list_deployments → deploymentId
      → get_deployment_runtime_logs
```

Agents are expected to chain these small calls rather than receive one giant response. A `manufact://info` resource describes the catalog and this flow, so agents can orient themselves.

## Widgets [#widgets]

The four analytics tools render **interactive widgets** (charts and tables) in clients that support MCP Apps, gateway metrics, event streams, client breakdowns, and tool breakdowns appear as live UI instead of raw JSON.

## Built with mcp-use [#built-with-mcp-use]

The server is built with the [mcp-use framework](https://docs.mcp-use.com) and hosted on Manufact Cloud itself, the same workflow described in the [Dashboard docs](/dashboard) and deployable with the [CLI](/cli).