Skip to main content

Perspective MCP Server

The Perspective MCP server exposes Perspective's capabilities as a set of tools that AI assistants can call directly. Using any MCP-compatible client — Claude Desktop, Claude Code, Cursor, or any other host that speaks the Model Context Protocol — you can ask an AI to build and update funnels, author email sequences, query analytics, look up CRM contacts, and manage brands, domains, and senders, all through natural conversation.

What you can do

AreaExamples
FunnelsCreate a new funnel from a brief, update copy and design, check job status
Email sequencesList, create, and update sequences; preview step HTML; publish or unpublish
Metrics & analyticsQuery KPIs, chart data, insights, sequence stats, and funnel events
CRMSearch contacts, fetch contact details, read CRM properties
Brands, domains & sendersList and create brands, list sending domains and sender addresses
WorkspacesList workspaces and their campaigns

Relationship to the REST API

The MCP server and the REST API share the same underlying Perspective workspace data. The REST API is designed for programmatic integrations — your backend code, webhooks, and automation pipelines. The MCP server is designed for conversational AI workflows: an AI assistant reasons about your goals and calls the appropriate tools on your behalf, without you having to write request code.

Both interfaces operate on the same workspace data. The REST API authenticates with an API key; the MCP server uses an OAuth2 Bearer token over HTTP, or an API key when run via the DXT desktop package.

Two ways to connect

  • Remote HTTP — point any MCP client at https://api.perspective.co/mcp and authenticate with an OAuth2 Bearer token. Best for cloud-based clients and CI integrations. See Connecting.
  • Desktop DXT — install the perspective-mcp DXT package in Claude Desktop. The DXT binary runs locally and proxies to the hosted server. No OAuth flow needed — just paste your API key in the DXT settings. See Connecting.

Tool scopes

The MCP server supports five named tool scopes that limit which tools are registered for a given session. Scopes keep the model focused: when you only need to build a funnel there is no reason to expose CRM or sequence tools. See Tool Scopes for the full mapping.

Next steps