Skip to content

CRM

Octapipe MCP connector

Connect Octapipe to Elaichi and Claude, ChatGPT, Cursor, or any MCP client can read and update your Octapipe pipelines, cards, database records, notes, and files inside each person's own access, with every action logged.

  • How it connects. Connects with an API key. 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.

How to connect

How to connect Octapipe to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Octapipe once

  1. Open Connections, choose Add connection, and pick Octapipe.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste an Octapipe API key. One person generates a token in Octapipe and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

octapipe
Octapipe
Affinity
Attio
Clazar
Clio Manage
Close
2

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.

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

Octapipe 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 today. The plugin directory lives at chatgpt.com/plugins.

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

Connect Octapipe 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.

Use cases

What teams do with Octapipe through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Sales

    Catch a pipeline card up after a call

    Tell the agent what happened on the call and it adds a note to the Octapipe pipeline card and updates the matching database record, so nothing waits until the end of the day.

  • Sales

    See what is sitting in each stage

    Ask which cards have been in the same Octapipe pipeline stage for more than two weeks and get the list back, ready to work through before the pipeline review.

  • Support

    Log a customer issue on their record

    When a customer writes in, the agent finds their Octapipe record, adds a note describing the problem, and attaches the file they sent.

  • Operations

    Clean up a database in bulk

    Fix an owner, a region, or a status across hundreds of Octapipe database records in one pass, or export the whole set to check it in a spreadsheet first.

  • Marketing

    Load a batch of new leads at once

    Hand over the attendee list from an event and the agent creates the Octapipe database records in bulk, then opens a pipeline card for the ones worth following up.

  • Leadership

    Get a plain-language read on the pipeline

    Ask how many Octapipe pipeline cards moved this week and which notes were added to the biggest ones, and get an answer in a few sentences instead of clicking through each pipeline.

Try asking

  • “List the Octapipe databases my team writes to most.”
  • “How many records were created in Octapipe last week?”
  • “Export contact records from the Octapipe pipeline database.”

See all 42 Octapipe tools below

Compare

Elaichi vs Zapier MCP vs Composio for Octapipe

All three can connect Octapipe 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 Octapipe, 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 Octapipe tools Allow or restrict single Octapipe 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 Octapipe 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

Octapipe tools for your AI agents

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

See it in Elaichi

What connecting Octapipe gets you

6 screens from the product, each doing one job for your Octapipe account.

The agent

Ask in plain words, read live records.

Three starter prompts pull answers straight from Octapipe databases and records.

  • databases
  • records
  • contacts
  • files

Ask Elaichi to work across your apps.

List the Octapipe databases my team writes to most.

How many records were created in Octapipe last week?

Export contact records from the Octapipe pipeline database.

Also runs in Claude, ChatGPT or Cursor

MCP clients

One Octapipe endpoint for every MCP client.

Claude, ChatGPT and Cursor connect over OAuth, no SDK, no shared key.

ElaichiMCP clients
Claude ChatGPT Cursor

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

Tool catalog

42 Octapipe tools ready without custom code.

Databases, records, bulk operations and files, each listed with its methods.

  • Get single Octapipe database by ID
  • List all Octapipe databases
  • Create a Octapipe database record
  • Get single Octapipe database record by ID
ElaichiTools
Tool Action Description
Get single Octapipe database by ID Get Get a single Octapipe database by its UUID. Returns: uuid, name, description, icon, custom_fields, created_at, updated_at, and deleted_at. Required: id.
List all Octapipe databases List List all Octapipe databases with optional filtering, search, and ordering. Returns: uuid, name, description, icon, custom_fields, created_at, updated_at, and deleted_at for each database record.
Create a Octapipe database record Create Create a new record in an octapipe database. Returns the created record including uuid, name, custom_fields_values, created_at, updated_at, database_uuid, owner_user, and creator_user. Required: database_uuid, name, custom_fields_values.
Get single Octapipe database record by ID Get Get a single octapipe database record by its uuid. Returns uuid, name, custom_fields_values, created_at, updated_at, deleted_at, database_uuid, owner_user, and creator_user. Required: database_uuid, id.
List all Octapipe database records List List all records in an octapipe database with optional filtering, search, and sorting. Returns uuid, name, custom_fields_values, created_at, updated_at, database_uuid, owner_user, and creator_user per record. Required: database_uuid. Max 15 items per page.

