Skip to content
meruma Developers
meruma.app Log in

Developers · Artificial intelligence

Connect your AI to meruma

Claude, ChatGPT or another AI works in meruma as you, with your permissions. It searches contacts and cards, reads chats and the agenda, and takes notes for you.

How to connect it

You paste an address and sign in to meruma: the AI works as you, in the organization you choose. The MCP address is:

https://mcp.meruma.app/mcp
  • Claude: on the web or in the desktop app, go to Settings › Connectors › “Add custom connector” and paste the address. It asks you to sign in to meruma and pick the organization.
  • ChatGPT: where your plan allows custom connectors, create one with this address and authorize it with your meruma account.
  • Claude Code and other clients: any MCP client with OAuth works. In Claude Code: claude mcp add --transport http meruma https://mcp.meruma.app/mcp.

First, an owner or admin has to allow external AIs in Integrations › Connect your AI: it is off by default. Each person also needs Integrations in their role.

What it can do, and what it can’t

It can:

  • Search and read contacts, cards, chats, the agenda and reports, and look things up in the help center.
  • Add notes and reminders, create and move cards, and assign contacts and cards.
  • Everything it changes shows in the activity as done by you, with the AI’s name, and owners and admins see it in the log.

It can’t:

  • Send messages to customers: that stays in meruma, where you confirm each one.
  • Make bulk changes or create and delete automations.
  • See fields marked as sensitive or the credentials of your channels.

Your permissions, always

  • It sees only what you see: the same role, visibility and hidden fields.
  • Each connection is yours: nobody else can use it, and you disconnect it from Integrations whenever you want.
  • Tokens last one hour and renew. If your role loses Integrations or the organization turns external AIs off, they stop working right away.
  • meruma tells the AI that what customers write is data, never instructions.

Limits

  • 30 requests per minute and 1,000 per day, per connection.
  • Up to 200 changes per day per connection; reading keeps working.
  • Up to 10 connected AIs per person in each organization.

For people building MCP clients

Standard MCP over Streamable HTTP, with OAuth 2.1.

  • MCP 2026-07-28 (stateless, with server/discover) and the earlier versions 2025-11-25, 2025-06-18 and 2025-03-26 with initialize, on the same endpoint, which responds in JSON.
  • Discovery: https://mcp.meruma.app/.well-known/oauth-protected-resource/mcp (RFC 9728) points to the authorization server, https://api.meruma.app/.well-known/oauth-authorization-server (RFC 8414).
  • Clients register with a metadata document (the client_id is its URL) or, otherwise, with dynamic registration (RFC 7591). They are public clients: PKCE with S256 is required.
  • Scopes mcp:read and mcp:write. With resource (RFC 8707), the token only works on the MCP.

Reviewed on