Developer · Local MCP server
Trail
Issue tracker and durable project memory for your coding agent, scoped to the folder you open.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.usetrail/trail- Version
- 1.29.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-17
- Updated
- 2026-09-17
- Publisher
- dev.usetrail
- Namespace
- Namespace verified by the MCP Registry via the domain usetrail.dev · how
- Website
- usetrail.dev
- Repository
- github.com/arsprengel/trail-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | usetrail | 1.29.1 | stdio |
How to connect Trail
Trail runs locally from a Node.js package published to the npm registry: usetrail version 1.29.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y usetrail@1.29.1. It reads these environment variables: TRAIL_API_URL and TRAIL_PROJECT; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"trail": {
"command": "npx",
"args": [
"-y",
"usetrail@1.29.1"
],
"env": {
"TRAIL_API_URL": "<value>",
"TRAIL_PROJECT": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Tracepiishield MCPPII scanning and redaction receipts for LLM traces and tool payloads. | Remote · HTTPLive check: ✗ no handshake |
| TraceWeavePortable MCP runtime for RTL logs and VCD; repository setup adds FSDB and site EDA integration. | Local · stdio |
| TractorScopeQuery your databases and build charts, dashboards, filters and alerts in TractorScope. | Remote · HTTPLive check: sign-in required |
| tradesearcher.aiSearch TradeSearcher strategies and backtests from Claude Code, Cursor, Codex, and other agents. | Local · stdio |
| TrainBudTalk to your own fitness data. Findings computed in code against your own 28-day baselines. | Local · stdio |
| Trayd MCPTrade Robinhood through natural language in Claude Code. | Remote · HTTPLive check: sign-in required |
| Tree-sitter MCP ServerParse code into Tree-sitter ASTs to see node kinds, field names, and positions. | Local · stdio |
| TreeringA local map of your codebase over time: symbols, callers, subgraphs and structural change. | Local · stdio |