Connect Your AI Agent to TRM API Docs

TRM API Docs is agent-ready. Connect the authenticated TRM API Docs MCP server once, then ask your coding agent to find current API contracts, answer implementation questions, and help build TRM API integrations in your workspace. The TRM API Docs MCP server also exposes a Compliance API integration skill that helps your agent build multi-step workflows, such as withdrawal flows and webhook integrations. The connection gives your agent two complementary sources of TRM guidance:

Capability	What your agent receives	How it helps
Search with your agent	Search and full-page access to the API reference and implementation guides available to your TRM Docs account	Grounds answers and generated code in current request schemas, responses, authentication, errors, and operational guidance
Build integrations faster	Skills are exposed as MCP resources, including common Compliance API scenarios	Helps the agent combine individual APIs into complete workflows such as deposits and withdrawals

How it works

Connect MCP to your agent

Add the authenticated TRM API Docs MCP server to Claude, Cursor, Codex, VS Code, or another compatible agent.

Authenticate

Your agent opens the TRM API Docs sign-in page in a browser. Sign in, then follow the redirect back to your agent.

Retrieve current guidance

For your prompt, the agent reads a matching skill resource and retrieves the minimum current API pages and guides.

Build in your workspace

Your coding agent uses the retrieved contracts and skill instructions to generate or modify code, add tests, and report assumptions or missing choices.

Connect your agent

Use the authenticated MCP endpoint:

https://docs.trmlabs.com/authed/mcp

Choose your client and complete the one-time setup.

Authentication is client-specific. Follow the authentication step in your client tab below to open the TRM API Docs sign-in flow in your browser.

Add TRM API Docs at user scope so it is available across projects:

claude mcp add --transport http --scope user trm-api-docs https://docs.trmlabs.com/authed/mcp

To authenticate from within Claude Code, start Claude Code and enter:

/mcp

Select trm-api-docs, then select Authenticate.Alternatively, trigger authentication directly from your terminal:

claude mcp login trm-api-docs

Either method opens the TRM API Docs sign-in flow in your browser.

claude mcp login must run in an interactive terminal. In a non-interactive or CI shell it fails with stdin isn't a terminal — authenticate once interactively (or use /mcp inside Claude Code), then reuse the stored credentials.

Confirm that the server is configured:

claude mcp get trm-api-docs

See the Claude Code MCP documentation for client-specific options.

For an individual Claude account:

Open Customize → Connectors.
Select Add custom connector.
Enter TRM API Docs as the name and https://docs.trmlabs.com/authed/mcp as the URL.
Add the connector, then select Connect to open the TRM API Docs sign-in flow in your browser.
After signing in, enable TRM API Docs for your conversation from the connectors menu.

On Claude Team and Enterprise plans, an Owner or Primary Owner must first add the custom connector under Organization settings → Connectors. Each user then connects their own TRM API Docs account.

See Claude custom connectors for plan-specific instructions.

Add the server to your global ~/.cursor/mcp.json file:

{
  "mcpServers": {
    "trm-api-docs": {
      "url": "https://docs.trmlabs.com/authed/mcp"
    }
  }
}

Save the file. Then trigger authentication using either option:

Cursor IDE: Open Cursor’s MCP settings, find trm-api-docs, and select Connect.
Cursor Agent CLI: Run:
cursor-agent mcp login trm-api-docs

Either action opens the TRM API Docs sign-in flow in your browser. Use .cursor/mcp.json instead if you want the configuration to apply only to one project.See the Cursor MCP documentation for configuration and authentication details.

Add and authenticate the server from the command line:

codex mcp add trm-api-docs --url https://docs.trmlabs.com/authed/mcp
codex mcp login trm-api-docs

The login command opens the TRM API Docs sign-in flow in your browser.Confirm that the server is configured:

codex mcp get trm-api-docs

Restart Codex after authentication. The Codex app, CLI, and IDE extension share MCP configuration on the same host.See the Codex MCP documentation for UI and config.toml alternatives.

Add the server to .vscode/mcp.json:

{
  "servers": {
    "trm-api-docs": {
      "type": "http",
      "url": "https://docs.trmlabs.com/authed/mcp"
    }
  }
}

