# Staffbase MCP connector

The Staffbase connector brings employees, groups, channels and posts to Claude, ChatGPT, Cursor and Microsoft Copilot, so each person can search, update and publish in Staffbase inside their own access, with every action logged.

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

## Facts

| | |
| --- | --- |
| Application | Staffbase |
| Category | Unified User |
| AI tools | 142 |
| 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 Staffbase is connected

- Find every Staffbase user in the Berlin branch group
- Draft a post for the All Employees channel about Friday's town hall
- Which Staffbase groups is Maria Lopez in?

## Connect Staffbase in Elaichi

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

1. Open Connections, choose Add connection, and pick Staffbase.
2. Optionally set Share with, then press Connect.
3. Paste a Staffbase API key. One person generates a token in Staffbase 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 Staffbase tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Staffbase 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.

## Staffbase 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`.

## Staffbase 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.

## Staffbase 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.

## Staffbase 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 Staffbase 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 Staffbase 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 Staffbase through Elaichi

### Publish a channel post from a quick brief

Internal comms. Ask for a draft of the Friday update, check the wording, then post it to the right Staffbase channel without leaving the chat.

### Set up a new hire on day one

HR. Create the Staffbase user, add them to the right groups, and confirm what they can see before their first shift.

### Sign a lost phone out everywhere

IT. End every active session for one Staffbase user and send an account recovery so they can get back in safely.

### Find who is in which branch

Operations. Search Staffbase users and groups to confirm who sits in a branch before a change is announced there.

### Catch a record up after a change

HR. Update a job title, department or location on a Staffbase user as soon as the change is confirmed, no form to fill in.

### Check what a branch channel has said

Internal comms. List the posts in a branch channel and get a plain summary of what frontline staff have been told this month.

## Elaichi vs Zapier MCP vs Composio for Staffbase

All three can connect Staffbase 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 Staffbase tools | Allow or restrict single Staffbase 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 Staffbase 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 Staffbase to Claude?

Connect Staffbase in Elaichi first, which asks for a Staffbase API key and nothing else; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks, and Staffbase users, groups, channels and posts are ready to work with.

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

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

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

It can find employees and groups in Staffbase, create or update a user, add someone to a group, and draft and publish a post to a channel. It can also end a user's sessions, send an account recovery, and check the latest directory syncs. Short, concrete asks, such as listing the posts in the Munich branch channel, work better than long sentences.

### Does connecting Staffbase give the AI access to every employee and channel?

No. Every call runs as the person who signed in, so an agent sees only the Staffbase users, groups, channels and posts that person already has access to. Elaichi can narrow that further with roles and restrictions, and it can never widen it.

### Can my team share one Staffbase connection?

Yes. One person connects Staffbase with the API key, shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who created a user or published a post, not the connection.

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

Yes. Restrictions apply per action, so you can keep deleting Staffbase users or groups, or publishing posts, off limits for a role or for one person. A restricted action still appears in Elaichi's tool search flagged as restricted, but no client can run it, whatever the prompt says.

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

Offboarding a person in Elaichi ends their access to Staffbase through every client at once. A connection they shared keeps working for everyone else on the team. If you want Staffbase gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

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

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

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

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

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

## All 142 Staffbase tools

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

