AI Coding Agent Context · For Engineering
Model selection matters less than the harness around the model. ProtoMap is a context engine and model harness for gRPC and Protobuf: it gives Claude Code and Codex organization-wide context, refreshed at development speed, with no full local checkout.
Ask ProtoMap about your code and data
List all gRPC services
Which services call <RPC method>?
What is the blast radius of changing <field name>?
Claude Code with Opus 5.5 at high effort, across 20 prompts on 9 gRPC repositories (5M LOC), with higher accuracy (100% vs. 98%). See the benchmarks
From Anthropic’s own guidance
“It works best when Claude has enough starting context to know where to look… Teams that invest in codebase setup see better results.”
The harness problem
The same model that ships a clean PR on a 10k-line project struggles on a monorepo. The bottleneck moves from the model to the harness around it: context, permissions, tools, and freshness. That harness decides whether a competent model succeeds on a real codebase or wastes tokens on grep, and it is what an engineering org actually has to build.
Conventions, repo orientation, “where the tests live,” coding standards. These are prose guidance an agent reads once. They scale to setup, not to “which 14 services call this RPC.”
Cross-repo consumer mapping. Field-level usage. Change-impact analysis. The questions an agent has to answer to safely modify a shared API in a system it didn’t write.
Ask ProtoMap
Engineers ask in plain English in the web platform. Coding agents ask over MCP. Both get the same deterministic answer from ProtoMap’s context engine.
Every service that depends on it, directly or through other services, grouped by domain, with the direct callers and their call sites.
Callers and callees of a method two hops out, plus every call site with the calling method and its file location.
credit_card?The message that carries the field, where it is defined, and the services and repositories that send or receive it.
RPCs with no callers or call sites in the scanned code, plus what to check before you remove each one.
Ask ProtoMap about your code and data
List all gRPC services
Which services call <RPC method>?
What is the blast radius of changing <field name>?
Ask ProtoMap about your code and data
List all gRPC services
Which services call <RPC method>?
What is the blast radius of changing <field name>?
Ask ProtoMap about your code and data
List all gRPC services
Which services call <RPC method>?
What is the blast radius of changing <field name>?
Ask ProtoMap about your code and data
List all gRPC services
Which services call <RPC method>?
What is the blast radius of changing <field name>?
Deterministic. No embeddings. No LLM in the analysis loop: the same commit always produces the same catalog. Source code is processed only inside your environment, on the developer’s machine, in your CI, in your Enterprise tenant, or fully on-premises. Only the catalog itself is centrally queryable.
Connect your coding agent
Any agent that implements the MCP protocol.
Once an engineer is ready to apply a change, the coding agent pulls the dependencies directly from ProtoMap over MCP.
claude mcp add protomap -- protomap mcp serve
codex mcp add protomap -- protomap mcp serve
{
"mcpServers": {
"protomap": { "command": "protomap", "args": ["mcp", "serve"] }
}
}
copilot mcp add protomap -- protomap mcp serve
code --add-mcp '{"name":"protomap","command":"protomap","args":["mcp","serve"]}'
opencode mcp add protomap -- protomap mcp serve
Setup guides for every coding agent: docs.protomap.ai
See it in action
10:53
Live demo · MozFest 2026
Live demo of HoundDog.ai’s ProtoMap at MozFest’s Open Source House: callers and callees, and the blast radius of changing a field name.
The same prompt in two live sessions: ProtoMap’s answers in 50 seconds for $0.40, the baseline’s in 6 minutes for $14.44.
Rollout
Install the self-hosted platform and CLI with Docker, scan your repositories, and query ProtoMap in plain English or over MCP. Free for code scanned on your machine.
git clone https://github.com/hounddogai/protomap.git
cd protomap
./self-hosted/scripts/install.sh
Enterprise keeps context current across every repository in your organization, so agents no longer clone repositories they don’t own.
Discovery vs. reasoning
AI agents are great at reasoning. They are an expensive and inefficient way to repeatedly rediscover deterministic facts about your codebase.
Without precomputed context, every agent has to search files, follow references, inspect protobuf definitions, and reconstruct dependencies before it can start on the actual problem. Across developers, prompts, and repositories, you pay for the same discovery again and again in tokens, latency, and compute.
HoundDog.ai separates discovery from reasoning. ProtoMap computes API, field, consumer, and service relationships deterministically, keeps them current as code changes, and makes that evidence available to your existing AI agents through MCP.
Compute the facts once. Keep them fresh. Let every authorized AI agent reason over them.
Fresh on every build
AI coding agents are only as useful as the context they can access. In large codebases, that context changes every time services, APIs, fields, consumers, or dependencies change. HoundDog.ai integrates directly into your CI workflows to continuously regenerate this context from source code.
Our fast, deterministic analysis engine runs on standard CPU infrastructure with minimal impact on CI latency. ProtoMap computes these relationships once and refreshes them as your code changes.
The resulting evidence can power your service catalog, API and gRPC discovery, microservices documentation, change blast radius analysis, and organization wide context for AI coding agents. Through MCP, authorized agents such as Claude Code can query this continuously updated context whenever they need it.
Use AI where reasoning adds value. Let CI handle the deterministic discovery. The MCP server delivers structured traces, not raw source code, so AI agents reason over facts they no longer have to rediscover.
FAQ
AGENTS.md and CLAUDE.md hold conventions, repo orientation, and prose guidance an agent should read once. ProtoMap provides structured, queryable context about every API and consumer in your code, refreshed on every commit. The two are complementary: the markdown files tell the agent how to behave, ProtoMap tells it what is in the codebase.
No. RAG and semantic retrieval are good at finding text that resembles a query. ProtoMap is good at answering deterministic structural questions: which services call this RPC, which fields are consumed where, what breaks if I rename this. The two approaches complement each other.
Any MCP-capable coding agent: Claude Code, Codex, Antigravity, Copilot CLI, VS Code, and OpenCode.
On the free local tier, analysis runs on the developer’s machine and source never leaves it. On Enterprise, scans run inside your tenanted environment (cloud or on-premises), and only the resulting catalog and findings are centrally accessible. Source code never leaves your infrastructure in either tier.
The Enterprise tier connects directly to GitHub, Bitbucket, or GitLab and auto-scans every selected repo. A centralized MCP server keeps an org-wide catalog continuously fresh and serves it to every developer’s agent on demand. No developer needs to clone or check out the full codebase to get useful context, which is the only model that scales to massive monorepos and large microservice estates.
gRPC is supported today, with GraphQL and REST coming soon.
Install the self-hosted version for free. It runs on your machine with Docker, and your source code stays in your environment.
Paste into your coding agent
Set up ProtoMap and show me what it can do. ProtoMap maps gRPC services and protobuf messages across repositories, and gives coding agents that graph over MCP. Docs: https://docs.protomap.ai/quickstart/
Tell me what you are about to do before each step that installs something.
1. Check that this computer has git, Docker with Compose 2.23.1 or newer, at least 4 GB of RAM, and 20 GB of disk space. If anything is missing, tell me and stop.
2. Install ProtoMap Server, in a folder outside this repository:
git clone https://github.com/hounddogai/protomap.git
cd protomap
./self-hosted/scripts/install.sh
The installer asks questions. Choose Trial, which runs PostgreSQL locally and logs the CLI in, and keep the default port.
3. Show me the address and the one-time setup key the installer prints. Ask me to open the address, enter the key, and create my organization and owner account. Wait until I say that's done.
4. Scan this repository, from a new shell so the CLI is on the PATH:
protomap scan .
If it has no gRPC services in a supported language, tell me, and offer to scan a public example instead:
git clone https://github.com/GoogleCloudPlatform/microservices-demo.git
protomap scan microservices-demo
5. From the scanned repository's folder, add ProtoMap to yourself as an MCP server:
Claude Code: claude mcp add protomap -- protomap mcp serve
Codex: codex mcp add protomap -- protomap mcp serve
Antigravity: add "protomap": { "command": "protomap", "args": ["mcp", "serve"] } under mcpServers in ~/.gemini/config/mcp_config.json
Others: https://docs.protomap.ai/coding-agents/
Tell me if I need to restart you for it to take effect.
6. Tell me what the scan found, then use ProtoMap's tools to answer one question about my services, such as which services call a method and where. Suggest two more questions I could ask.