MCP server

The GAMPEON MCP server lets AI assistants work with GAMPEON through the Model Context Protocol. It is the tool layer behind Build with AI.

Endpoints

URL	Authentication	Tools
https://api.gampeon.com/mcp/docs	none	Docs, Lua API, resource templates and checks, public marketplace and projects
https://api.gampeon.com/mcp	Bearer token (gpat_…)	All of the above plus account tools

Transport: Streamable HTTP. The server is stateless and supports the MCP revisions 2026-07-28, 2025-11-25 and 2025-06-18.

Plain JSON docs search

The GAMPEON portal searches these docs through two plain JSON endpoints on the same server. They need no sign-in and no MCP client.

URL	Returns
GET https://api.gampeon.com/mcp/search?q=<text>&limit=<1-20>	The best matching pages, ranked like the search_docs tool
GET https://api.gampeon.com/mcp/pages	Every page with title, description, status and section, without the page text

Both allow 120 requests per minute per IP. Browsers can call them only from the GAMPEON portal (CORS). For anything else, use the MCP tools or /llms.txt.

How it works

The MCP server is a thin client of the GAMPEON web API. It has no database access and no rights of its own: every call goes to the API with your token, and the API checks the token’s scopes. The assistant can never do more than you, and never more than the token allows.

AI assistant ──MCP──▶ GAMPEON MCP server ──HTTPS + your token──▶ GAMPEON API

Authentication

• Access tokens (now): create one in the portal and send it as Authorization: Bearer gpat_….
• OAuth 2.1 (planned): sign in from Claude or ChatGPT with your GAMPEON account. Uses authorization code with PKCE, Client ID Metadata Documents and protected resource metadata (RFC 9728), as the MCP specification requires.

See Tools for the tool list and Security for the security model.