Fibery MCP connector
Connect Fibery to Elaichi and Claude, ChatGPT, Cursor or any MCP client can search your spaces, read and update features, bugs and documents, and change states, all as you, with every call logged.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
50 tools
How to connect
How to connect Fibery to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Fibery once
-
Open Connections, choose Add connection, and pick Fibery.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Fibery. Fibery's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Fibery MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Fibery MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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.
Fibery MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Connect Fibery to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
Use cases
What teams do with Fibery through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Product
Catch the roadmap up after a customer call
Tell the agent what the customer asked for and it creates or updates the feature in Fibery, links it to the account, and sets the right state.
-
Engineering
Move bugs through states from the terminal
From Cursor, ask which bugs are assigned to you, set one to In Progress, and append a note to the bug's document without leaving your editor.
-
Design
Keep specs current in Fibery documents
Paste decisions from a review and the agent appends them to the spec document in Fibery, so the written spec matches what was agreed.
-
Customer Success
Turn feedback into linked Fibery requests
Drop in a support thread and the agent creates a feedback entity, adds it to the right feature's collection, and reports what is already planned.
-
Research
Summarize interview notes into insights
Ask for the themes across this month's interview documents in Fibery and get a summary with each insight linked back to the entities it came from.
-
Leadership
Ask how the quarter's initiatives are tracking
Query the initiatives view in Fibery in plain language and get a status rundown, with the entities that have no owner or have stalled called out.
Try asking
- “Summarize bugs moved to Done in the Platform space this week”
- “Create a feature in the Roadmap database from these customer notes”
- “Which initiatives in the Q3 view have no owner yet?”
Compare
Elaichi vs Zapier MCP vs Composio for Fibery
All three can connect Fibery 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.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Fibery tools | Allow or restrict single Fibery 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 Fibery 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Fibery tools for your AI agents
50 tools are ready to call through Elaichi's MCP endpoint the moment you connect Fibery, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Fibery builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Fibery gets you
6 screens from the product, each doing one job for your Fibery account.
The agent
Ask Fibery questions in plain language.
Get answers from live features, bugs and documents, not from a stale export.
- entities
- documents
- databases
- spaces
Ask Elaichi to work across your apps.
Summarize bugs moved to Done in the Platform space this week
Create a feature in the Roadmap database from these customer notes
Which initiatives in the Q3 view have no owner yet?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint reaches Fibery from every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
50 Fibery tools, ready without writing code.
Search, query, create, update and delete entities, documents, databases and spaces.
- Schema
- Schema detailed
- Get me
- Query
ElaichiToolsToolboxes
Every team gets its own Fibery toolbox.
Product, engineering and design each work with the Fibery tools scoped to them.
- Product
- Engineering
- Design
- Customer Success
ElaichiToolboxesShared connections
Teammates use Fibery without seeing a credential.
One person connects Fibery, shares it, and the table shows exactly who has access.
- Product
- Engineering
- Design
- Customer Success
ElaichiConnectionsAudit log
Every Fibery change is logged with a name.
See when, who, what happened and which entity, in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule turns Fibery updates into a digest.
Fetch new entities, group them, draft a digest, approve it, then post back to Fibery.
Fibery digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch entities
Fibery
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Fibery
Queued
Collections and dashboards
Fibery health, computed with no model involved.
Four metrics, 14 days of entities created and a team breakdown, refreshed on a schedule.
Fibery health
Refreshed 4 minutes ago · every 15 minutes · from the entities collection
Entities
1,284 ↓ 12%
Documents
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Entities created
Last 14 days
By team
Share of activity
Product 34%
Engineering 27%
Design 21%
Customer Success 18%
FAQ
Frequently asked questions
How do I connect Fibery to Claude?
In Elaichi, choose Fibery and sign in to your Fibery workspace over OAuth, the same way you sign in to Fibery normally; there is no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and Fibery is available in the conversation from then on.
Does Fibery work with ChatGPT and Cursor as well as Claude?
Yes. Once Fibery is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. You connect Fibery once and every client picks it up.
What can an AI agent actually do with my Fibery data?
An agent can search and query entities across your Fibery spaces, read the data behind a view, open and edit documents, create or update features, bugs and other entities, set their states, and link them together. It can also create or rename databases and spaces if your role allows. Short, concrete asks such as "set this bug to Done" work better than long paragraphs.
Does connecting Fibery give the AI every space in my workspace?
No. The agent works inside the Fibery access of the person who signed in, so it sees only the spaces, databases and entities that person can already see. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what Fibery itself grants.
Can I stop an agent from deleting or changing things in Fibery?
Yes. Restrictions in Elaichi work per action, so you can allow searching and reading in Fibery while blocking deleting entities, removing databases or deleting spaces. A restricted action is never advertised to Claude, ChatGPT or Cursor, so no prompt can reach it.
What happens to a Fibery connection when someone leaves?
Offboarding a person in Elaichi ends their access to Fibery through every client at once. A Fibery connection they shared keeps working for everyone else on the team. If you want Fibery gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the Fibery MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Fibery 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 Fibery?
Yes. Both let Claude, ChatGPT or Cursor use Fibery. 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 Fibery call.
How is Elaichi different from Composio for Fibery?
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 Fibery: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Fibery in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.