Skip to main content
The Trophy Docs MCP Server is a remote Model Context Protocol server that gives AI agents live access to Trophy documentation — guides, feature pages, API references, and OpenAPI specs. Think of it as an on-demand skill: instead of relying on the model’s training data, your agent can search and open the same docs you read on docs.trophy.so whenever it needs accurate, up-to-date detail.
Server URL

​
Why a Docs MCP?

Trophy changes: new endpoints ship, parameters evolve, and guides get updated. Agents that only use built-in knowledge risk inventing APIs, missing constraints, or shipping integrations against outdated patterns. The docs MCP keeps that context current. Before integrating a feature or explaining a payload, the agent can pull the latest docs snippet or full page and work from source of truth. Typical uses:
  • Answer “how does X work?” from published docs before writing code
  • Look up request/response shapes and auth patterns from API reference pages
  • Follow feature guides (streaks, points, leaderboards) while implementing backend events
  • Explore OpenAPI specs when the agent needs exact path or schema detail

​
How It Works

Trophy hosts a remote MCP endpoint backed by the public docs site. You install it in your MCP client; the agent gets tools to search the knowledge base and read full pages from a sandboxed docs filesystem. The server is read-only. It does not access your Trophy account, mutate configuration, or call Trophy APIs. For account actions, use the Account MCP Server.
Best results come from installing both servers: docs for context, Account MCP for action. See Best practice.

​
Get Started

Installation

Connect the Docs MCP Server in common clients.

Capabilities

See how search and page-read tools work.

​
Get Support

Want to get in touch with the Trophy team? Reach out to us via email. We’re here to help!

Related topics

Introduction