fix: MCP docs say VS Code and Perplexity can connect

[sonpiaz]

cms#505 (merged 0fe16b2, tag v3.16.112) lets VS Code and Perplexity register as MCP clients. This updates the MCP page and the hosted MCP changelog entry.

Changes

• api-reference/mcp.mdx: VS Code tab in the install CodeGroup + a VS Code bullet; new Perplexity section; "Which apps can connect" lists every allowed return address and the real registration error; frontmatter description names VS Code and Perplexity.
• changelog/hosted-mcp-server.mdx: adds VS Code and Perplexity to the client list.

Sources

• Allowed hosts and pinned paths: affiliate-cms v3.16.112:src/mcp/redirect-allowlist.ts (VENDOR_REDIRECT_HOSTS, PINNED_PATHS). enterprise.perplexity.ai is not in the set, so the page says so.
• Error text: src/mcp/provider.ts (cms#505), error_description = 'redirect_uris must be https on a supported AI app host, or http on 127.0.0.1 or localhost'.
• Live on prod: GET https://mcp.affitor.com/.well-known/oauth-authorization-server/oauth now returns scopes_supported: ["read"] (the same PR's http.ts change; before it listed openid).
• VS Code format: code.visualstudio.com/docs/copilot/customization/mcp-servers (top-level servers, "type": "http", .vscode/mcp.json or the user profile mcp.json, MCP: Add Server).
• Perplexity steps and labels: Perplexity Help Center, "Adding custom remote connectors" (Plugins / Customize › Connectors, Add custom › Connector › Add MCP connector, Remote, MCP Server URL, Authentication OAuth, Transport Streamable HTTP, Add, click card to authenticate; DCR means no client id/secret).
• No install line was run against prod (skill rule).

Checks

npm run build && check-agent-surface && check-docs-host && check-docs-host-http pass locally. No media needed.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
affitor-docs	Ready	Preview	Oct 17, 2026 3:14am UTC