Skip to main content

Getting Started

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

Requirements​

  • An active GameDiscoverCo Pro account with MCP access enabled.
  • A compatible remote MCP client with browser-based OAuth.

Connection Settings​

Use these settings when adding a custom MCP server or connector:

Server URL:

https://api.gamediscover.co/mcp
  • Name: GameDiscoverCo
  • Transport / Type: Streamable HTTP (sometimes called HTTP or remote), not STDIO or legacy SSE.
  • Authentication: OAuth, using the browser sign-in flow.
  • Access: Read-only.

Leave Bearer token env var, Headers, Headers from environment variables, and advanced client credentials blank. No manual API key, client ID, or client secret is needed for the OAuth setup.

Sign in with the GameDiscoverCo account that has MCP access and authorize the connection. Only approve clients you trust. Enable the server's tools in your conversation, then ask:

What tools are available from GameDiscoverCo?

If you're already signed in to the main GameDiscoverCo app in the same browser, sign-in is skipped automatically. Check the account and client, then choose Connect. You do not need to enter your password again. A separate browser profile or an AI app's embedded browser may not have your app session.

Otherwise, use the normal GameDiscoverCo sign-in screen: enter your email or username and choose Sign in. Email users receive a sign-in link, with a password option on the next screen; demo usernames continue to password sign-in. Open the email on the same device, choose Continue to GameDiscoverCo, check the client and account shown, then choose Connect. The link expires after 30 minutes and works once. If it expires or the client times out, restart the connection from your AI app. Email sign-in does not create an account or grant MCP access.

You do not need to find GameDiscoverCo in an app's connector directory. Use its custom-server setup, or ask it to add the server where conversational setup is supported.

Choose Your App​

The official guides below own each app's current setup steps. Use our connection settings above rather than API keys or credentials shown in examples for other services. Availability depends on app version, subscription, and workspace policy. These links describe documented capabilities, not successful GameDiscoverCo authentication and tool-call tests in every client.

Claude​

Recommended. Follow Claude's official custom connector guide. Add the remote connector on web or desktop; connected services are also available on mobile and in Cowork. Free accounts are limited to one custom connector. Team and Enterprise organizations may require an owner or authorized administrator to add it first.

ChatGPT Desktop​

Follow OpenAI's desktop and Codex MCP guide. In the Plugins interface shown by current desktop versions, use Plugins → Add → Add MCP server, choose Streamable HTTP, then Save and Authenticate when prompted. Other versions expose MCP configuration under Settings; follow OpenAI's guide for your version.

You can add the server directly; creating a web plugin first is not required.

ChatGPT Web​

Follow OpenAI's ChatGPT MCP connection guide to create and install a custom plugin, authenticate with GameDiscoverCo, and select it in a new conversation. This hosted-plugin flow is different from configuring a local desktop or Codex host. Account and workspace policies apply.

Codex​

Follow OpenAI's Codex MCP guide. In the Plugins interface, use Add → Add MCP server and select Streamable HTTP, not STDIO. Leave the bearer-token and header fields blank and complete browser authentication.

Codex CLI and the IDE extension also support remote MCP with OAuth and share configuration on the same Codex host. Follow the guide's configuration steps, then use codex mcp login <server-name> to sign in. No experimental feature flag is required by the current guide.

Muse​

Ask Muse to add the connection in chat:

Add the GameDiscoverCo MCP server at https://api.gamediscover.co/mcp using Streamable HTTP and browser-based OAuth. Help me sign in and enable its tools.

Follow its sign-in and approval prompts. Meta's official connector guide documents asking Muse to create custom connectors for services outside its directory. A directory listing is not required. Meta does not review these custom connectors, so review what you authorize.

Muse Code is a separate developer client; see Developer Tools.

Grok Bot​

Ask your bot in chat:

Add the GameDiscoverCo MCP server at https://api.gamediscover.co/mcp using Streamable HTTP and browser-based OAuth. Help me sign in and enable its tools.

Confirm the connection details and complete the sign-in and approval prompts. Cursor support confirms this conversational setup, including public HTTPS MCP endpoints with Streamable HTTP. Tools become available from your next message; a settings form or catalog listing is not required. See Grok Bot's plugin guide for managing connections.

