RECONNED API

API keys are for scripts, CLI tools, and server-to-server integrations with the REST API and MCP server. If you're connecting an AI assistant to our MCP server you don't need one — see the OAuth section below. You can create and manage your keys from your account settings.

Our REST API is fully documented using the OpenAPI 3.1 specification. Browse the interactive API reference to explore all available endpoints, request schemas, and response types.

RECONNED provides a Model Context Protocol (MCP) server that lets AI assistants and tools interact with the platform. The MCP server exposes tools for searching clubs, events, and players, as well as managing your RECONNED data.

Endpoint:

Authentication:

The easiest way to connect is OAuth — no API key required. MCP clients that support OAuth (claude.ai, Claude Code, ChatGPT, Cursor, and most others) discover our authorization server automatically: just add the server URL and you'll be prompted to sign in with your RECONNED account.

For scripted or headless use you can authenticate with an API key instead, passed via the X-API-Key header or the Authorization: Bearer header.

Client configuration (OAuth):

{
  "mcpServers": {
    "reconned": {
      "url": "https://reconned.com/api/mcp"
    }
  }
}

Client configuration (API key):

{
  "mcpServers": {
    "reconned": {
      "url": "https://reconned.com/api/mcp",
      "headers": {
        "X-API-Key": "your-api-key"
      }
    }
  }
}

Here are some example requests to get you started with the RECONNED API.