home / mcp / ags extend sdk mcp server

AGS Extend SDK MCP Server

Provides access to Extend SDK symbols, symbol details, and app templates via an MCP interface to accelerate Extend SDK development.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "accelbyte-ags-extend-sdk-mcp-server": {
      "url": "http://localhost:3000/",
      "headers": {
        "PORT": "3000",
        "LOG_LEVEL": "info",
        "TRANSPORT": "http",
        "CONFIG_DIR": "config/go",
        "ALLOWED_ORIGINS": "https://example.com"
      }
    }
  }
}

You can access AGS Extend SDK functions and models through an MCP server that exposes search and describe tools plus a scaffold for Extend app projects. This server lets AI coding assistants ask questions, locate symbols, and generate Extend SDK code by providing a consistent programmatic interface.

How to use

Connect to the MCP server from your MCP client to discover Extend SDK symbols, fetch detailed symbol information, and create Extend app templates. Use the available tools to search by name or tags, describe specific symbols by their IDs, and start a new Extend app project from a predefined template. When you run prompts, the server returns structured results that you can feed back into your coding workflow.

How to install

Prerequisites you need before starting are a Docker runtime and a development environment that can run an MCP client. You will run two alternative transports: STDIO (default) and streamable HTTP.

# Alternative 1: STDIO transport (default)
docker pull ghcr.io/accelbyte/ags-extend-sdk-mcp-server:2025.9.1

# Start the MCP server as a local STDIO transport via a container
# This example passes a Go config directory; adjust for your language as needed
```

```bash
# Alternative 2: Streamable HTTP transport
# Start the MCP server so it exposes an HTTP endpoint on port 3000
docker run -p 3000:3000 \
  -e TRANSPORT=http \
  -e PORT=3000 \
  -e CONFIG_DIR=config/go \
  -e NODE_ENV=production \
  -e LOG_LEVEL=info \
  ghcr.io/accelbyte/ags-extend-sdk-mcp-server:2025.9.1

Additional configuration and startup notes

Configure your MCP client to point to the appropriate transport. If you use STDIO, you will typically run the server in a background process or integrate it into your development workflow, then enable the dedicated MCP server in your client settings. If you use HTTP transport, ensure your client points to the server URL (for example, http://localhost:3000/).

Important: Use the image tag that matches your AGS version to avoid incompatibilities. For HTTP transport, port and environmental variables should be aligned with your project needs. For STDIO transport, provide the container run command and the CONFIG_DIR setting appropriate to your Extend SDK language.

Technical configuration examples

The following configurations illustrate how to connect your MCP client to the server using the two transport methods described above.

# HTTP transport configuration (remote HTTP endpoint)
{
  "mcpServers": {
    "extend-sdk-mcp-server": {
      "type": "http",
      "url": "http://localhost:3000/",
      "args": []
    }
  }
}
```

```json
# STDIO transport configuration (local container execution)
{
  "mcpServers": {
    "extend-sdk-mcp-server": {
      "type": "stdio",
      "name": "extend-sdk-mcp-server",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "CONFIG_DIR",
        "ghcr.io/accelbyte/ags-extend-sdk-mcp-server:2025.9.1"
      ],
      "env": {
        "CONFIG_DIR": "config/go"
      }
    }
  }
}

Notes and tips

- Start from an Extend SDK getting started sample project or an Extend app template to provide context for the server tools and improve results. - When you run the HTTP transport, the server listens on the port you configure (default 3000). - When using STDIO, ensure the CONFIG_DIR points to the language-specific config directory (for example config/go). - The server exposes a set of tools for symbol search, symbol description, and app template creation. Use them to quickly locate symbols like functions and models and to scaffold new Extend apps.

Security and troubleshooting

- Limit access to the HTTP endpoint with appropriate origin checks or network controls to prevent unauthorized use. - Check logs for the transport and server startup messages to diagnose connectivity or language runtime issues. - If you switch transports, ensure your MCP client is configured to the correct URL or local STDIO workflow and that environment variables are in place.

Available tools

search-symbols

Search for symbols (functions and models) by name, tags, or fuzzy description to quickly locate relevant Extend SDK components.

describe-symbols

Retrieve detailed information about specific symbols using their IDs to understand usage, parameters, and relationships.

create-extend-app

Provide a prompt template for creating Extend app projects, helping you scaffold new apps efficiently.