# Featurebase MCP connector

Connect Featurebase to Elaichi and Claude, ChatGPT, Cursor and Microsoft Copilot can read your boards, changelogs and comments, draft release notes and update admin workloads, each person signed in as themselves.

Source: https://elaichi.ai/connectors/featurebase/

## Facts

| | |
| --- | --- |
| Application | Featurebase |
| Category | Ticketing |
| AI tools | 171 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Featurebase is connected

- Draft a changelog for the three features we shipped this week
- Which admins are marked away today and who covers their queue?
- Summarize the newest comments on the mobile app board

## Connect Featurebase in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Featurebase.
2. Optionally set Share with, then press Connect.
3. Paste a Featurebase API key. One person generates a token in Featurebase and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Featurebase tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Featurebase MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Featurebase MCP connector for Claude Code

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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`.

## Featurebase MCP connector for ChatGPT

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

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

## Featurebase MCP connector for Cursor

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

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

## Featurebase MCP connector for Microsoft Copilot

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

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

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

## Connect Featurebase to any MCP client

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

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

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Featurebase tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Featurebase through Elaichi

### Draft the changelog from this week's shipped work

Product. Ask for a changelog entry covering the features that went out, review the wording, then publish it to the Featurebase changelog without opening the editor.

### Reply to feedback comments without leaving chat

Support. Pull the newest comments on a board, draft replies in your own voice, and post them back to Featurebase from the same conversation.

### Publish release notes and manage subscribers

Marketing. Publish or unpublish a changelog on the day of launch and add a list of new subscribers in one go so they get the announcement.

### Rebalance assignments when someone is out

Support. See which admins are marked away and why, then update assignment limits and workloads in bulk so nothing waits on an empty desk.

### Read every comment before a renewal call

Customer success. List the comments a customer left across your Featurebase boards and get a summary of what they asked for and what was answered.

### Review the Featurebase audit log on demand

IT. Pull the Featurebase audit log, admin roles and brand settings to answer who changed what, without handing out an admin seat.

## Elaichi vs Zapier MCP vs Composio for Featurebase

All three can connect Featurebase 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. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Featurebase tools | Allow or restrict single Featurebase 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 Featurebase 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Featurebase to Claude?

Connect Featurebase in Elaichi by pasting a Featurebase API key, there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks and Featurebase is ready to use.

### Does Featurebase work with ChatGPT and Cursor as well as Claude?

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

### What can an AI agent actually do with my Featurebase data?

It can read your Featurebase boards, brands and changelogs, list and reply to comments, write a new changelog entry and publish or unpublish it, and add or remove changelog subscribers in bulk. It can also see which admins are away, their roles and workloads, update assignment limits, and pull the Featurebase audit log. Short, concrete asks such as draft a changelog for the new export feature work better than long paragraphs.

### Does connecting Featurebase give the AI access to everything in my workspace?

No. Every call to Featurebase runs with the access of the person who signed in to Elaichi, so an agent only sees the boards, changelogs and admin settings that person can already see. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what the Featurebase API key allows.

### Can my team share one Featurebase connection?

Yes. One person connects Featurebase in Elaichi and shares it with a team, and nobody else ever handles the Featurebase API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every changelog edit or comment.

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

Yes. Restrictions in Elaichi apply per action, so you can restrict deleting a Featurebase changelog or removing subscribers for a role or for one person while leaving reading and drafting open. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Featurebase connection when someone leaves?

Offboarding that person in Elaichi ends their access to Featurebase at once, across Claude, ChatGPT, Cursor and every other client. A Featurebase connection they shared keeps working for everyone else on the team. Disconnecting Featurebase once in Elaichi removes it from every client at the same time.

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

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

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

### How is Elaichi different from Composio for Featurebase?

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

## All 171 Featurebase tools

Every tool below is callable through https://api.elaichi.ai/mcp once Featurebase is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Featurebase admin assignment limits bulk update** (Update). Update an admin assignment limit. Updates the admin capacity mode or paused state. mode can be inherit, custom, or unlimited. custom requires limit. Omitted fields keep their current value. Required: admin_id.
- **Featurebase admin away states bulk update** (Update). Update admin away state. Updates an admin away state. awayReasonId uses a stable managed-reason ID. Omit it to preserve the current reason, or send null to clear the reason. Required: admin_id, enabled.
- **List all Featurebase admin roles** (List). List admin roles. Returns all available admin roles and their permissions. This endpoint returns all roles at once (typically a small list). No pagination is supported. Returns every record in one response: Featurebase does not page this endpoint, so limit and cursor are not supported and are ignored if sent.
- **Featurebase admin workloads bulk update** (Update). Bulk update admin workload state. Atomically updates away state or assignment limits for up to 50 admins. One request performs one operation type. Assignment-limit operations require an explicit paused value. Required: adminIds, operation.
- **List all Featurebase admins** (List). List admins. Returns all admins for your organization. This endpoint returns all admins at once (typically a small list). No pagination is supported. Returns every record in one response: Featurebase does not page this endpoint, so limit and cursor are not supported and are ignored if sent.
- **Get single Featurebase admin by ID** (Get). Get an admin by ID. Retrieves a single admin by their unique identifier. Returns the admin object if found and they belong to your organization. Required: id.
- **List all Featurebase audit logs** (List). List audit logs. Returns a list of audit log events in your organization using cursor-based pagination (newest first).
- **List all Featurebase away reasons** (List). List managed away reasons. Returns active managed away reasons. Set includeArchived=true to include historical reasons. Returns every record in one response: Featurebase does not page this endpoint, so limit and cursor are not supported and are ignored if sent.
- **List all Featurebase boards** (List). List all boards. Returns all boards (post categories) for the authenticated organization. Boards are containers for posts/feedback. Each board can have different. Returns every record in one response: Featurebase does not page this endpoint, so limit and cursor are not supported and are ignored if sent.
- **Get single Featurebase board by ID** (Get). Get a board by ID. Retrieves a single board by its unique identifier. Returns the full board object including all access controls, feature toggles, and localization settings. Required: id.
- **List all Featurebase brands** (List). List all brands. Returns all brands in your organization with cursor-based pagination.
- **Get single Featurebase brand by ID** (Get). Get brand by ID. Retrieves a single brand by its Featurebase ID. Required: id.
- **Create a Featurebase changelog publication** (Create). Publish a changelog. Publishes a changelog and optionally sends an email notification to subscribers. Required: changelog_id.
- **Featurebase changelog subscribers bulk create** (Create). Add changelog subscribers. Adds email addresses as changelog subscribers in bulk. Subscribers will receive email notifications when new changelogs are published (if email notifications are enabled during publishing). Required: emails.
- **Featurebase changelog subscribers bulk delete** (Delete). Remove changelog subscribers. Removes email addresses from changelog subscribers in bulk. Removed subscribers will no longer receive email notifications when new changelogs are published. Required: emails.
- **Create a Featurebase changelog unpublication** (Create). Unpublish a changelog. Unpublishes a changelog, removing it from public view. Required: changelog_id.
- **List all Featurebase changelogs** (List). List all changelogs. Returns all changelogs for the authenticated organization. Changelogs are release notes and updates that keep users informed about new features, improvements, and bug fixes. Each changelog can have.
- **Create a Featurebase changelog** (Create). Create a new changelog. Creates a new changelog for the authenticated organization. Required: title.
- **Get single Featurebase changelog by ID** (Get). Get a changelog by ID. Retrieves a single changelog by its unique identifier or slug. Returns the full changelog object including. Required: id.
- **Update a Featurebase changelog by ID** (Update). Update a changelog. Updates an existing changelog by its unique identifier. You can update. Required: id.
- **Delete a Featurebase changelog by ID** (Delete). Delete a changelog. Deletes a changelog by its unique identifier. Required: id.
- **List all Featurebase comments** (List). List comments. Returns comments for your organization. Comments are threaded discussions. Each comment can have.
- **Create a Featurebase comment** (Create). Create a new comment. Creates a new comment or reply to an existing comment. You can create a comment for a post or changelog. Comments support. Required: content.
- **Get single Featurebase comment by ID** (Get). Get a comment by ID. Retrieves a single comment by its unique identifier. Returns the full comment object including. Required: id.
- **Update a Featurebase comment by ID** (Update). Update a comment. Updates an existing comment by its unique identifier. You can update. Required: id.
- **Delete a Featurebase comment by ID** (Delete). Delete a comment. Deletes a comment by its unique identifier. Required: id.
- **Featurebase comments search** (Search). Search comments. Search comments with a structured filter AST, full-text search, sorting, and cursor pagination.
- **List all Featurebase companies** (List). List all companies. Returns all companies in your organization with cursor-based pagination.
- **Create a Featurebase company** (Create). Create or update a company. Creates a new company or updates an existing one. Uses the external companyId as the unique identifier for upsert matching. If a company with the given companyId already exists, it will be updated. Otherwise, a new company will be created. Required: companyId, name.
- **Get single Featurebase company by ID** (Get). Get company by ID. Retrieves a single company by its Featurebase ID. Required: id.
- **Delete a Featurebase company by ID** (Delete). Delete a company. Deletes a company by its Featurebase ID. This will also remove the company from all linked users' associations. Required: id.
- **Featurebase companies search** (Search). Search companies. Search companies with a structured filter AST, sorting, and cursor pagination.
- **Delete a Featurebase companies by company ID by ID** (Delete). Delete a company by external company ID. Permanently deletes a company by its external company ID (the companyId from your system). This will also remove the company from all linked users' associations. Required: id.
- **List all Featurebase company contacts** (List). List contacts attached to a company. Returns all contacts (customers) attached to a specific company. Only returns contacts with type "customer" that have the company in their companyIds array. Uses cursor-based pagination. Required: company_id.
- **Create a Featurebase company contact** (Create). Attach a contact to a company. Attaches a contact (customer) to a company. Adds the company to the contact's companyIds array and embedded companies array. This operation is additive - existing company associations are preserved. Also increments the linkedUsers count on the company. Required: company_id, contactId.
- **Delete a Featurebase company contact by ID** (Delete). Remove a contact from a company. Removes a contact (customer) from a company. Removes the company from the contact's companyIds array and embedded companies array. Also decrements the linkedUsers count on the company. Required: id, company_id.
- **Create a Featurebase contact block** (Create). Block a contact. Blocks a contact by their Featurebase ID using the global moderation system. Required: contact_id.
- **List all Featurebase contact email preferences** (List). Get contact email preferences by ID. Retrieves the email preference state for a customer contact by their Featurebase ID. Required: contact_id.
- **Featurebase contact email preferences bulk update** (Update). Update contact email preferences by ID. Updates one or more email preferences for a customer contact by their Featurebase ID. Required: contact_id, preferences.
- **List all Featurebase contact email preferences by user ID** (List). Get contact email preferences by external user ID. Retrieves the email preference state for a customer contact by their external user ID. This endpoint only supports customer contacts and mirrors the existing by-user-id lookup pattern used across the contact API. Required: user_id.
- **Featurebase contact email preferences by user ID bulk update** (Update). Update contact email preferences by external user ID. Updates one or more email preferences for a customer contact by their external user ID. This endpoint only supports customer contacts and mirrors the existing by-user-id lookup pattern used across the contact API. Required: user_id, preferences.
- **Create a Featurebase contact merge** (Create). Merge a lead into a customer. Merges a lead into a customer. Use it when a lead becomes a user of your product. The source contact must be a lead and the destination contact must be a customer. Both must belong to the authenticated organization. When the merge completes. Required: destinationContactId, sourceContactId.
- **Create a Featurebase contact unblock** (Create). Unblock a contact. Unblocks a contact by their Featurebase ID from the global moderation system. Required: contact_id.
- **List all Featurebase contacts** (List). List contacts. Returns a list of contacts (customers and leads) in your organization using cursor-based pagination.
- **Create a Featurebase contact** (Create). Create or update a contact. Creates a new contact or updates an existing one. If a contact with the given email or userId already exists, it will be updated. Otherwise, a new contact will be created.
- **Get single Featurebase contact by ID** (Get). Get contact by ID. Retrieves a single contact by their Featurebase ID. Returns both customers and leads. Required: id.
- **Delete a Featurebase contact by ID** (Delete). Delete contact by ID. Permanently deletes a contact by their Featurebase ID. Supports deleting both customers and leads. Required: id.
- **Featurebase contacts search** (Search). Search contacts. Search contacts (customers and leads) with a structured filter AST, sorting, and cursor pagination.
- **Get single Featurebase contacts by user ID by ID** (Get). Get contact by external user ID. Retrieves a single contact by their external user ID (from your system via SSO). Required: id.
- **Delete a Featurebase contacts by user ID by ID** (Delete). Delete contact by external user ID. Permanently deletes a contact by their external user ID. Required: id.
- ...and 121 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
