Skip to content

Fibery MCP connector

Connect Fibery to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot 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.

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

Summarize bugs moved to Done in the Platform space this week

Working in Fibery with Elaichi

  • Get me
  • Query
  • Search
Ask anything…
Governance / Audit log Last 24 hours
Fibery Search Emily Carter · Claude · 9:41 AM Done
Fibery Query Emily Carter · Claude · 9:41 AM Done
Fibery Get me Emily Carter · Claude · 9:41 AM Done
Fibery Schema Megan Brooks · ChatGPT · 9:38 AM Done
Fibery Schema detailed Ryan Hayes · Cursor · 9:35 AM Done

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

Step by step, for each AI app

Fibery 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.

Fibery 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.

Fibery 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.

Fibery 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.

Fibery 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 Fibery 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 Fibery through Elaichi

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

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

See all 50 Fibery tools →

What connecting Fibery gets you

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

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask Fibery questions in plain language.

Get answers from live features, bugs and documents, not from a stale 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 reaches Fibery from every client.

Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.

ElaichiTools
Tool Action Description
Schema Action Returns the high-level structure of the workspace: all spaces and their databases, without field details.
Schema detailed Action Returns field definitions and enum values for specific databases in YAML format.
Get me Get Returns information about the currently authenticated user.
Query Search Executes a Fibery Query API command against any database. Supports field selection, filtering, sorting, pagination, sub-queries, and aggregation.
Search Search Searches workspace content using BM-25 keyword matching against entity titles, descriptions, document content, and comments.

Tool catalog

50 Fibery tools, ready without writing code.

Search, query, create, update and delete entities, documents, databases and spaces.

ElaichiToolboxes
Name Source template Tools Created

Product toolbox

Fibery · features and roadmap

Fibery starter 18 Mar 4, 2026

Engineering toolbox

Fibery · bugs and sprints

— 9 Mar 2, 2026

Design toolbox

Fibery · specs and prototypes

— 24 Feb 27, 2026

Customer Success toolbox

Fibery · feedback and requests

Fibery starter 6 Feb 19, 2026

Research toolbox

Fibery · interviews and insights

— 31 Jan 30, 2026

Leadership toolbox

Fibery · initiatives and views

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Fibery toolbox.

Product, engineering and design each work with the Fibery tools scoped to them.

ElaichiConnections
Connection Scope Status Access
FI

Fibery (Product)

Connected by Emily Carter

Personal • Active 1 team · 6 members
FI

Fibery (Engineering)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
FI

Fibery (Design)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
FI

Fibery (Customer Success)

Connected by Tyler Reed

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

Fibery (Research)

Connected by Ryan Hayes

Personal • Active Not shared
FI

Fibery (Leadership)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates use Fibery without seeing a credential.

One person connects Fibery, shares it, and the table shows exactly who has access.

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]

Fibery Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Fibery Entities Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Fibery Entities List Toolbox

Audit log

Every Fibery change is logged with a name.

See when, who, what happened and which entity, in an append-only log.

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.

Fibery digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch entities

    Fibery

    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

    Fibery

    Queued

Workflows

A schedule turns Fibery updates into a digest.

Fetch new entities, group them, draft a digest, approve it, then post back to Fibery.

Fibery health

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

Live

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%

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.

Why connect Fibery's MCP server through Elaichi

Fibery builds and runs this MCP server. Elaichi sits in front of it, so Fibery'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 Fibery's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Fibery's tools at the same Elaichi address as every other connected app. Nobody adds Fibery'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 Fibery 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 Fibery's server. By default, a tool Fibery 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 Fibery

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

    the.fibery.io/@public/User_Guide/Guide/Contact-Support

Why run a vendor's MCP server through Elaichi →

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Fibery, 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 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 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.

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.

Questions, answered

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, Microsoft Copilot, 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 my team share one Fibery connection?

Yes. One person connects Fibery in Elaichi and shares it with a team, and nobody else ever handles a Fibery credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every change in Fibery.

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 restricting deleting entities, removing databases or deleting spaces. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.

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