Toolboxes

Every team gets its own Octapipe toolbox.

Toolboxes are scoped per team, so Sales and Support see different tools.

  • Sales
  • Marketing
  • Customer Success
  • Support
ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

Octapipe · deals and contact records

Octapipe starter 18 Mar 4, 2026

Marketing toolbox

Octapipe · campaign lists and segments

— 9 Mar 2, 2026

Customer Success toolbox

Octapipe · account records and renewals

— 24 Feb 27, 2026

Support toolbox

Octapipe · ticket records and case files

Octapipe starter 6 Feb 19, 2026

Revenue Operations toolbox

Octapipe · bulk updates and exports

— 31 Jan 30, 2026

Finance toolbox

Octapipe · invoice records and attached files

— 12 Jan 22, 2026

Shared connections

Teammates use Octapipe without touching a credential.

See who connected each account and how many teams and members share it.

  • Sales EMEA
  • Sales AMER
  • Marketing
  • Support
ElaichiConnections
Connection Scope Status Access
OC

Octapipe (Sales EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
OC

Octapipe (Sales AMER)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
OC

Octapipe (Marketing)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
OC

Octapipe (Support)

Connected by Tyler Reed

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

Octapipe (Customer Success)

Connected by Ryan Hayes

Personal • Active Not shared
OC

Octapipe (RevOps)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Answer who changed which Octapipe record.

Every call is logged with time, actor, action, type and resource.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Octapipe Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Octapipe Databases Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Octapipe Databases List Toolbox

Launching 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 fires, Octapipe work gets done.

Records are fetched, grouped, drafted into a digest, approved, then posted back.

Octapipe digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch databases

    Octapipe

    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 Michael Brennan

    Approve
  6. Post the digest

    Octapipe

    Queued

Collections and dashboards

Octapipe numbers arrive before anyone asks.

Four metrics, 14 days of records created, split by team, refreshed on schedule.

Octapipe health

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

Live

Databases

1,284 ↓ 12%

Records

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Databases created

Last 14 days

By team

Share of activity

Sales EMEA 34%

Sales AMER 27%

Marketing 21%

Support 18%

FAQ

Frequently asked questions

How do I connect Octapipe to Claude?

Connect Octapipe in Elaichi first: pick Octapipe from the catalog and paste in the API key from your Octapipe settings, which is the only sign-in step. 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. Claude asks you to sign in to Elaichi once and Octapipe is available.

Does Octapipe work with ChatGPT and Cursor as well as Claude?

Yes. Once Octapipe 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 Octapipe once and every client you use picks it up.

What can an AI agent actually do with my Octapipe data?

An agent connected to Octapipe can look up pipelines and pipeline cards, find and update database records one at a time or in bulk, add notes and files to a record, send notifications, and export a database when you need it in a spreadsheet. In practice that means asking for the cards stuck in a stage, adding a note after a call, or loading a list of new leads. Because Octapipe has a lot of actions, short concrete asks like "add a note to the Acme card" work better than long paragraphs.

Does connecting Octapipe give the AI access to every database and pipeline?

No. Every call to Octapipe runs with the access of the person who signed in, so the agent sees the same Octapipe databases, pipelines, and records that person can already open. Elaichi can narrow that further for a team, for example read only or no deletes, but it can never widen it beyond what Octapipe itself allows that person.

Can my team share one Octapipe connection?

Yes. One person connects Octapipe in Elaichi and shares the connection with a team, and nobody else ever sees or handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every note added or record changed in Octapipe.

Can I stop an agent from deleting or changing things in Octapipe?

Yes. In Elaichi you set restrictions per action, so you can allow reading Octapipe records and adding notes while blocking deletes, bulk updates, or creating pipeline cards. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt, however worded, can reach it.

What happens to a Octapipe connection when someone leaves?

When you offboard someone in Elaichi, their access to Octapipe through every client ends at once. If they had connected Octapipe and shared it with a team, the shared connection keeps working for everyone else. And if you ever want Octapipe gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

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

Yes. Octapipe 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 Octapipe?

Yes. Both let Claude, ChatGPT or Cursor use Octapipe. 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 Octapipe call.

How is Elaichi different from Composio for Octapipe?

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 Octapipe: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Octapipe in front of your team

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

Works with
Claude ChatGPT Cursor 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.