AGS API

Exposes AccelByte APIs as MCP tools, enabling semantic search, authenticated API execution, and token information for AI assistants.

typescript

GitHub Stars

typescript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "accelbyte-ags-api-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "--interactive",
        "--env",
        "AB_BASE_URL=https://yourgame.accelbyte.io",
        "--env",
        "OAUTH_CLIENT_ID=your-client-id",
        "--env",
        "OAUTH_CLIENT_SECRET=your-client-secret",
        "ghcr.io/accelbyte/ags-api-mcp-server:2025.9.0"
      ],
      "env": {
        "AB_BASE_URL": "https://yourgame.accelbyte.io",
        "OAUTH_CLIENT_ID": "your-client-id",
        "OAUTH_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

You can empower AI assistants to access AccelByte Gaming Services APIs by running a dedicated MCP server in a container. This MCP server exposes AccelByte APIs as discoverable tools, supports semantic API search, executes authenticated requests, and can provide token information to your assistants.

How to use

Configure your AI assistant to connect to the running MCP server, then use the built-in tools to search APIs, inspect details, and execute requests. The server handles authentication, request validation, and result formatting, so your assistant can focus on intent and response quality.

How to install

Prerequisites you need before starting:

Docker installed and running
AccelByte environment URL and credentials for authentication (AB_BASE_URL, OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET)

# Example: pull and run the MCP server container with required environment variables
# Replace placeholders with your actual values
AB_BASE_URL=https://yourgame.accelbyte.io
OAUTH_CLIENT_ID=your-client-id
OAUTH_CLIENT_SECRET=your-client-secret

docker run --rm --interactive \
  --env AB_BASE_URL=$AB_BASE_URL \
  --env OAUTH_CLIENT_ID=$OAUTH_CLIENT_ID \
  --env OAUTH_CLIENT_SECRET=$OAUTH_CLIENT_SECRET \
  ghcr.io/accelbyte/ags-api-mcp-server:2025.9.0

Additional setup for each client

If you use editor integrations, you will configure the MCP server in your editor or tool following the provider-specific instructions. The same Docker command and environment variables apply to all clients.

Available tools

get_token_info

Retrieves information about the currently authenticated user and token, including user ID, namespace, roles, and token expiration.

search-apis

Search AccelByte API operations by description, tags, path, method, or service name to discover relevant endpoints.

describe-apis

Provide detailed information about a specific API operation, including parameters, schemas, authentication requirements, and example requests.

run-apis

Execute authenticated API requests against AccelByte endpoints with automatic validation and formatted responses.

run-workflow

Access predefined workflows and prompts to automate common sequences against AccelByte APIs.

Built by

VeilStrat

AI signals for GTM teams