- **List all Staffbase users** (List). List all users in Staffbase with their available data. Returns: activated, avatar, config, created, department, emails, externalID, firstName, groupIDs, id, lastName, location, phoneNumber, position, profile, publicEmailAddress, role, status, updated, contacts. The v1 endpoint returns only activated users by default.
- **Create a Staffbase user** (Create). Invite a new user to the Staffbase platform. Returns the created user including id, role, status, emails, and created. Requires role.
- **Staffbase users search** (Search). Search users in Staffbase based on the provided search criteria. Returns: total, nextCursor, prevCursor, entries.
- **Get single Staffbase user by ID** (Get). Get a single Staffbase user by id. Returns: activated, avatar, config, created, department, emails, externalID, firstName, groupIDs, id, lastName, location, phoneNumber, position, profile, publicEmailAddress, role, status, updated, AdministrativeToken. Required: id.
- **Update a Staffbase user by ID** (Update). Update a Staffbase user by applying an incremental update to the user with the given id. Returns the updated user object including id, email, userName, role, status, and profile. Required: id. This legacy endpoint is deprecated; use the PATCH method instead.
- **Delete a Staffbase user by ID** (Delete). Delete a Staffbase user by id. Deleted accounts cannot be restored by administrators or Staffbase, and the last remaining administrator cannot be deleted. Returns an empty 204 response on success. Required: id.
- **Staffbase users partial update** (Update). Partially update a Staffbase user, providing only the fields to change. Returns the updated user: id, email, role, status, createdAt, profile, userName. Required: user_id. User API v1 is deprecated.
- **List all Staffbase user groups** (List). List the Staffbase groups a specific user is a member of. Returns: id, externalID, name, type, ownerID, users. Required: user_id. Max 100 per page.
- **Staffbase user groups search** (Search). Search the groups of a Staffbase user by group name, sorted by creation date. Returns: id, attributes, AdministrativeToken. Required: user_id.
- **Get single Staffbase groups visible by ID** (Get). List the Staffbase groups visible to a user, filtered by group type with conditional groups omitted. Returns: id, externalID, name, type, ownerID, users. Required: id.
- **Create a Staffbase user recovery** (Create). Send an account recovery email to a Staffbase user. Returns an empty 202 response on success — the API only confirms the recovery mail was sent. Required: user_id.
- **Staffbase user sessions bulk delete** (Delete). Log a user out of Staffbase by invalidating all their active sessions. Returns a 202 status with no payload on success. Required: user_id.
- **List all Staffbase users syncs** (List). List Staffbase users ordered by their updated timestamp for incremental synchronization. Returns: activated, avatar, config, created, department, emails, externalID, firstName, groupIDs, id, lastName, location, phoneNumber, position, profile, publicEmailAddress, role, status, updated. Max 1000 per page.
- **List all Staffbase groups** (List). List all groups on the Staffbase platform sorted by name. Returns: id, accessorIds, adminIds, externalId, config, type, creator, updatedAt, inclusions, inclusionUserIds, exclusions, exclusionUserIds. Max 500 per page.
- **Create a Staffbase group** (Create). Create a new group on the Staffbase platform; the group type is determined by the configuration settings you provide. Returns: id, accessorIds, adminIds, externalId, config, type, creator, updatedAt, inclusions, inclusionUserIds, exclusions, exclusionUserIds. Required: config.
- **Staffbase groups search** (Search). Search groups on the Staffbase platform by free-text query or filter by name, type, creator, and permission. Returns: data. All filters are optional.
- **Get single Staffbase group by ID** (Get). Get the details of a specific Staffbase group by id. Returns: id, accessorIds, adminIds, externalId, config, type, creator, updatedAt, inclusions, inclusionUserIds, exclusions, exclusionUserIds, AdministrativeToken. Required: id.
- **Update a Staffbase group by ID** (Update). Update a Staffbase group by id; only fields provided in the body are changed (does not apply to nested fields like localization). Returns: id, accessorIds, adminIds, externalId, config, type, creator, updatedAt, inclusions, inclusionUserIds, exclusions, exclusionUserIds, AdministrativeToken. Required: id.
- **Delete a Staffbase group by ID** (Delete). Delete a group in Staffbase by its group identifier. Returns an empty 204 response on success. Required: id.
- **List all Staffbase branch channels** (List). List all Staffbase news channels that are manageable by the current accessor (API token or user), including channels that are not published. Returns channel records with id and attributes (the channel fields defined upstream).
- **List all Staffbase channels** (List). List news channels in Staffbase that are accessible to the current API token or user. Returns: id, name. Supports searching by channel name via the query parameter. Max 100 per page.
- **Get single Staffbase channel by ID** (Get). Get a single Staffbase news channel by its id. Returns the channel object with its id and name. Required: id.
- **List all Staffbase channel posts** (List). List the news posts of a Staffbase news channel. Returns each post with id, externalID, planned, published, and contents. Required: channel_id. Max 100 per page.
- **Create a Staffbase channel post** (Create). Create a new news post in a Staffbase news channel. Returns the newly created post including id, externalID, planned, published, contents, and campaignId. Required: channel_id, contents.
- **List all Staffbase posts** (List). List all Staffbase news posts that are accessible for the current accessor. Returns post records with id, externalID, planned, published, contents, and campaignId. Supports query, sort, manageable, and contentType filters.
- **Staffbase posts search** (Search). Search Staffbase news posts for a query matching the content, hashtags, image description, teasers, or titles. Returns matching posts with id, externalID, planned, contents, and campaignId. Endpoint is in Beta and may still undergo changes.
- **Get single Staffbase post by ID** (Get). Get a single Staffbase news post by id. Returns the full post object including id, externalID, planned, published, contents, and campaignId. The id can be either the system-assigned post ID or the externalID supplied on creation. Required: id.
- **Update a Staffbase post by ID** (Update). Update a Staffbase news post by id with the data provided in the request. Returns the updated post including id, externalID, planned, published, contents, and campaignId. Campaign assignment is managed through the Campaigns API, not this endpoint. Required: id.
- **Delete a Staffbase post by ID** (Delete). Delete a Staffbase news post by id; the post is removed from the system or moved to trash if trash is active on the platform. Returns an empty 204 response on success. Required: id.
- **Create a Staffbase post notification** (Create). Resend notifications for a news post in Staffbase. Returns the created resend configuration including email, push, recipients, and per-locale contents. Required: post_id, email, push, recipients.
- **List all Staffbase post acknowledgements** (List). List acknowledgements for a Staffbase news post, most recent acknowledgements first. Returns acknowledgement records with id and attributes (the user who acknowledged the post and the point in time they did so); attribute fields are defined upstream and not enumerated in the docs. Required: post_id.
- **List all Staffbase newspage posts** (List). List Staffbase news page posts for the client view, ordered by publish date; only posts accessible to the current accessor are included. Returns: id, attributes. Required: news_page_id.
- **List all Staffbase newspage channels** (List). List channels of a Staffbase news page in which the current accessor (API token or user) is a contributor and therefore allowed to create posts. Returns channel records with id. Required: news_page_id. Max 10 per page.
- **List all Staffbase newspage rights** (List). List the rights the current accessor (API token or user) has on a Staffbase news page, to determine whether it may contribute to news channels assigned to the page. Returns an array of right strings such as "CONTRIBUTE" when contribution is allowed. Required: news_page_id.
- **List all Staffbase pages** (List). List Staffbase pages with their content. Filter by spaceIds, status, and sort with orderBy. Returns: id, spaceId, createdAt, updatedAt, title.
- **Create a Staffbase page** (Create). Create a page in a Staffbase space. Returns the created page with id, contents, spaceId, createdAt, and publishedAt. Required: contents.
- **Get single Staffbase page by ID** (Get). Get a single Staffbase page by id, including its localized content and access settings. Returns: id, createdAt, updatedAt, title. Required: id.
- **Update a Staffbase page by ID** (Update). Update the content and details of a Staffbase page by id. Returns: id, createdAt, updatedAt, title. Required: id, contents.
- **Delete a Staffbase page by ID** (Delete). Delete a Staffbase page by id. Returns an empty 204 response on success. Required: id.
- **List all Staffbase pages syncs** (List). List Staffbase pages updated or deleted within the last 60 days, paged by cursor. Returns each sync entry with state and the page entity including id, branchId, spaceId, contents, timestamps, ownerId, readers, and admins; deleted entries carry only id, branchId, spaceId, and deletedAt.
- **List all Staffbase chats timeseries** (List). Get Staffbase chat timeseries stats about active chat users, active group conversations and active direct conversations. Returns: activeChatUsers, activeDirectConversations, activeGroupConversations, group. Prefer format=json over csv. Required: groupBy.
- **List all Staffbase contents rankings** (List). List Staffbase content rankings — content with its branch, space, and publicity context ranked descending by visits. Returns: group, registeredVisitors, registeredVisits, unregisteredVisitors, unregisteredVisits. Supports SCIM filtering, result grouping, and CSV output via format=csv.
- **List all Staffbase pages rankings** (List). List Staffbase pages ranked by their usage statistics for a reporting interval. Returns: bounceRate, clicks, id, menuId, pageTitle, secondsSpent, sessions, shortSessions, spaceId, spaceName, viewers, views. Required: since, until.
- **List all Staffbase pages timeseries** (List). Get the Staffbase pages timeseries: page views and unique visitors grouped into day, week, or month buckets. Returns: date, views, visitors. Required: since, until, groupBy.
- **List all Staffbase views streams** (List). List Staffbase page view counts for all currently published pages over an interval. Returns: pageId, viewCount. Required: since, until. Response is a newline-delimited JSON stream with one object per line.
- **Get single Staffbase page click ranking by ID** (Get). Get the aggregated click ranking for a specific Staffbase page, ranked by how many times each URL or element was clicked. Returns: clickCount, title, url. Limit must be between 1 and 10000. Required: id, since, until.
- **List all Staffbase page group rankings** (List). List the Staffbase groups whose members visited a specific page, ranked by the number of unique visitors per group. Returns: groupId, groupName, visitors. Required: page_id, since, until.
- **Get single Staffbase page histogram by ID** (Get). Get the time-distribution histogram for a specific Staffbase page, grouping visitor sessions into predefined time-spent buckets. Returns: count, seconds. Required: id, since, until.
- **List all Staffbase page timeseries** (List). Get detailed timeseries analytics for a single Staffbase page, including views, unique visitors, and total clicks grouped into time buckets. Returns: date, totalClicks, views, visitors. Required: page_id, since, until, groupBy.
- **List all Staffbase page views** (List). Get the total view count for a specific Staffbase page within the provided reporting interval. Returns: count. Required: page_id, since, until.
- ...and 92 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
