Manufact MCP server icon

Manufact

by Manufact

HIPAA CompliantSOC2 ReadyISO 27001 Ready
Developer Tools20 tools

Deploy, redeploy, stop and monitor MCP servers on Manufact Cloud from an AI agent. Manufact documents 20 tools; Anthropic's directory lists 18. OAuth sign-in with identity-only scopes.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Manufact via MCP

https://mcp.manufact.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Manufact Tools & Capabilities (20)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • No application scopes exist. The RFC 9728 resource descriptor at https://mcp.manufact.com/.well-known/oauth-protected-resource/mcp and the authorization server at https://cloud.manufact.com/api/auth both advertise exactly openid, profile, email and offline_access on 2026-08-22. Nothing at the OAuth grant separates reading a deployment from stopping one, so the boundary that matters is your Manufact role, not the consent screen.
  • The default role is not narrow. Manufact documents the built-in member role as able to create, update and delete servers, deployments, API keys, domains and GitHub integrations. The narrower alternative — custom roles — is an Enterprise-plan feature.
  • Anthropic's directory under-lists by two writes. update_server and redeploy are documented by Manufact and absent from the directory entry we hold, dated 2026-08-16.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so all parameter detail on this page comes from Manufact's documentation rather than from the server's own tools/list reply.
  • The manufact://info resource is documented but unverified. resources/list returned 401 alongside every other RPC, so we could not confirm the resource surface. Manufact's directory entry does record has_mcp_app: true.
  • get_server_tool_breakdown has a fixed window. Manufact documents it as the last 24 hours with hourly buckets and no time parameters, unlike get_server_client_breakdown, which accepts 24h, 7d, 30d or 90d. Longer-range tool analysis is not available through this tool.
  • Analytics retention is plan-gated. Manufact's pricing lists 7 days on Free, 30 days on Hobby, one year on Startup and unlimited on Enterprise. The analytics tools cannot return data the plan has already dropped.
  • Free-plan traffic stops rather than overflows. Manufact documents the gateway returning 402 Payment Required on Free once the monthly credit grant is used, with no pay-as-you-go overage.
  • This is not the mcp-use docs server. Manufact also publishes an unauthenticated documentation server at https://docs.mcp-use.com/mcp, and the mcp-use GitHub organization contains a separate repository named mcp-server that serves docs and build guidance to coding agents. Neither is the connector on this page.

Frequently asked questions

Yes. Manufact documents stop_deployment as taking a running deployment offline, and marks it destructive so clients may ask you to confirm. Recovery is a separate call — Manufact's own documentation says bring the server back with redeploy. Nothing in the OAuth grant prevents an agent from reaching it.

Manufact documents 20 and Anthropic's directory lists 18. The two missing from the directory are update_server, which changes deploy configuration, and redeploy, which triggers a new deployment. Both write. Manufact's own MCP page states plainly that each of the 20 tools has its own reference page, so treat 20 as the real figure.

Four, and none of them scope anything. Manufact's RFC 9728 descriptor and its authorization server both advertise openid, profile, email and offline_access on 2026-08-22. Those are OpenID identity claims plus refresh-token issuance. There is no scope that grants reading a deployment without also granting stopping one.

Yes, through one tool. Manufact documents invite_org_member as sending an email invitation to join an organization at a role you specify. That is the connector's only outbound path to a third party. Manufact states you can only invite at or below your own role, so a member can invite members only.

The role allows it, though no delete tool is listed. Manufact's permissions documentation states plainly that the built-in member role is not read-only and can create, update and delete servers, deployments, API keys and domains. Narrower access requires an Enterprise custom role, which Manufact gates behind its Enterprise plan.

Seven days per access token, ninety days per refresh token. Manufact documents both windows and states each refresh extends the ninety-day window. Manufact also automatically grants the offline_access scope so clients receive a refresh token even when they omit it from the authorization request, meaning re-consent is rare.

Gateway telemetry about your own MCP servers. Manufact documents request counts, error counts, average duration, per-client session totals and per-tool call counts. The event log also carries country and client version for each request. In MCP Apps clients these four tools render interactive charts rather than raw JSON.

No, but the free tier is small. Manufact's pricing lists Free at $0 with $5 of monthly credits, 2 projects, 1 team member and 7-day analytics retention. Manufact states the gateway returns 402 Payment Required on Free once monthly credits are exhausted, rather than billing overage.

Sources

Use in Agentman

Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Server Info

Category
Developer Tools
Developer
Manufact
Tools
20
Domain
mcp.manufact.com

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.