Skip to main content

Connecting to the MCP Server

There are two ways to connect an MCP client to Perspective:

MethodBest for
Remote HTTPClaude Code, Codex, Cursor, server-side integrations, and stdio-only clients through mcp-remote
Desktop DXTClaude Desktop

Remote HTTP​

The MCP server is reachable at:

POST https://api.perspective.co/mcp

To limit the tools exposed in a session, append a scope to the path:

POST https://api.perspective.co/mcp/funnel-build
POST https://api.perspective.co/mcp/sequences
POST https://api.perspective.co/mcp/analytics
POST https://api.perspective.co/mcp/crm

Omitting the scope (plain /mcp) registers all tools — the default for backward compatibility.

Authentication​

The HTTP endpoint is protected by OAuth2. Requests must include a valid Bearer token in the Authorization header:

Authorization: Bearer <your-oauth-token>

See Authentication for how to obtain a token and how the OAuth discovery endpoints work.

Client configuration​

note

MCP client configuration formats evolve quickly. Verify the exact field names against your client's current MCP documentation (Claude Desktop, Claude Code, Codex, Cursor).

Any client that implements the MCP authorization spec can connect, including clients that strictly validate the OAuth discovery documents, such as Codex and mcp-remote. The client's OAuth callback must be on the server's redirect_uri allowlist; loopback callbacks (http://localhost, used by most CLI clients) always are.

Add a remote MCP server entry to your Claude Code configuration (.claude/settings.json or via /mcp add). As of this writing, clients typically use a config like:

{
"mcpServers": {
"perspective": {
"type": "http",
"url": "https://api.perspective.co/mcp"
}
}
}

To use a specific scope:

{
"mcpServers": {
"perspective-funnels": {
"type": "http",
"url": "https://api.perspective.co/mcp/funnel-build"
}
}
}

Desktop DXT​

The perspective-mcp DXT package bundles a small Node.js binary (dist/stdio.js) that runs locally and proxies MCP messages to the hosted server over HTTPS. All tool logic stays server-side, so server deployments update behavior without requiring a DXT rebuild.

Install​

  1. Download the perspective-mcp DXT from the Perspective website or the Claude Desktop extension library.
  2. In Claude Desktop, open Extensions (or Settings → Extensions) and install the downloaded .dxt file.

Configure​

After installation, Claude Desktop prompts you for your API key. Enter the PERSPECTIVE_API_KEY value from your Perspective account. The DXT manifest maps this to the PERSPECTIVE_API_KEY environment variable used by the binary.

See Authentication → API Keys and Getting an API key for where to find your key.

How it works​

The DXT binary acts as a transparent proxy:

Claude Desktop ←stdio→ dist/stdio.js ←HTTPS→ https://api.perspective.co/mcp

The binary connects to the remote server with the x-perspective-api-key header set to your API key. All MCP tool definitions live on the server, so you always get the latest tools without updating the DXT.

DXT manifest reference​

FieldValue
Package nameperspective-mcp
Display namePerspective
Entry pointdist/stdio.js
User configapi_key → PERSPECTIVE_API_KEY
PlatformsmacOS, Windows
Requires Node.js≥ 18

Next steps​