@letretro/mcp
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@letretro/mcpshow my latest retrospective"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
What is this?
@letretro/mcp is the official Model Context Protocol package for LetRetro. It gives AI coding assistants direct access to your LetRetro workspace — boards, cards, retrospectives, and team data.
It runs in two modes:
Mode | What it does |
| Interactive CLI wizard that auto-configures your MCP clients |
server (default) | Local MCP stdio server using the official MCP SDK — forwards requests to |
One install command, zero manual JSON editing.
Related MCP server: Labradoc MCP Server
Quick start
npx @letretro/mcp installYou'll be prompted for your LetRetro API key. The installer detects your installed MCP clients and writes the configuration — you pick which ones to set up.
╔══════════════════════════════════╗
║ LetRetro MCP Installer ║
╚══════════════════════════════════╝
Enter your LetRetro API Key: ••••••
Detected clients:
✓ Claude Desktop
✓ Cursor
✓ VS Code
✓ OpenAI Codex CLI
✓ OpenCode
✓ Antigravity
✓ Hermes
✓ OpenClaw
(Use space to select, enter to confirm)
✔ Select clients to configure:
✓ Claude Desktop: Updated ~/Library/Application Support/Claude/claude_desktop_config.json
✓ Cursor: Created ~/.cursor/mcp.json
╔══════════════════════════════════╗
║ LetRetro MCP Installed ║
╚══════════════════════════════════╝
Restart your MCP clients to start using
LetRetro tools.What gets configured
The installer adds a letretro server entry to your client's MCP config:
{
"mcpServers": {
"letretro": {
"command": "npx",
"args": ["-y", "@letretro/mcp"],
"env": {
"LETRETRO_API_KEY": "lr_..."
}
}
}
}Restart your AI coding tool and LetRetro tools are automatically available.
Supported clients
The installer auto-detects these clients and writes the correct config for each:
Client | Auto-detect | Config file written | Format |
✅ macOS/Linux |
| JSON | |
✅ |
| JSON | |
✅ binary + config |
| JSON | |
✅ |
| TOML | |
✅ |
| JSON | |
✅ |
| JSON | |
✅ |
| YAML | |
✅ |
| JSON | |
✅ config check |
| JSON | |
✅ |
| JSON |
Don't see your client? Open an issue.
How it works
AI Assistant npx @letretro/mcp mcp.letretro.com
│ │ │
│ MCP JSON-RPC over stdio │ │
│ (initialize, tools/list, │ │
│ tools/call, ...) │ │
│──────────────────────────> │ │
│ │ HTTP POST (Bearer token) │
│ │ (forwarded JSON-RPC) │
│ │ ────────────────────────────>│
│ │ │
│ │ JSON-RPC response │
│ │ <────────────────────────────│
│ MCP JSON-RPC response │ │
│ <──────────────────────────│ │The local process is a proper MCP stdio server built with the official MCP SDK. It:
Handles the full MCP handshake (
initialize,ping,notifications/*)Implements
tools/listwith a cached response from the remote serverForwards
tools/callrequests tomcp.letretro.comand returns resultsSupports graceful shutdown via
SIGTERM/SIGINTReads
LETRETRO_API_KEYand an optionalLETRETRO_MCP_URLoverride from the environment
All MCP tools, resources, and prompts are implemented server-side on mcp.letretro.com, so you get updates instantly — no package upgrade needed.
Manual setup
If you prefer to configure clients manually instead of using the installer, add the following to your client's MCP config file.
Claude Desktop / Cursor / Antigravity / OpenClaw / Windsurf / Continue:
{
"mcpServers": {
"letretro": {
"command": "npx",
"args": ["-y", "@letretro/mcp"],
"env": {
"LETRETRO_API_KEY": "your_key_here"
}
}
}
}VS Code:
{
"servers": {
"letretro": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@letretro/mcp"],
"env": {
"LETRETRO_API_KEY": "your_key_here"
}
}
}
}OpenCode:
{
"mcp": {
"letretro": {
"type": "local",
"command": ["npx", "-y", "@letretro/mcp"],
"enabled": true,
"environment": {
"LETRETRO_API_KEY": "your_key_here"
}
}
}
}OpenAI Codex CLI:
[mcp_servers.letretro]
command = "npx"
args = ["-y", "@letretro/mcp"]
[mcp_servers.letretro.env]
LETRETRO_API_KEY = "your_key_here"Hermes:
mcp_servers:
letretro:
command: "npx"
args:
- "-y"
- "@letretro/mcp"
env:
LETRETRO_API_KEY: "your_key_here"Environment variables
Variable | Default | Description |
| — | Your LetRetro API key (required) |
|
| Override the remote MCP server URL (for testing) |
|
| URL used for API key validation during install |
Development
git clone https://github.com/LetRetroHQ/mcp-cli.git
cd letretro-mcp/mcp-npm
pnpm install
pnpm dev # watch mode
pnpm build # production build
pnpm typecheck # type checking
pnpm test # run testsProject structure
src/
├── index.ts # Entry point — routes to install or server mode
├── install.ts # Interactive installer (prompt → detect → configure)
├── server.ts # MCP stdio server (MCP SDK) — forwards to mcp.letretro.com
├── clients/
│ ├── index.ts # Client registry and detection helpers
│ ├── claude.ts # Claude Desktop
│ ├── cursor.ts # Cursor
│ ├── vscode.ts # VS Code
│ ├── codex.ts # OpenAI Codex CLI (TOML config)
│ ├── opencode.ts # OpenCode
│ ├── antigravity.ts # Google Antigravity
│ ├── hermes.ts # Hermes Agent (YAML config)
│ ├── openclaw.ts # OpenClaw
│ ├── windsurf.ts # Windsurf
│ └── continue.ts # Continue
└── utils/
├── paths.ts # OS-aware config file paths
├── toml.ts # TOML serializer for Codex config
└── yaml.ts # YAML serializer for Hermes configContributing
Contributions are welcome! Whether it's adding support for a new MCP client, improving the installer, or fixing a bug:
Fork the repo
Create a feature branch (
git checkout -b feat/my-feature)Commit your changes (
git commit -am 'feat: add support for...')Push to the branch (
git push origin feat/my-feature)Open a Pull Request
See CONTRIBUTING.md for detailed guidelines.
License
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Let AI agents query data and act across all your business apps via MCP.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
Remote MCP for Kanban AI boards—manage projects, tasks, and comments from AI tools.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Related MCP Servers
AlicenseAqualityAmaintenanceConnects MCP-compatible AI tools to ScrumDo boards, enabling card, task, comment, and search operations without manual copy-pasting.45MIT- AlicenseBqualityDmaintenanceEnables AI assistants to interact with Labradoc's document management, email ingestion, task extraction, and integration features through MCP tools.1716MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to securely access and manage MyMLH user data, including profiles, education, and employment history, through OAuth-authenticated MCP tools.-
- AlicenseNot gradedqualityCmaintenanceEnables AI tools to retrieve codebase context, summaries, decision notes, and file details via MCP, avoiding re-explaining the project.2MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/LetRetroHQ/mcp-cli'
If you have feedback or need assistance with the MCP directory API, please join our Discord server