Skip to content

feat(agent): integrate AI Context MCP for repository navigation#36

Open
yenklabs wants to merge 1 commit into
mainfrom
feat/ai-context-mcp-integration
Open

feat(agent): integrate AI Context MCP for repository navigation#36
yenklabs wants to merge 1 commit into
mainfrom
feat/ai-context-mcp-integration

Conversation

@yenklabs

Copy link
Copy Markdown
Owner

Summary

  • Vendors the AI Context MCP server at tools/ai-context/ for local repo indexing and token-budgeted context capsules
  • Wires dual MCP in .cursor/mcp.json: dali (corpus tools) + ai-context (code navigation)
  • Adds agent routing rule (.cursor/rules/ai-context-routing.mdc) and setup guide (docs/agent-context.md)
  • Updates contributor docs to describe the complementary two-server workflow

Closes #35

Architecture

Server Tools Use when
ai-context run_pipeline, get_context_capsule "Where is X implemented?", module layout, file discovery
dali lint, score, replay, probe, draft, pack Corpus validation, evaluation, PR readiness

Typical flow: run_pipeline → edit → lintscorereplay

Test plan

  • cd tools/ai-context && npm install succeeds
  • Cursor shows both dali and ai-context MCP servers
  • run_pipeline with task "where is replay_hash computed" returns capsule referencing dali/runners/run_integrity.py
  • Existing Dali MCP score smoke test on Mata v. Avianca record still works
  • .ai-context/ index cache is gitignored

Adds a vendored ai-context MCP server for local repo indexing and token-budgeted
context capsules, wired next to the existing dali MCP in Cursor config and docs.

Closes #35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(agent): integrate AI Context MCP for repository navigation alongside Dali MCP

1 participant