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.
claude mcp add visitingmedia --transport http http://vmp-api-mcp.demo.truetour.app/mcp
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 auth Claude Code or vice versa.
Settings → Connectors → Add custom connector → paste http://vmp-api-mcp.demo.truetour.app/mcp as the URL. Claude Desktop runs the OAuth flow inside the app.
Add an entry to your MCP config pointing at http://vmp-api-mcp.demo.truetour.app/mcp with HTTP transport. The client handles the OAuth handshake on first connection.
This deployment is configured for API-key authentication. Set the X-API-Key header on POST /mcp requests.
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.
Need help? Email support@visitingmedia.com.