Twiceshy MCP server
{
"mcpServers": {
"twiceshy": {
"type": "http",
"url": "https://api.twiceshy.app"
}
}
}{
"mcpServers": {
"twiceshy": {
"type": "http",
"url": "https://api.twiceshy.app"
}
}
}{
"mcpServers": {
"twiceshy": {
"type": "http",
"url": "https://api.twiceshy.app"
}
}
}{
"servers": {
"twiceshy": {
"type": "http",
"url": "https://api.twiceshy.app"
}
}
}{
"mcpServers": {
"twiceshy": {
"type": "http",
"url": "https://api.twiceshy.app"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.1.0
What it does
Twiceshy is a self-hosted service that stores engineering experience records—known issues, root causes, and validated fixes—and surfaces them to LLM coding agents at decision time via MCP tools. It uses git-backed markdown records with relevance-filtered retrieval to help agents avoid repeating known mistakes.
- Retrieve validated fixes and known dead-ends when a coding agent encounters a problem, filtered by relevance to avoid weak matches.
- Record engineering decisions, root causes, and trap patterns as git-backed markdown that agents can query during development.
- Prevent repetition of known mistakes by injecting hard-won experience into agent decision-making workflows.
Tools this server exposes
| Tool | Does |
|---|---|
| retrieve_experience | Query the experience corpus with relevance-filtered retrieval; returns up to 3 records above a relevance threshold or nothing if no match is strong enough. |
| submit_trap_card | Record a new issue, dead-end, or validated fix as a candidate experience record that requires validation and human review before promotion. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.