Claude Manufact connectorWhat Claude can do in your Manufact account.
The Claude Manufact connector exposes 18 tools. 14 read tools look at organizations, servers, deployments, logs and stats; 4 write tools deploy, stop or handle invitations; 0 undocumented. Below: what Claude can run, and what depends on your role.
Verified Trustpilot reviews · AI, automation & growth agency
Your Manufact dashboard, run in plain English
Manufact Cloud hosts the tool servers that assistants like Claude call. With the connector, you ask instead of opening the dashboard: why did this deployment fail, how much traffic did that server get, who's still invited to the team. Claude chains the small lookups it needs on its own and answers.
Figure out a failed deploy. list_deployments finds the latest attempt, get_deployment_build_logs pulls the tail of the build log. If the issue shows up in production, get_deployment_runtime_logs filters runtime logs for the word you want.
Measure a server's usage. get_observability_overview aggregates metrics over a time window, get_server_client_breakdown shows which clients connect, and get_server_tool_breakdown counts calls per tool over the last 24 hours. These analytics tools render charts in clients that support it.
Ship again. deploy deploys a GitHub repository, creating a server or redeploying an existing one.
What the connector won't do: it doesn't get around your role, since every tool acts with your dashboard permissions. The publisher's docs announce two more tools than the sheet lists. And nothing fires on its own, so Claude acts when you ask. For unattended chains of steps, the tools on the Integrations hub do a different job.
Words to know before connecting Manufact
Five terms, explained once.
- Connector
- The bridge you set up once between Claude and a service you already use, so Claude can work with it while answering you.
- Tool
- A named capability the connector opens to Claude. Claude picks what it needs on its own; the directory sheet lists every one.
- Authorization
- The service's own screen where you hand Claude the access it will use. Granted once per person, and revocable.
- Approval
- The confirmation Claude waits for before an action that changes something in an account, shown in the chat at the right moment.
- MCP
- The open standard connectors are built on: it lets an assistant like Claude hold a conversation with an outside service.
Connect the Claude Manufact connector
- 01
Find Manufact in Claude
In Claude, open Customize, then Connectors, and spot Manufact. On a Team or Enterprise workspace, an Owner or Primary Owner enables it for the organization first; each member then connects on their own.
- 02
Start the connection
Click Connect on the Manufact row, then sign in through the window Manufact opens itself. If the link ever breaks, hit Disconnect and connect again from the same row.
- 03
Read the authorization screen
Go through the authorization screen before you accept. It belongs to the service, not to Claude, and it sets what the access covers. You can also take that access back later from the service itself.
Manufact's 18 tools, reads and writes kept apart
Manufact gives Claude 18 tools: 14 that read your account, 4 that change something in it.
Eighteen tools, all described in Manufact's documentation. Names stay in English, as Claude shows them. Manufact designed them to chain: organization, then server, then deployment, then logs.
- 14 read
- 4 write
What Claude reads (14)
14 toolsFourteen tools that look at your Manufact Cloud space without changing it.
get_deployment
Opens the full record of one deployment, including the source Git commit and the published server address. The starting point for knowing what's actually live. Its ID comes from list_deployments.
get_deployment_build_logs
Shows the tail of a deployment's build log, or follows an in-progress build live, chunk by chunk through an offset. The deployment ID comes from list_deployments.
get_deployment_runtime_logs
Pulls a deployment's recent runtime logs, with an optional filter on a piece of text. For understanding what happens once the server is up. You get the raw lines Claude then summarizes.
get_observability_overview
Aggregates a server's gateway metrics over a time window and, in compatible clients, renders them as an interactive chart. Manufact counts it among its four analytics tools that render widgets.
get_organization_stats
Sums up an organization in a few numbers: servers, deployments, tool calls and sessions. A bird's-eye view before digging in. Each figure comes from the organization you pick.
get_server
Returns a server's core details, including its deploy configuration. You point to the server with the ID that list_servers provides. It's the server's identity card, read as is.
get_server_client_breakdown
Shows which assistant clients connect to a server, with session and request counts for each. Rendered as an interactive table where the client supports it.
get_server_domain
Reports a server's main custom domain and its verification status. Useful to see whether the address is live. A quick check on whether the custom address is wired up.
get_server_tool_breakdown
Counts a server's tool, resource and prompt calls over the last 24 hours. You see at a glance what actually gets used. In compatible clients the result shows as a widget rather than raw data.
list_deployments
Lists deployments as compact rows, filterable by server and status. It's what supplies the ID the log tools need. Each row stays short so Claude can scan many at once.
list_org_invitations
Shows the invitations still pending in an organization. Handy for spotting who hasn't joined yet. The list covers the organization you name, and only invitations not yet accepted show up.
list_organizations
Lists the organizations your account can access. Manufact makes it the entry point of every session, because the other tools need the target organization.
list_server_events
Pages through the gateway request log of a server, shown as an interactive stream in compatible clients. Each page leads to the next through a cursor, so long histories stay readable.
list_servers
Lists an organization's servers in compact form, each with the ID the other tools require. Short rows keep long lists readable in the chat.
What Claude changes (4)
4 toolsFour tools that act on your account. No source describes a dedicated confirmation, so the general rule below applies.
cancel_org_invitation
Approval: see the ruleCancels a pending invitation in an organization. Only invitations still pending are in scope, the ones list_org_invitations shows.
deploy
Approval: see the ruleDeploys a GitHub repository to Manufact Cloud: it creates a server if none exists, or redeploys the existing one.
invite_org_member
Approval: see the ruleSends an invitation to join an organization with a specific role.
stop_deployment
Approval: see the ruleStops a running deployment, which takes the server offline.
What Claude asks before acting on Manufact
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. No source describes a dedicated confirmation for deploy, stop_deployment, invite_org_member or cancel_org_invitation.
On Team and Enterprise, workspace owners decide whether a member may let certain actions through without being asked again. They can also limit what Manufact may do for the whole organization, keeping reading open and closing writes for example, with a setting nobody bypasses from their own account. Finally, Claude works with the connected person's rights: what that person can't reach, Claude can't reach either.
Which plans include it
None of the 819 directory sheets shows plan availability. Connector by connector, that information isn't published anywhere: it's a real gap in the catalogue.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens the connector for the organization first. For the current status on your account, the only reference is the Manufact sheet in the official directory, which the button on this page opens.
Where Manufact stops inside Claude
A connector isn't an automation: Claude calls these tools while answering you, and none of them reacts on its own to a failed build or a traffic spike. Only Manufact, the publisher, documents this connector.
The tool list is an observed floor, not a promise: an admin can open capabilities that appear on no public sheet. The directory badge isn't a security audit, and Anthropic notes on every sheet that it doesn't control a publisher's tools. A connected community connector has exactly the same access as any other. Here, the sheet and the docs don't even list the same number of tools. Other connectors are gathered on the Claude connectors page.
How many tools does the Manufact connector expose?
- Claude directory sheet ↗October 2026The sheet lists 18 tools.
- Manufact documentation ↗October 2026The publisher's docs announce 20 tools, two more than the sheet.
What this page followsThere's no telling which text is newer, since neither carries a precise date. This page covers the 18 tools on the sheet, the only list tied to Claude's connector, and flags the gap. Check the directory sheet on your own account for the current list.
Need help connecting Manufact to Claude?
A person reads every message.
