Putting the language in the path means one hosted instance serves four SDKs and changing yours is a one-word edit. It also means a typo returns an HTTP 400 rather than silently serving the wrong reference, which is the better failure. The `required permissions` field on `describe-symbols` is the detail that saves time later — generated code that compiles but lacks the permission is the failure this avoids.
A hosted reference server for the AccelByte Extend SDK. Instead of letting a model guess at SDK signatures, it serves the actual symbols — functions and models with their parameters, fields, imports, return types and required permissions — so generated code matches the SDK. Language is chosen by URL path, and one instance serves all four.
- `search-symbols` finds SDK symbols by name, tags or description with fuzzy matching, returning a paginated list of summaries
- `describe-symbols` returns full detail for specific symbols by ID — fields, parameters, imports, example usage, return type and required permissions
- `create-extend-app`, a prompt that clones an Extend app template and opens it, in a Dev Container where one is available
- Four languages selected by URL path: `/extend-mcp/csharp`, `/extend-mcp/go`, `/extend-mcp/java`, `/extend-mcp/python`
- Switching language later means changing the trailing path segment, nothing else
- The base path with no language serves the deployment's configured default
No sign-in and nothing to install — the data is read-only SDK reference. You need the host of your organisation's deployment, which your AccelByte administrator supplies; the URL is that host followed by `/extend-mcp/{language}`. Transport is Streamable HTTP, so clients that support HTTP connect directly; stdio-only clients bridge through `mcp-remote`, which needs Node.js 18+ with `npx`. Package `extend-sdk-mcp-server`, version 2026.4.0. An unknown language in the path returns HTTP `400`, which is the first thing to check when tool calls fail.