Remote MCP

SalesTouch exposes a remote MCP server directly from the main Next.js application:

https://salestouch.io/api/mcp

This is available explicitly through --mcp.

OAuth-first setup

The preferred setup flow is:

pnpm salestouch setup --claude --mcp --login

That installs:

• the remote MCP configuration
• the SalesTouch rule
• the SalesTouch skill

Agent snippets

Claude:

{
  "mcpServers": {
    "salestouch": {
      "type": "http",
      "url": "https://salestouch.io/api/mcp"
    }
  }
}

Cursor:

{
  "mcpServers": {
    "salestouch": {
      "url": "https://salestouch.io/api/mcp"
    }
  }
}

Codex:

[mcp_servers.salestouch]
url = "https://salestouch.io/api/mcp"

OpenCode:

{
  "mcp": {
    "salestouch": {
      "type": "remote",
      "url": "https://salestouch.io/api/mcp",
      "enabled": true
    }
  }
}

API key fallback

If your client supports custom headers, you can install a non-interactive setup:

pnpm salestouch setup --cursor --mcp --api-key st_...

Supported fallback configs today:

• Claude: type: "http" plus headers
• Cursor: url plus headers
• OpenCode: oauth: false plus headers

Codex remains OAuth-only in the generated setup until custom header injection is documented for remote MCP in config.toml.

Local fallback

If you explicitly want stdio instead of the remote server:

pnpm salestouch setup --claude --mcp --local-mcp --login
pnpm salestouch mcp serve