In the command palette, run MCP: List Servers, select trm-api-docs, and start the server. Starting it opens the TRM API Docs sign-in flow in your browser. To make the server available across workspaces, use MCP: Add Server and select your user profile instead.VS Code users can run MCP: Browse Resources to view TRM skills exposed by the server.See the VS Code MCP documentation for configuration and resource-management options.

Add a remote Streamable HTTP server named trm-api-docs with this URL:

https://docs.trmlabs.com/authed/mcp

Save the configuration, then use your client’s Connect or Authenticate action to open the TRM API Docs sign-in flow. Your client must support OAuth for remote MCP servers. Consult its documentation for the exact action and resource support.

After you sign in, the browser redirects you to your client, and the server returns only the content available to your TRM Docs user groups.

Verify the connection

Start a new agent conversation and ask:

Use trm-api-docs, not model memory. Find and read the Compliance API authentication guide (/guides/public/Authentication). Return its title and URL and confirm it lists both API Key and OAuth2 (Recommended). Then list the TRM MCP resources available in this session.

A successful connection should show that your agent:

Uses the documentation search capability to find the relevant page.
Retrieves the full page through the TRM API Docs filesystem capability.
Cites or links to the TRM API Docs page it used.
Lists any TRM workflow skills available to your account when the client supports MCP resources.

Start building with TRM

You can use the connection for a focused API question, a single implementation, or a complete workflow.

Connecting the MCP uses browser sign-in and grants your agent access to TRM documentation only. The integration code your agent writes authenticates to the TRM API separately — with your own API key or OAuth client. Generate one at my.trmlabs.com → Settings → API Tokens and keep it in an environment variable or secret manager, never in the prompt or the code.

Answer an API question

Using trm-api-docs, find and read the current documentation for the Wallet Screening endpoint that submits one or more addresses for screening. Explain the request, response, authentication, errors, and operational constraints. Cite every TRM API Docs page you use.

Integrate with a TRM API

Using trm-api-docs, implement a Wallet Screening client in this repository for one address and chain. Read the current endpoint, authentication, and error-handling documentation before editing code. Follow the repository’s existing conventions, add tests, and report the documentation pages and assumptions used.

Build a common compliance workflow

Using trm-api-docs, discover and read the TRM Compliance API integration skill. Help me implement a withdrawal workflow. Ask for any choices that materially change the implementation before editing code.

AI-generated code can be incomplete or incorrect. Review the retrieved documentation, generated code, tests, authentication, and customer-specific compliance decisions before using an implementation in production.

Troubleshooting

The browser does not open

Confirm that your client supports OAuth for remote HTTP MCP servers. Remove and re-add the server, or use the client’s manual authentication command.

Authentication succeeds but protected pages are missing

Open the page directly in TRM API Docs with the same account. If you cannot access it there, request the appropriate API documentation permission and authenticate again.

Tools work in the session but the server is not listed in `/mcp`

The server can be authenticated and its tools usable in the current session yet not appear in the persisted /mcp list. Reload the client, or remove and re-add the server, to persist it. This is a display or persistence quirk, not an authentication failure.

API documentation tools are available but a skill is not used

Ask the agent to list MCP resources and explicitly read the matching skill before using search tools. Some clients expose resources without automatically selecting them.

Results appear stale after an API documentation update

Start a fresh agent session and reconnect the MCP server. Clients can cache resource lists or conversation context.

​How it works

​Connect your agent

​Verify the connection

​Start building with TRM

​Answer an API question

​Integrate with a TRM API

​Build a common compliance workflow

​Troubleshooting

​The browser does not open

​Authentication succeeds but protected pages are missing

​Tools work in the session but the server is not listed in /mcp

​API documentation tools are available but a skill is not used

​Results appear stale after an API documentation update

How it works

Connect your agent

Verify the connection

Start building with TRM

Answer an API question

Integrate with a TRM API

Build a common compliance workflow

Troubleshooting

The browser does not open

Authentication succeeds but protected pages are missing

Tools work in the session but the server is not listed in `/mcp`

API documentation tools are available but a skill is not used

Results appear stale after an API documentation update