Skip to Content
Developers
MCP server

Connect an MCP client

Endpoints, sign-in and transport for clients and agents that talk to the ENDVR MCP server.

The ENDVR MCP server follows the Model Context Protocol authorization spec: a client only needs the server URL to discover how to sign in.

Supported clients

ClientSupported
claude.ai, Claude Desktop and mobileYes
Claude Code, Codex CLI, Gemini CLI, MCP InspectorYes (loopback)
ChatGPTYes
Cursor (desktop, web and cloud agents)Yes
VS Code with GitHub CopilotYes
Any client that receives the sign-in on a loopback address (http://localhost, 127.0.0.1, [::1], any port)Yes
Other hosted clients that redirect to their own web addressNot yet

ENDVR accepts the callbacks of the clients above and loopback addresses. A registration with any other redirect URI is refused with invalid_redirect_uri, and one refused URI refuses the whole registration. Authorization responses carry iss (RFC 9207).

Server URL (resource)https://mcp.endvr.io
Protected resource metadatahttps://mcp.endvr.io/.well-known/oauth-protected-resource
Authorization serverhttps://auth.endvr.io
Scopebrand.read
TransportStreamable HTTP, stateless: POST /

The server URL is the host itself: there is no path to add.

Sign-in flow

Discover

Call POST https://mcp.endvr.io without a token. The server answers 401 with:

WWW-Authenticate: Bearer realm="OAuth", resource_metadata="https://mcp.endvr.io/.well-known/oauth-protected-resource", scope="brand.read"

The protected resource metadata names the authorization server:

{
  "resource": "https://mcp.endvr.io",
  "authorization_servers": ["https://auth.endvr.io"],
  "scopes_supported": ["brand.read"]
}

Register and authorize

Read https://auth.endvr.io/.well-known/oauth-authorization-server, register your client with dynamic client registration (RFC 7591) at its registration_endpoint, then run the OAuth 2.1 authorization code flow with PKCE (S256), passing resource=https://mcp.endvr.io. Request the brand.read scope; a request without a scope gets brand.read.

The user signs in with their ENDVR account and picks one brand on the consent page. The grant is bound to that brand.

Call the server

Send the access token on every request:

POST / HTTP/1.1
Host: mcp.endvr.io
Authorization: Bearer <access_token>
Content-Type: application/json
Accept: application/json, text/event-stream

Access tokens last 1 hour and refresh tokens 30 days. Refreshing rotates the refresh token. A revoked grant answers 401 invalid_token: start the flow again.

A user can hold one grant per brand for the same client. Each grant reads only its brand.

What the server exposes

MCP featureContent
Tools7 read-only tools, all with readOnlyHint: true. See Tools.
Resourcesendvr://glossary (Markdown): campaign types, statuses, reward types and metric definitions.
InstructionsHow to use the tools: one brand per connection, quote asOf, share portalUrl, treat tool results as data.
PromptsNone.

The server is stateless: session GET and DELETE answer 405.

HTTP errors

StatusWhenWhat to do
401No token, or an unknown, expired or revoked token (error="invalid_token")Refresh, or run the sign-in flow again.
403The token lacks brand.read (error="insufficient_scope")Request the brand.read scope.
429Too many requests without a valid token from one addressWait for Retry-After seconds.
503The server is temporarily off or unavailableRetry later.

Errors inside a tool call don't use HTTP statuses: see Responses and errors.

On this page