← All integrations

Fibery MCP server

31 operations0 webhooks

Manage Fibery workspace schema, entities, documents, files, views, and paginated change history through the documented HTTP APIs.

Try Fibery with your agent

Connect Fibery, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Fibery on my account, then run one read-only example and show me the result.

Runs once, when you ask

Fibery tools and triggers

Tools are what your agent can do in Fibery through Corsair's MCP server. Triggers are the Fibery events a routine can start from.

Schema

  • Create DatabaseWrite

    Create a Fibery database with its documented fields and metadata

    schema.createDatabase

  • Create EnumWrite

    Create a Fibery enum database for select-field options

    schema.createEnum

  • Create FieldWrite

    Create a primitive or relation field in a Fibery database

    schema.createField

  • Delete DatabaseDestructive

    Delete a Fibery database and optionally its entities and related fields

    schema.deleteDatabase

  • Delete FieldDestructive

    Delete a Fibery field and optionally its stored values

    schema.deleteField

  • Install MixinsWrite

    Install documented Fibery mixins on databases

    schema.installMixins

  • QueryRead-only

    Read Fibery workspace databases, fields, and schema metadata

    schema.query

  • Rename DatabaseWrite

    Rename a Fibery database

    schema.renameDatabase

  • Rename FieldWrite

    Rename a field in a Fibery database

    schema.renameField

  • Set Field MetaWrite

    Set documented metadata on a Fibery database field

    schema.setFieldMeta

Entity

  • CreateWrite

    Create a Fibery entity with primitive and relation field values

    entity.create

  • DeleteDestructive

    Delete a Fibery entity by database and UUID

    entity.delete

Connect Fibery to Claude, ChatGPT or Cursor

  1. 1

    Connect Fibery in Corsair

    Add your Fibery API key or sign in with OAuth once in Corsair. Corsair stores the credential encrypted and makes the Fibery API calls for your agent, so it never goes into a prompt or a config file. Connect Fibery

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Fibery. On a ChatGPT personal plan, connect Fibery here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Fibery's read and write operations run right away and its 6 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/fibery, add the Fibery plugin, and connect with an API key or OAuth. Then call methods like corsair.fibery.api.collection.add() from your app. Corsair stores tokens, and keeps each tenant isolated.

Yes. Fibery supports an API key or OAuth. Use credentials or OAuth scopes that match what you automate. Create them in the Fibery developer console, then paste into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Fibery, GitHub, Notion, Stripe, and the rest. Trigger Fibery from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for manage Fibery workspace schema, entities, documents, files, views, and paginated change history through the documented HTTP APIs. Common builds include sync jobs, admin tooling, and agents that call Fibery APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Fibery API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/fibery in the open repo. When Fibery ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Fibery data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Fibery data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Fibery on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 6 destructive Fibery operations. You can change a link's mode at hub.corsair.dev/me.