Skip to content

Unified User

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.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Find every Staffbase user in the Berlin branch group

Working in Staffbase with Elaichi

  • List all Staffbase users
  • Staffbase users search
  • Get single Staffbase user by ID
Ask anything…
Governance / Audit log Last 24 hours
Staffbase Get single Staffbase user by ID Emily Carter · Claude · 9:41 AM Done
Staffbase Staffbase users search Emily Carter · Claude · 9:41 AM Done
Staffbase List all Staffbase users Emily Carter · Claude · 9:41 AM Done
Staffbase Create a Staffbase user Megan Brooks · ChatGPT · 9:38 AM Done
Staffbase Update a Staffbase user by ID Ryan Hayes · Cursor · 9:35 AM Done

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

Step by step, for each AI app

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

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

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

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

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

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

  • Internal comms

    Publish a channel post from a quick brief

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

  • HR

    Set up a new hire on day one

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

  • IT

    Sign a lost phone out everywhere

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

  • Operations

    Find who is in which branch

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

  • HR

    Catch a record up after a change

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

  • Internal comms

    Check what a branch channel has said

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

Try asking

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

See all 142 Staffbase tools →

What connecting Staffbase gets you

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

Elaichi Agent

Ask Elaichi to work across your apps.

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?

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask Staffbase questions in plain language.

Three starter prompts pull live answers from Staffbase users, groups, channels and posts.

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

Every MCP client reaches Staffbase through one endpoint.

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

ElaichiTools
Tool Action Description
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.

Tool catalog

142 Staffbase tools, ready with no code.

Users, groups, channels and posts covered without an engineer writing custom code.

ElaichiToolboxes
Name Source template Tools Created

Internal comms toolbox

Staffbase · channels and posts

Staffbase starter 18 Mar 4, 2026

HR toolbox

Staffbase · users and onboarding

— 9 Mar 2, 2026

IT toolbox

Staffbase · accounts, sessions and syncs

— 24 Feb 27, 2026

Operations toolbox

Staffbase · branch channels and groups

Staffbase starter 6 Feb 19, 2026

Leadership toolbox

Staffbase · company-wide announcements

— 31 Jan 30, 2026

Branch managers toolbox

Staffbase · local teams and updates

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Staffbase toolbox.

Internal comms, HR and IT each see a toolbox scoped to their work.

ElaichiConnections
Connection Scope Status Access
ST

Staffbase (Internal comms)

Connected by Emily Carter

Personal • Active 1 team · 6 members
ST

Staffbase (HR)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
ST

Staffbase (IT helpdesk)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
ST

Staffbase (Operations)

Connected by Tyler Reed

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

Staffbase (Frontline)

Connected by Ryan Hayes

Personal • Active Not shared
ST

Staffbase (Head office)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates use Staffbase without touching the API key.

One person connects an account, shares it with teams, and nobody else sees a credential.

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]

Staffbase Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Staffbase Users Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Staffbase Users List Toolbox

Audit log

Every Staffbase action names who did it.

When, who, what happened, type and resource, 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.

Staffbase digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch users

    Staffbase

    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

    Staffbase

    Queued

Workflows

A schedule starts the Staffbase digest, you approve.

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

Staffbase health

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

Live

Users

1,284 ↓ 12%

Groups

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Users created

Last 14 days

By team

Share of activity

Internal comms 34%

HR 27%

IT helpdesk 21%

Operations 18%

Collections and dashboards

Staffbase numbers computed on a schedule, no model.

Four metrics, posts created over 14 days and a breakdown by team, refreshed automatically.

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Staffbase, 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 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Staffbase tools for your AI agents

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

Questions, answered

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.

Put Staffbase 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