Connect your MCP client

Codex

export VIRALSPY_API_KEY='vsp_live_…'
codex mcp add viralspy \
  --url https://api.viralspy.com/mcp \
  --bearer-token-env-var VIRALSPY_API_KEY

Claude Code

export VIRALSPY_API_KEY='vsp_live_…'
claude mcp add-json viralspy \
  '{"type":"http","url":"https://api.viralspy.com/mcp","headers":{"Authorization":"Bearer ${VIRALSPY_API_KEY}"}}'

The single quotes preserve the environment placeholder instead of writing the key into Claude's configuration.

OAuth clients

OAuth 2.1 with PKCE is available to explicitly registered clients during beta. Public dynamic client registration is disabled. Integration developers can contact support with their client metadata and exact redirect URIs; after registration, the browser consent screen shows the organisation and requested capabilities before approval.

Generic Streamable HTTP configuration

{
  "mcpServers": {
    "viralspy": {
      "url": "https://api.viralspy.com/mcp",
      "headers": {
        "Authorization": "Bearer ${VIRALSPY_API_KEY}"
      }
    }
  }
}

The client must support Streamable HTTP and Authorization: Bearer. OAuth clients must also support Protected Resource Metadata discovery and PKCE. Never put credentials in the server URL.