https://docs.trustgrid.io/docs/mcp/Recent content in MCP onHugoenhttps://docs.trustgrid.io/docs/mcp/authentication/Mon, 01 Jan 0001 00:00:00 +0000https://docs.trustgrid.io/docs/mcp/authentication/The Trustgrid MCP server requires authentication for every request. There are two ways to provide credentials. OAuth 2.0 The server implements OAuth 2.0 with the MCP authorization spec. Clients that support the OAuth handshake — including Claude Desktop and Claude Code — will automatically open a browser-based login when you first connect. After you authorize, the client manages token refresh without further intervention. No manual token setup is required for OAuth-capable clients.https://docs.trustgrid.io/docs/mcp/installation/Mon, 01 Jan 0001 00:00:00 +0000https://docs.trustgrid.io/docs/mcp/installation/Before you start You need two things: Your MCP endpoint URL — The default is https://mcp.trustgrid.io/mcp. If your organization uses a tenant-specific portal domain (for example, acme.trustgrid.io), use https://mcp.acme.trustgrid.io/mcp instead. The path suffix selects the tool group: /mcp/codemode (codemode), /mcp/read, /mcp/tools, or a combination like /mcp/codemode/read. Credentials — OAuth is the preferred method: if your client supports it, point it at the URL and it will handle login automatically — no token management required.https://docs.trustgrid.io/docs/mcp/tools/Mon, 01 Jan 0001 00:00:00 +0000https://docs.trustgrid.io/docs/mcp/tools/The Trustgrid MCP server organizes its tools into three groups. Each group is available at a distinct URL path, and paths can be combined to get the union of multiple groups. Tool groups codemode (/mcp/codemode) The codemode group is the default when no path suffix is specified. It provides an AI code execution sandbox with full read-only access to the Trustgrid API, plus documentation search and structured resource inspection. This reduces token usage and agent turns, and allows your agent to perform complex multi-step reasoning and data retrieval in a deterministic single turn — without needing to switch back and forth between tools.https://docs.trustgrid.io/docs/mcp/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.trustgrid.io/docs/mcp/troubleshooting/Common issues The server isn’t appearing in my client Check that your client supports HTTP transport. Not all MCP clients support Streamable HTTP — some only support stdio (local process) connections. The Trustgrid MCP server is HTTP-only. Verify your client’s MCP documentation. Check the URL format. The URL must include the path prefix: https://mcp.trustgrid.io/mcp ✓ correct https://mcp.trustgrid.io ✗ missing /mcp https://mcp.trustgrid.io/mcp/ ✓ trailing slash is fine Check your domain. If your organization has a tenant-specific endpoint (e.