GameFlash / protocol

Your newsroom,
in the loop.

Connect GameFlash to an MCP client to search the newsroom, read dispatches, and—depending on your role—publish or manage content without leaving your workflow.

Remote Streamable HTTP transport

Personal tokens inherit your GameFlash role

Tokens can be revoked at any time in your account

Codex

Add the server to your Codex configuration file at~/.codex/config.toml, then restart Codex or begin a new task.

toml

[mcp_servers.gameflash]
url = "https://gameflash.net/api/mcp"

[mcp_servers.gameflash.http_headers]
Authorization = "Bearer YOUR_MCP_TOKEN"

Keep the token local. Do not commit it into a repository or a shared configuration file.

Claude Code

Run this in your terminal to add GameFlash for the current project. Add --scope user if you want it available in every project.

shell

claude mcp add --transport http gameflash \
  https://gameflash.net/api/mcp \
  --header "Authorization: Bearer YOUR_MCP_TOKEN"

Verify the connection with claude mcp list, then open Claude Code and ask it to search GameFlash.

Prefer JSON configuration?

Add this server object to your .mcp.json. Use an environment variable for a shared project configuration rather than placing a real token in the file.

json

{
  "mcpServers": {
    "gameflash": {
      "type": "http",
      "url": "https://gameflash.net/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_MCP_TOKEN"
      }
    }
  }
}

ChatGPT

ChatGPT can connect to remote MCP apps in Developer Mode, but its custom-connector flow expects OAuth or an unauthenticated endpoint. The GameFlash server currently uses personal Bearer tokens, so it cannot be connected directly to ChatGPT yet.

Use Codex or Claude Code today.

Once GameFlash adds OAuth, you will be able to create it as a custom app in ChatGPT's Apps settings and authenticate through the normal connection flow.

Another MCP client

Configure a remote HTTP / Streamable HTTP server using the endpoint and header below. The client must send the Authorization header with every request.

Endpoint: https://gameflash.net/api/mcp
Transport: Streamable HTTP
Header: Authorization: Bearer YOUR_MCP_TOKEN

Hand it to an agent

Copy this prompt into Codex, Claude Code, or another coding agent. It gives the agent the server details and keeps token handling explicit and local.

Agent handoff

Set up the GameFlash MCP server in the MCP-capable client available in this environment.

Server details:
- Name: gameflash
- Transport: Streamable HTTP
- URL: https://gameflash.net/api/mcp
- Required header: Authorization: Bearer YOUR_MCP_TOKEN

Instructions:
1. Identify the current client and use its native configuration method. For Codex, add the server to ~/.codex/config.toml. For Claude Code, use `claude mcp add --transport http` or its native configuration. For another MCP client, use its remote HTTP server configuration.
2. Ask me for a personal GameFlash MCP token if one is not already available through an approved secret store or environment variable. Do not invent a token.
3. Never put the token in a Git repository, project file, commit, terminal output, chat response, or any shared configuration. Keep it only in the client’s private user-level configuration or approved secret storage.
4. Verify the connection by listing the server’s tools or making one harmless read-only request. Do not create, edit, publish, or delete GameFlash content during setup.
5. Tell me which client and local configuration path you used, confirm whether verification passed, and never repeat the token in your final response.

If the current client is ChatGPT custom connectors, stop and explain that this GameFlash server currently uses personal Bearer tokens; ChatGPT’s direct connector flow requires OAuth or an unauthenticated endpoint.

First prompt

“Search GameFlash for the latest RPG news.”

Create an MCP token