MCP Server

Claude on the web, desktop and mobile.

1. In Claude, open Customize → Connectors, click Add, then Add custom connector.
2. Name it stat-api and paste this URL as the remote MCP server URL:

   https://api.stat-api.com/mcp

3. Under Authentication, choose Sign in when needed, then click Add. Claude preselects “No sign-in”, because the catalog tools work without an account.
4. Ask Claude for data. The first data tool shows Connect: click it, sign in to stat-api.com (or create a free account) in the window that opens, and click Allow.

Team and Enterprise plans: an owner adds the connector once in Organization settings → Connectors, and each member then clicks Connect and signs in with their own STAT-API account.

claude mcp add --transport http stat-api https://api.stat-api.com/mcp

Then run /mcp in Claude Code, pick stat-api and choose Authenticate. Your browser opens the STAT-API sign-in; click Allow.

With an API key instead of the sign-in:

claude mcp add --transport http stat-api https://api.stat-api.com/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

The button opens Cursor with the STAT-API server filled in: confirm the install. Cursor supports MCP sign-in: when it asks, sign in to stat-api.com and click Allow. To use an API key instead, add the headers entry from Other clients to the STAT-API server in Cursor's mcp.json.

Add https://api.stat-api.com/mcp as a remote (streamable HTTP) MCP server. A client that supports MCP sign-in opens the STAT-API sign-in the first time a data tool needs it. A client that takes request headers can send an API key instead (clients nest this entry under their own mcpServers key):

{
  "url": "https://api.stat-api.com/mcp",
  "headers": { "Authorization": "Bearer YOUR_API_KEY" }
}