Visiting Media MCP Server

This is an MCP server. It exposes read-only tools backed by the Visiting Media API. You don't open it directly in a browser; connect from an MCP client.

Connect from Claude Code (CLI)

Claude Code launches the OAuth flow in your browser on first use, then stores the token in ~/.claude/. Each Claude client maintains its own token store. Authenticating via Claude Desktop does not authenticate Claude Code or vice versa.

Connect from Claude Desktop

Settings → Connectors → Add custom connector → paste https://vmp-api-mcp.qa.truetour.app/mcp as the URL. Claude Desktop runs the OAuth flow inside the app.

Connect from Cursor / Codex / VS Code Copilot

Add an entry to your MCP config pointing at https://vmp-api-mcp.qa.truetour.app/mcp with HTTP transport. The client handles the OAuth handshake on first connection.

OAuth

This server uses OAuth 2.1 with PKCE and dynamic client registration. MCP clients perform the full handshake automatically, with no API key required.

Authorization server: https://vmp-api.qa.truetour.app
Protected resource: https://vmp-api-mcp.qa.truetour.app/mcp
Metadata: https://vmp-api.qa.truetour.app/.well-known/oauth-authorization-server

API key compatibility

Service integrations can also authenticate by sending a Visiting Media API key in the X-API-Key header on POST /mcp requests.

I'm already connected but Claude says I'm not

Each Claude product (Desktop, Code CLI, claude.ai web) keeps its own MCP token store. If you authenticated in one and another says you're not connected, run the connect command above in that specific client. There's no shared session.