Partoo MCP Server - Partoo API

Overview

The Partoo MCP Server implements the Model Context Protocol, a standard that lets AI assistants call external tools. It exposes the Partoo API as a set of ready-to-use tools so that LLMs like Claude can search businesses, reply to reviews, send messages, publish posts, and query analytics — all without writing a single line of integration code.

The MCP server is stateless and proxies every request to the Partoo REST API on your behalf. No data is stored server-side.

Authentication

Every MCP request must include your Partoo API key in the x-APIKey header. The server forwards it to the Partoo API and never stores it.

x-APIKey

string

required

Your Partoo API key. Refer to the API Keys guide to generate one.

Keep your API key secret. Do not commit it to source control — use your LLM client’s secret/environment variable mechanism instead.

Environments

Environment	MCP Server URL
Production	`https://mcp.partoo.co`
Sandbox	`https://mcp.sandbox.partoo.co`

Start with the Sandbox URL to test your setup safely before switching to Production.

Connect with your LLM

The Partoo MCP Server uses the Streamable HTTP transport (a single POST / endpoint). All major MCP-compatible clients support this transport. Replace YOUR_API_KEY with your actual Partoo API key in the snippets below.

Claude Desktop
Claude Code
Cursor
Other clients

Claude Desktop connects to the Partoo server through a small helper called mcp-remote. You don’t need to install it by hand — the configuration below launches it automatically with npx.

Why the helper is needed. Claude Desktop’s built-in “Add custom connector” option only signs in with OAuth — it logs you into a service through a browser pop-up and has no place to enter an API key. The Partoo server doesn’t use OAuth; it authenticates with your API key sent in the x-APIKey header. Since the connector screen can’t attach that header, the built-in option can’t reach Partoo. mcp-remote fills the gap: it sits between Claude Desktop and the Partoo server and adds your API key to every request.

Before you start, install Node.js (the LTS version is fine). This provides the npx command used in the configuration. To confirm it’s installed, open a terminal and run node --version and npx --version — both should print a version number.Then edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

claude_desktop_config.json

{
  "mcpServers": {
    "partoo": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.partoo.co",
        "--header",
        "x-APIKey:${PARTOO_API_KEY}"
      ],
      "env": {
        "PARTOO_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY with your actual Partoo API key — leave PARTOO_API_KEY untouched. PARTOO_API_KEY is the name of the environment variable referenced by ${PARTOO_API_KEY} in the arguments; only the value next to it (YOUR_API_KEY) should be edited.

Do not put a space in the --header value. mcp-remote splits header arguments on spaces, so reference the key via the PARTOO_API_KEY environment variable (set in env) using ${PARTOO_API_KEY} with no space.

Fully quit and reopen Claude Desktop after saving (closing the window is not enough). The Partoo tools will then appear in the tool picker.

Option 1 — CLI (recommended)Run the following command to register the server. Use --scope project to limit it to the current repository, or --scope user to make it available globally.

Production

claude mcp add --transport http --scope user partoo https://mcp.partoo.co \
  --header "x-APIKey: YOUR_API_KEY"

Sandbox

claude mcp add --transport http --scope user partoo https://mcp.sandbox.partoo.co \
  --header "x-APIKey: YOUR_API_KEY"

Option 2 — Manual configAdd the server directly to ~/.claude/settings.json (user-level) or .claude/settings.json at the root of your project (project-level):

settings.json

{
  "mcpServers": {
    "partoo": {
      "type": "http",
      "url": "https://mcp.partoo.co",
      "headers": {
        "x-APIKey": "YOUR_API_KEY"
      }
    }
  }
}

Prefer --scope project (or the project-level config file) when working in a single repository. Add .claude/settings.json to .gitignore if it contains your API key directly.

Create or edit .cursor/mcp.json at the root of your project (or ~/.cursor/mcp.json for a global config):

.cursor/mcp.json

{
  "mcpServers": {
    "partoo": {
      "url": "https://mcp.partoo.co",
      "headers": {
        "x-APIKey": "YOUR_API_KEY"
      }
    }
  }
}

Reload the Cursor window after saving.

Any MCP client that supports Streamable HTTP can connect to the Partoo MCP Server. Use the following values:

Setting	Value
Transport	Streamable HTTP
URL	`https://mcp.partoo.co`
Header name	`x-APIKey`
Header value	Your Partoo API key

Refer to your client’s documentation for the exact configuration format.

Available tools

The server exposes 14 tools across 5 groups. See the Tools Reference for the full parameter list.

Group	Tools
Businesses	`search_businesses`, `get_business`, `update_business`
Reviews	`search_reviews`, `reply_to_review`, `get_review_metrics`
Messages	`list_conversations`, `send_message`, `list_messages`
Posts	`create_post`, `search_posts`
Analytics	`get_profile_metrics`, `get_profile_keywords`

​Overview

​Authentication

​Environments

​Connect with your LLM

​Available tools

Overview

Authentication

Environments

Connect with your LLM

Available tools