MCP
MCP server
The trumpet MCP server provides a standardized interface that allows compatible AI clients to connect to your trumpet workspace. Connect natively in Claude, Cursor, ChatGPT, and other MCP-capable tools, or use the mcp-remote module for clients that do not support remote MCP.
Tools, capabilities, and use cases
Setup
General
The MCP server uses Streamable HTTP as the primary transport, accessible at:
https://trumpet.app/api/mcpAuthentication uses OAuth 2.0 with Dynamic Client Registration. On first connection, your client opens a browser-based authorisation flow where you approve access and select your workspace (if you belong to more than one). Subsequent requests use the resulting token transparently.
Directory listings pending approval
Claude
Add trumpet as a custom connector in Claude. This is the primary setup path — Claude Code inherits connectors configured here.
- Open Connectors (or Manage Connections) in Claude
- Add a Custom Connector and paste the server URL:
https://trumpet.app/api/mcp - Click Connect and complete the OAuth flow on trumpet
- Select your workspace if prompted
Claude Code
Set up trumpet in Claude first, then use it in Claude Code. Claude Code pulls MCP connectors from your Claude account — once trumpet is connected in Claude, it is available in Claude Code sessions.
- Follow the Claude setup above to connect trumpet as a custom connector
- Open Claude Code — the trumpet connector will be available automatically
Cursor
Add the following to your Cursor MCP configuration ( .cursor/mcp.json or Cursor MCP settings). OAuth is triggered on first tool use.
{
"mcpServers": {
"trumpet": {
"url": "https://trumpet.app/api/mcp"
}
}
}ChatGPT
Connect trumpet from Apps in ChatGPT. The official app store listing is pending approval — see the Intercom guide for the current connect flow.
Custom / other clients
Building your own client
If you are building your own LLM application and want to integrate trumpet directly, connect to the remote MCP server over Streamable HTTP:
https://trumpet.app/api/mcpYour client must support OAuth 2.0 and Dynamic Client Registration (DCR) to authenticate users against trumpet. On first connect, your app should open a browser-based authorisation flow where the user approves access and selects their workspace. Once authenticated, standard MCP tool calls against the endpoint should work as expected.
Refer to the MCP specification for the remote server transport and auth requirements.
Terminal bridge via mcp-remote
If your client does not support remote MCP natively — for example, a local IDE extension or CLI tool that only speaks stdio — you can use mcp-remote as a bridge. It runs in the terminal and proxies stdio MCP to the remote trumpet server:
{
"mcpServers": {
"trumpet": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://trumpet.app/api/mcp"]
}
}
}| Setting | Value |
|---|---|
command | npx |
args | -y mcp-remote https://trumpet.app/api/mcp |
environment | None |
Setup FAQ
Connection or auth errors
Clear saved auth credentials and retry the OAuth flow. If you are using mcp-remote, run rm -rf ~/.mcp-authin your terminal, then reconnect from your client's MCP settings.
Multiple workspaces
Each trumpet workspace requires its own authentication context. During the OAuth flow, select the workspace you want the client to access. If you use mcp-remote, set a separate config directory per workspace with MCP_REMOTE_CONFIG_DIR and authenticate each one independently.
Remote connection dropped
Remote MCP connections can occasionally need a reconnect. Disconnect and reconnect the trumpet server from your client's MCP settings. This is a client-side reset and does not affect your trumpet data or authentication session.
Authentication method
The trumpet MCP server uses OAuth 2.0 with Dynamic Client Registration. All supported clients authenticate through the browser-based OAuth flow on first connect.