# Manufact MCP connector

The Manufact connector brings your organizations, servers, deployments and server analytics to Claude, ChatGPT, Cursor and the Elaichi Agent, so your team can deploy, check logs and read usage inside their own Manufact access.

Source: https://elaichi.ai/connectors/manufact/

## Facts

| | |
| --- | --- |
| Application | Manufact |
| Category | Application Development |
| AI tools | 22 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Manufact builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | manufact.com/contact |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Manufact is connected

- Show build logs for the latest billing server deployment
- Which tools on the docs server got the most requests this week?
- Redeploy the staging server and tell me when it is healthy

## Connect Manufact in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Manufact.
2. Optionally set Share with, then press Connect.
3. Approve it in Manufact. Manufact's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Manufact tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Manufact MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Manufact MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## Manufact MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Manufact to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Manufact tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Manufact through Elaichi

### Ship a deployment and watch the build

Engineering. Ask for a deploy of a server, then follow the build logs and runtime logs in the same conversation. If the build fails, the agent reads back the lines that matter instead of making you dig through the console.

### Find out why a server is throwing errors

Platform. Pull the health summary and the error runtime logs for a Manufact server in one ask. Redeploy or stop the deployment from the same place once you know what went wrong.

### Check deployment logs when a customer reports trouble

Support. When a ticket says a tool stopped responding, ask for the latest deployment of that server and its runtime logs. You get an answer for the customer without waiting on an engineer.

### See which clients and tools people actually use

Product. Ask for the client breakdown and tool breakdown on any Manufact server to learn whether traffic comes from Claude, Cursor or elsewhere, and which tools carry the load.

### Get a weekly picture of usage by country

Leadership. Request the analytics summary and requests by country across your Manufact organizations, and have the agent turn it into a short readout for the Monday meeting.

### Invite a teammate and tidy pending invitations

Operations. Invite a new member to a Manufact organization, list who has not accepted yet, and cancel invitations that went to the wrong address, all without opening the admin screen.

## Elaichi vs Zapier MCP vs Composio for Manufact

All three can connect Manufact to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Manufact tools | Allow or restrict single Manufact tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Manufact call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Manufact to Claude?

Connect Manufact in Elaichi first: you are sent to Manufact's own sign-in page, approve access, and come back. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude asks you to sign in to Elaichi and Manufact is available in your chats.

### Does Manufact work with ChatGPT and Cursor as well as Claude?

Yes. Once Manufact is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Manufact once and every client picks it up.

### What can an AI agent actually do with my Manufact data?

With Manufact connected, an agent can list your organizations and servers, start a deploy or redeploy, stop a deployment, and read build logs and runtime logs. It can also pull server analytics such as health, requests by country, and which clients and tools are getting traffic, and it can invite or cancel organization members. Short, specific asks like "show the error logs for the docs server" work better than long sentences.

### Does connecting Manufact give the AI access to every organization and server?

No. Access follows the person who signed in to Manufact, so the agent sees only the organizations, servers and deployments that person can already see. Elaichi can narrow that further, for example read-only analytics for one team, but it can never widen access beyond what Manufact grants.

### Can my team share one Manufact connection?

Yes. One person connects Manufact in Elaichi and shares the connection with a team, and nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who redeployed a server or read its logs.

### Can I stop an agent from stopping deployments or changing servers in Manufact?

Yes. Restrictions in Elaichi work per action, so you can allow reading Manufact logs and analytics while blocking deploy, redeploy, stop deployment or server updates. A restricted action is never advertised to the AI client at all, so no prompt can reach it.

### What happens to a Manufact connection when someone leaves?

Offboarding that person in Elaichi ends their Manufact access at once, in every client they used. A shared Manufact connection keeps working for everyone else on the team. If you need to remove Manufact entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

### Does the Manufact MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Manufact is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Manufact?

Yes. Both let Claude, ChatGPT or Cursor use Manufact. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Manufact call.

### How is Elaichi different from Composio for Manufact?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Manufact: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 22 Manufact tools

Every tool below is callable through https://api.elaichi.ai/mcp once Manufact is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List organizations** (List). List the organizations the authenticated user can access.
- **Get organization stats** (Get). Summary stats for an organization. Servers, deployments, tool calls, sessions.
- **Invite org member** (Invite). Send an invitation to join an organization with a specified role.
- **List org invitations** (List). List pending invitations for an organization.
- **Cancel org invitation** (Cancel). Cancel a pending organization invitation.
- **List servers** (List). List MCP servers in an organization as compact rows.
- **Get server** (Get). Core details for one MCP server, including its deploy configuration.
- **Update server** (Update). Update a server's deploy configuration or metadata, optionally redeploying immediately.
- **Get server domain** (Get). The main custom domain and verification status for a server.
- **List deployments** (List). List deployments as compact rows, filterable by server and status.
- **Get deployment** (Get). Full details for one deployment, including the git commit and MCP URL.
- **Deploy** (Action). Deploy a GitHub repository to Manufact Cloud. Creates a server or redeploys an existing one.
- **Redeploy** (Action). Trigger a new deployment of an existing server.
- **Stop deployment** (Stop). Stop a running deployment, taking it offline.
- **Get deployment runtime logs** (Get). Tail runtime logs for a deployment, with optional substring filtering.
- **Get deployment build logs** (Get). Tail build logs for a deployment, or stream an in-flight build by offset.
- **Get server analytics summary** (Get). Requests, sessions, tool calls, errors and latency for the window, with the change against the previous window of the same length
- **Get server analytics client breakdown** (Get). Which MCP clients connect, with sessions and requests per client over time
- **Get server analytics tool breakdown** (Get). Calls per tool, prompt and resource over time
- **Get server analytics health** (Get). Per-tool and per-client error rates, tool-result errors and p50 / p95 / p99 latency
- **Get server analytics requests by country** (Get). Requests and sessions by country
- **Get server analytics error runtime logs** (Get). Runtime logs around an errored request, from the deployment that served it