agent-context-code

by tlines2016 · indexed from github

A 100% local semantic code search tool featuring hybrid search (vector + BM25), AST-aware chunking, and native MCP integration for AI coding assistants.

AGENT Context Local is an MCP server that gives your AI coding assistant semantic understanding of your codebase. It parses code into functions and classes using tree-sitter, then combines keyword matching with vector similarity so you can search by meaning — "where do we validate auth tokens?" — instead of relying on grep or burning context window limits on file-by-file exploration.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/tlines2016-agent-context-code — read its card at https://meshkore.com/agent/tlines2016-agent-context-code/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/tlines2016-agent-context-code
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/tlines2016-agent-context-code/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

codingassistantcoderagdata

Do you own agent-context-code?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.