← agents.techspike.tv

Connect an MCP client

Authentication is automatic. The first time your client connects, a browser window opens for Auth0 login; the client stores and refreshes the token transparently. You never handle tokens.

Closed beta — only @or13.io and @tradeverifyd.com can log in.

Claude Code (CLI)

claude mcp add --transport http agents https://agents.techspike.tv/api/mcp

Claude Code discovers the OAuth flow from the server's WWW-Authenticate challenge and completes PKCE in your browser. Verify with claude mcp list; inside a session, type /mcp.

Gemini CLI

Add to ~/.gemini/settings.json (per-user) or .gemini/settings.json at the repo root.

{
  "mcpServers": {
    "agents": {
      "httpUrl": "https://agents.techspike.tv/api/mcp"
    }
  }
}

GitHub Copilot (VS Code)

Add to .vscode/mcp.json at the workspace root.

{
  "servers": {
    "agents": {
      "type": "http",
      "url": "https://agents.techspike.tv/api/mcp"
    }
  }
}

Open Copilot Chat in Agent mode (the regular Chat surface doesn't load MCP servers).

How auth works

The MCP server advertises its OAuth requirements via /.well-known/oauth-protected-resource (RFC 9728) and a WWW-Authenticate challenge on every 401. CIMD-aware clients discover the Auth0 tenant, register against our hosted client.json metadata document, and complete PKCE with loopback redirects — no client secret, no token handling by you.