Skip to content

Manufact MCP connector

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

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Show build logs for the latest billing server deployment

Working in Manufact with Elaichi

  • List organizations
  • Get organization stats
  • List org invitations
Ask anything…
Governance / Audit log Last 24 hours
Manufact List org invitations Emily Carter · Claude · 9:41 AM Done
Manufact Get organization stats Emily Carter · Claude · 9:41 AM Done
Manufact List organizations Emily Carter · Claude · 9:41 AM Done
Manufact Invite org member Megan Brooks · ChatGPT · 9:38 AM Done
Manufact Cancel org invitation Ryan Hayes · Cursor · 9:35 AM Done

How to connect Manufact to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Manufact MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Manufact MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

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

Manufact MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

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

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

Manufact MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Manufact to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

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

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

What teams do with Manufact through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Manufact is logged.

  • Engineering

    Ship a deployment and watch the build

    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.

  • Platform

    Find out why a server is throwing errors

    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.

  • Support

    Check deployment logs when a customer reports trouble

    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.

  • Product

    See which clients and tools people actually use

    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.

  • Leadership

    Get a weekly picture of usage by country

    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.

  • Operations

    Invite a teammate and tidy pending invitations

    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.

Try asking

  • “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”

See all 22 Manufact tools →

What connecting Manufact gets you

6 screens from Elaichi, each doing one job for your Manufact account.

Elaichi Agent

Ask Elaichi to work across your apps.

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

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about your Manufact servers in plain language.

Deployments, build logs and request counts answered from live Manufact records, not a dashboard export.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint puts Manufact in every client.

Claude, ChatGPT, Cursor and Microsoft Copilot reach Manufact through one governed endpoint, no SDK, no shared API key.

ElaichiTools
Tool Action Description
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.

Tool catalog

22 Manufact tools, ready without writing code.

Servers, deployments, logs, invitations and analytics covered the moment Manufact is connected.

ElaichiToolboxes
Name Source template Tools Created

Platform toolbox

Manufact · servers and deployments

Manufact starter 18 Mar 4, 2026

Engineering toolbox

Manufact · build and runtime logs

— 9 Mar 2, 2026

Support toolbox

Manufact · deployment logs and health

— 24 Feb 27, 2026

Product toolbox

Manufact · tool and client usage

Manufact starter 6 Feb 19, 2026

Admin toolbox

Manufact · members and invitations

— 31 Jan 30, 2026

Leadership toolbox

Manufact · organization stats

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Manufact toolbox.

Platform deploys, Support reads logs, Product sees analytics, each from a toolbox scoped to them.

ElaichiConnections
Connection Scope Status Access
MA

Manufact (Platform)

Connected by Emily Carter

Personal • Active 1 team · 6 members
MA

Manufact (Production)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
MA

Manufact (Staging)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
MA

Manufact (Support)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
MA

Manufact (Product)

Connected by Ryan Hayes

Personal • Active Not shared
MA

Manufact (Admin)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share a Manufact connection, never a credential.

One person connects Manufact, teammates deploy and read logs through it without seeing a secret.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Manufact Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Manufact Servers Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Manufact Servers List Toolbox

Audit log

Every Manufact deploy is on the record.

Who redeployed, who stopped a deployment and when, in an append-only log you can search.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Manufact digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch servers

    Manufact

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Manufact

    Queued

Workflows

A schedule runs the Manufact digest for you.

Error logs are fetched, grouped and drafted into a digest a person approves before it posts.

Manufact health

Refreshed 4 minutes ago · every 15 minutes · from the servers collection

Live

Servers

1,284 ↓ 12%

Deployments

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Servers created

Last 14 days

By team

Share of activity

Platform 34%

Production 27%

Staging 21%

Support 18%

Collections and dashboards

Manufact server health, computed, not asked for.

Requests, errors and deployments over 14 days, refreshed on a schedule with no model involved.

Why connect Manufact's MCP server through Elaichi

Manufact builds and runs this MCP server. Elaichi sits in front of it, so Manufact's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Manufact's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Manufact's tools at the same Elaichi address as every other connected app. Nobody adds Manufact's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own Manufact sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Manufact's server. By default, a tool Manufact does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to Manufact

    Manufact builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Manufact team.

    manufact.com/contact

Why run a vendor's MCP server through Elaichi →

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Manufact, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. 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 Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Manufact tools for your AI agents

22 tools are ready to call through Elaichi's MCP endpoint the moment you connect Manufact, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Manufact builds and runs these tools.

Questions, answered

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, Microsoft Copilot, 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 role, 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 restricting deploy, redeploy, stop deployment or server updates. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.

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, Microsoft Copilot 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, Microsoft Copilot, 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.

Put Manufact in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot