Skip to main content

Getting Started

Use the GameDiscoverCo Pro MCP server when you need game market analytics, competitive research, genre sizing, subscription catalog context, or publisher benchmarking inside an AI assistant.

Setup Instructions​

Requirements​

  • An active GameDiscoverCo Pro account.
  • MCP access enabled for your account.
  • An MCP client that supports remote MCP servers, OAuth, or a local mcp-remote bridge.

General​

The GameDiscoverCo Pro MCP server is centrally hosted and uses Streamable HTTP. For clients that support authenticated remote MCP servers, use this address:

https://api.gamediscover.co/mcp
FieldValue
NameGameDiscoverCo
Server URLhttps://api.gamediscover.co/mcp
AuthenticationOAuth
AccessRead-only
TransportStreamable HTTP

Most clients should use OAuth. When you add the MCP server, your client opens a GameDiscoverCo login flow. Sign in with the email address associated with your GameDiscoverCo Pro subscription.

GameDiscoverCo is not currently listed in third-party app or connector directories. Use the manual/custom MCP server setup flow in clients that support it, or use mcp-remote for clients that need a local bridge.

After connecting, ask:

What tools are available from GameDiscoverCo?

Claude​

GameDiscoverCo is not currently listed in Claude's connector directory. If your Claude plan or workspace supports adding a custom remote MCP server, open Settings, go to Connectors, and add a custom connector with this MCP server URL:

https://api.gamediscover.co/mcp

Complete the GameDiscoverCo login flow when prompted.

Claude Code​

Run:

claude mcp add --transport http gamediscoverco https://api.gamediscover.co/mcp

Then open a Claude Code session, run /mcp, and follow the browser login flow.

Codex​

The setup steps are the same for the Codex CLI and IDE extension because they share MCP configuration.

Configuration via CLI:

codex mcp add gamediscoverco --url https://api.gamediscover.co/mcp

If your Codex install requires remote MCP to be explicitly enabled, add this to ~/.codex/config.toml:

[features]
experimental_use_rmcp_client = true

Then run:

codex mcp login gamediscoverco

Configuration through ~/.codex/config.toml:

[features]
experimental_use_rmcp_client = true

[mcp_servers.gamediscoverco]
url = "https://api.gamediscover.co/mcp"

Then run codex mcp login gamediscoverco to complete authentication.

ChatGPT​

GameDiscoverCo is not currently published as a ChatGPT app. If your ChatGPT plan or workspace supports custom MCP apps, open Settings, go to Apps, and add a custom MCP server or app.

Use:

https://api.gamediscover.co/mcp

If the custom app is available in your chat, select it before asking questions so the model knows to use the MCP server.

Microsoft Copilot​

In Copilot Studio, open your agent, go to Tools, and add a new Model Context Protocol tool.

Use:

https://api.gamediscover.co/mcp

Select OAuth and dynamic discovery if prompted, then complete the GameDiscoverCo login flow.

Cursor​

If your Cursor setup does not support authenticated remote MCP servers directly, use mcp-remote as a local bridge:

{
  "mcpServers": {
    "gamediscoverco": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.gamediscover.co/mcp"]
    }
  }
}

Visual Studio Code​

Clients that do not support remote MCP natively can usually connect through mcp-remote.

{
  "mcpServers": {
    "gamediscoverco": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.gamediscover.co/mcp"]
    }
  }
}

In VS Code, use MCP: Add Server, select Command (stdio), and enter:

npx mcp-remote https://api.gamediscover.co/mcp

Name the server GameDiscoverCo, then start it from MCP: List Servers.

Windsurf​

Open Windsurf settings, find the MCP server configuration, and add:

{
  "mcpServers": {
    "gamediscoverco": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.gamediscover.co/mcp"]
    }
  }
}

Zed​

Open Zed settings and add:

{
  "context_servers": {
    "gamediscoverco": {
      "source": "custom",
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.gamediscover.co/mcp"],
      "env": {}
    }
  }
}

Others​

If your client asks for a command and arguments separately, use:

FieldValue
Commandnpx
Arguments-y mcp-remote https://api.gamediscover.co/mcp
EnvironmentNone

The first connection should open a browser login flow.

FAQ​

How Long Do Access Tokens Last?​

Access tokens are valid for 60 days. Refresh tokens are not currently issued, so your client may ask you to reconnect or sign in again when the access token expires.

The 60-day token lifetime is separate from short-term anti-abuse request logs. Request metadata for the MCP service may be retained for 7 days for security and abuse prevention.

Login Works But Tools Are Unavailable​

Your account may not have MCP access enabled. Email contact@gamediscover.co so we can confirm your account permissions.

Can I Authenticate With A Bearer Token?​

Some developer tools can call the MCP endpoint with a GameDiscoverCo-issued JWT bearer token instead of running OAuth. The token must be signed by GameDiscoverCo and include MCP access for the user or API identity.

{
  "mcpServers": {
    "gamediscoverco": {
      "type": "http",
      "url": "https://api.gamediscover.co/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Firebase ID tokens, random API keys, and client-generated tokens are not accepted. For most end-user clients, use OAuth instead.

OAuth Cache Or CLI Login Is Stuck​

For local clients using mcp-remote, stale cached credentials can cause repeat login failures. Clear the local MCP auth cache, then reconnect:

rm -rf ~/.mcp-auth

If the problem continues, make sure your local Node.js version is current enough for the MCP client you are using.