Model context protocol (MCP)

Connect your AI tools to Unipile using MCP

The Model Context Protocol (MCP) is a standard for connecting Large Language Models (LLMs) to platforms like Unipile. Once connected, your AI assistants can interact with your Unipile accounts on your behalf.


Installation

1. Create a scoped API key

The MCP can be used simply to help your agent understand the Unipile API design and explore available endpoints.

However, you can also configure it with an Unipile API Key to allow the agent to call account Methods on your behalf.

Before connecting an AI client, create a dedicated Scope, assign only the accounts the client should access, and create a scoped Account API Key for that Scope.

Use this scoped key in the examples below. It limits the client to the accounts assigned to its Scope.

Do not use a Service API Key or a global Account API Key with an MCP client. Both provide access to every account in the Application. Keep your scoped key secret and only configure it in clients and environments you trust.


2. Set up your client

Choose your MCP client, then follow the instructions.

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "unipile": {
      "url": "https://developer.unipile.com/mcp?branch=v2.0",
      "headers": {
        "X-API-KEY": "your-scoped-api-key"
      }
    }
  }
}

Next step

Once configured, you can test your MCP server connection:

  1. Open your AI client (Cursor, Windsurf, Claude, Codex, or ChatGPT desktop)
  2. Start a new chat with the AI assistant
  3. Ask about Unipile or request an account action. For example:
    • "How do I [common use case]?"
    • "Show me an example of [API functionality]"
    • "Create an [integration type] using Unipile"
    • "Send a message to [xxxx] using account acc_1234521321"
    • "List all emails in the [email protected] inbox"

The AI should now have access to the Unipile API Reference and to the account data allowed by your Scope through the MCP server.


Available tools

  • list-specs - Lists all API specs available in the project, with their titles
  • list-endpoints - Returns all API paths and HTTP methods with their summaries
  • get-endpoint - Returns full detail on a specific endpoint: description, parameters, security
  • get-request-body - Returns the request body schema for an endpoint
  • get-response-schema - Returns the response schema for a specific endpoint and status code
  • list-security-schemes - Lists all authentication methods defined in your API spec
  • search-specs - Case-insensitive search across all paths, operations, and schemas
  • execute-request - Makes a live API call and returns the response. Requires auth headers to be forwarded
  • get-code-snippet - Generates a working code snippet for any endpoint in any programming language

Did this page help you?