XBASE MCP: use XBASE from Claude and Cursor

The XBASE MCP lets an AI agent, like Claude Code or Cursor, read and edit your workspace through plain-language conversation: WhatsApp, Instagram, AI agents, automations, contacts, conversations and funnels. There are 198 tools.

MCP (Model Context Protocol) is the open standard these agents use to connect to other systems.

How it worksCopy Anchor Link

• Server address: https://mcp.xbase.app/mcp (HTTP transport).
• Token access: each connection uses a workspace MCP access token, which starts with xmcp_.
• Locked to the workspace: the token only reads and edits the workspace where it was created, even if the agent asks for another one.
• Your roles apply: the token acts as the person who created it. If that person cannot edit agents in XBASE, the AI agent cannot either.
• You revoke it whenever you want: the token stops working right away.

Create the tokenCopy Anchor Link

1. In XBASE, open Integrations, go to the Agents & APIs tab and find the MCP access card. You need permission to manage integrations.
2. Click New token (or Connect integration, if it is your first one).
3. In Name, write something that identifies the use, like "Marco's Claude Code", and click Create token.
4. The Token created window shows the Token, the MCP server URL and the ready-made command for Claude Code (terminal). Copy it now: the token is not shown again.
5. Click Done, I copied it.

The card lists the tokens with their last 4 characters, the creation date and the last use. To cut access, click Revoke.

Connect in Claude CodeCopy Anchor Link

In the terminal, run the command shown in the Token created window, replacing xmcp_... with your token:

claude mcp add --transport http xbase https://mcp.xbase.app/mcp --header "Authorization: Bearer xmcp_..."

Then ask in plain language. Examples:

• "List the approved WhatsApp templates in my workspace."
• "Create a quick reply called hours with our business hours."
• "Show today's conversations that are in the Proposal stage."

Connect in Cursor and other MCP clientsCopy Anchor Link

Any MCP client with HTTP transport works. Enter the server URL and the authorization header. In Cursor, in the MCP configuration file (.cursor/mcp.json):

{
  "mcpServers": {
    "xbase": {
      "url": "https://mcp.xbase.app/mcp",
      "headers": { "Authorization": "Bearer xmcp_..." }
    }
  }
}

ToolsCopy Anchor Link

The full list, generated from the server code, has one page per area (on the side, under Tools). Where a tool asks for workspaceId, only the token's workspace id is accepted: if the agent sends another, the MCP refuses and answers with the right id.

Rules and limitsCopy Anchor Link

• The token does not pick tools: it unlocks every tool on the list, always limited to the roles of the person who created it.
• Actions have real effects: sending, editing and deleting through MCP is the same as doing it on screen. Delete actions cannot be undone.
• When someone stops being a member of the workspace, the tokens they created stop working.
• Keep the token like a password. If it leaks, revoke it in Integrations → MCP access and create another one.

Frequently asked questionsCopy Anchor Link

See alsoCopy Anchor Link