MCP transport for repo-recall so Claude Desktop can call it directly #64
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/repo-recall#64
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally filed by @coilysiren on 2026-05-03T19:53:44Z - https://github.com/coilysiren/repo-recall/issues/46
Inspiration:
anthropics/claude-ai-mcpandopenai/sample-deep-research-mcp- reference MCP servers that expose local data to a hosted agent.Joins against:
repo-recall(today: a 127.0.0.1-bound web app with a JSON twin), the JSON-twin discoverability rule incoilyco-ai/AGENTS.md.Repo-recall is already structured as an HTTP API the agent can hit. Adding an MCP transport on top is a small lift and unlocks Claude Desktop calling it directly without the user copy-pasting URLs. The endpoints already exist; this is just a thin MCP wrapper that surfaces them as tools. Makes the "point an agent at it" pitch in the README literal rather than aspirational.
Moved from coilysiren/coilyco-ai#46.
Iceboxed in the 2026-05-29 backlog burn-down: MCP transport for Claude Desktop, inspiration-driven speculative. Reopen anytime if it becomes real.