Trunk MCP Server
MCP serverTrunk.io runs this official remote MCP server for its flaky-test product. It gives supported coding agents two tools: one retrieves root-cause analysis and fix suggestions, and the other generates a plan for uploading test results to Trunk.
Not for: Running tests or replacing a test framework. The server analyzes results available to Trunk and helps configure uploads; it does not execute the test suite itself.
Source and setup verified on 2026-11-05
Developer ToolsQuick facts
- Maintainer
- Trunk.io (official)
- Endpoint
- https://mcp.trunk.io/mcp
- Transport
- Streamable HTTP
- Authentication
- OAuth 2.0 + OpenID Connect
- UI
- None documented; tools only
What you can do
- fix-flaky-test retrieves Trunk root-cause analysis and fix suggestions
- setup-trunk-uploads generates a plan for sending test results to Trunk
Requirements
- A Trunk account
- A supported MCP client with remote HTTP and OAuth support
- Test results uploaded to Trunk for flaky-test analysis
Use https://mcp.trunk.io/mcp in the client's remote MCP configuration. There is no local package to install.
Start the connection and complete the Trunk OAuth flow in the browser.
{
"mcpServers": {
"trunk": {
"url": "https://mcp.trunk.io/mcp"
}
}
}Always confirm the latest setup instructions with the maintainer before installing.
>Questions
Is the Trunk MCP server official?
Yes. Trunk.io owns the repository and runs the remote endpoint.
Does Trunk MCP need an API token in the config file?
No. The server uses OAuth 2.0 with OpenID Connect and prompts you to sign in when the client connects.
Does it render an app inside the chat?
No inline MCP App resource is documented. It exposes two analysis and setup tools.
>Related Apps
Real-time OS metrics dashboard for system monitoring
QR code generator for creating scannable codes
UI over MCP - Create next-gen UI experiences with the protocol and SDK