Grok Bot is separate from Grok chat and Grok Build. The complete GameDiscoverCo OAuth/tool-call flow has not been tested in this documentation review.

Cursor​

Follow Cursor's official MCP guide. Cursor supports Streamable HTTP and OAuth with dynamic client registration natively: add the remote URL and complete browser sign-in. A local proxy such as mcp-remote is not required. Do not copy static client credentials or API-key headers from other integrations.

Perplexity​

Follow Perplexity's custom remote connector guide. Select Remote, Streamable HTTP, and OAuth. Discovery and dynamic registration avoid manually supplying client credentials. Organization members may need an administrator to enable custom connectors; check the guide for current account availability.

Gemini Web And Mobile​

Follow Google's custom apps guide. Add the connection on Gemini web; it is then also available on mobile. Google documents dynamic client registration, so leave advanced client credentials blank.

Availability: currently US users aged 18+, in English, with a personal Google Account and Keep Activity enabled. Work and school accounts are excluded by the current guide.

GameDiscoverCo compatibility is not yet verified end to end. Google's guide documents custom MCP and registration, but does not specify transport and PKCE behavior. Gemini CLI is a separate product with its own guide below.

Grok​

Grok documents custom remote MCP connectors with a server URL and authentication. Business and Enterprise organizations require an administrator to provision connectors.

Compatibility not yet verified: that guide does not specify transport or OAuth registration/PKCE details needed to confirm GameDiscoverCo compatibility. Use our connection settings if your version offers them, but treat this as an unverified option. Grok Build is a separate developer product.

Microsoft Copilot​

For Copilot Studio agents, follow Microsoft's MCP connection guide. Select OAuth 2.0 → Dynamic discovery, not manual client credentials. Generative orchestration and organization policies must allow MCP.

This is an agent-builder integration, not a claim that consumer Copilot chat accepts arbitrary MCP URLs. GitHub Copilot in VS Code is a separate product with native remote HTTP and OAuth support; see its guide below.

Developer Tools​

Use the same server URL, Streamable HTTP, and browser OAuth settings with these clients. Follow their official guides for configuration and account availability:

  • Claude Code — remote HTTP; authenticate with /mcp.
  • Codex CLI and IDE — remote HTTP and OAuth; sign in with codex mcp login <server-name>.
  • GitHub Copilot in VS Code — native HTTP and OAuth; no local bridge required.
  • OpenCode — remote servers with automatic OAuth discovery and registration.
  • Gemini CLI — Streamable HTTP via httpUrl, with OAuth discovery and dynamic registration; authenticate with /mcp auth. The site announces migration of unpaid-tier and Google One users to Antigravity CLI; check current availability rather than assuming the same setup applies there.
  • Grok Build — remote HTTP and automatic browser OAuth; separate from Grok chat and Grok Bot.
  • Muse Code — remote Streamable HTTP, OAuth 2.1 and automatic registration; sign in with muse mcp login <server>. Separate from consumer Muse.
  • Windsurf and Zed — consult their current MCP guides and check support for the authentication requirements below. GameDiscoverCo compatibility has not been verified here.

Other Clients And Local Bridges​

Compatible remote clients need OAuth authorization code flow with S256 PKCE and dynamic client registration or Client ID Metadata Documents (CIMD). Callback URLs must use HTTPS, loopback HTTP for local apps, or a native-app URI scheme.

For clients with only local STDIO support, a remote-MCP bridge such as mcp-remote can provide the remote connection. Follow its current guide and your client's configuration format; do not use another app's JSON configuration unchanged. Prefer native remote HTTP and OAuth whenever available.

FAQ​

How Long Does A Login Last?​

Clients refresh access automatically. Sign in again when prompted. Refresh sessions expire after 90 days without a successful refresh, or after one year even with continued use. Older clients that do not refresh may need a new login sooner.

Session lifetimes are separate from anti-abuse request logs. Request metadata 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. It must be signed by GameDiscoverCo and include MCP access for the user or API identity. Firebase ID tokens, random API keys, and client-generated tokens are not accepted. For end-user setup, use OAuth and leave manual bearer-token fields blank.

OAuth Cache Or CLI Login Is Stuck​

See Troubleshooting for reconnecting, stale local bridge credentials, missing tools, and account access issues.