// config file
~/.warp/.mcp.json
Warp starts servers in this global file on its own. You can also paste the same JSON into Settings → Agents → MCP servers → + Add.
For Warp users
Warp’s agent runs commands and reads what they print. Maguyva indexes the whole repo and serves it over MCP, so the agent asks where code lives instead of running grep and cat until something matches.
Free tier: 3 repos, 50K indexed lines, no card.
One mcpServers entry in ~/.warp/.mcp.json: a URL and an Authorization header. Four facts specific to Warp.
// config file
Warp starts servers in this global file on its own. You can also paste the same JSON into Settings → Agents → MCP servers → + Add.
// transport
A url entry connects over Streamable HTTP or SSE. Nothing runs locally and Node.js is not needed.
// key
The key goes straight into the Authorization header. Keep it in the global file, not in a project’s .warp/.mcp.json that you commit.
// project files
Warp detects .warp/.mcp.json in a cloned repo but waits for you to start each server. It can also read servers from Claude Code and Codex configs once you turn that on.
# AGENTS.md
- Run make test before you call a change done.
- Use the scripts in bin/, not ad hoc commands.Warp reads project rules from AGENTS.md (or WARP.md, which wins if both exist) and applies Global Rules everywhere. Use them for:
Rules tell the agent how to work. They cannot tell it which service still reads the environment variable you are about to remove.
Three things a shell session cannot learn cheaply.
Every grep and cat the agent runs lands in the conversation. A search that prints two hundred lines spends context before the real work starts.
grep cannot tell a real call from a comment, a fixture, or a method with the same name on another class.
A new session knows nothing about the repo. Maguyva’s index is already built, so the first question gets a ranked answer.
One mcpServers entry gives Warp’s agent:
Warp gives the agent a terminal.
Maguyva gives the agent a map of the code.
Ask the map first, then run commands.
// workflow 01
warp agent> deploy.sh fails: BUILD_ID is unset. where is it set? text_pattern_search("BUILD_ID=") ci/env.sh:9 export BUILD_ID=... docs/deploy.md:31 ← prose → The agent sources ci/env.sh and reruns the deploy. [exit 0]
One indexed search replaces a recursive grep across the repo and its output.
// workflow 02
warp agent> can we stop running migrations at startup? dependency_search("runMigrations", dependents) 3 callers: server.ts, worker.ts, scripts/seed.ts → The agent moves all three to the release step. [exit 0]
The callers arrive before the change, so the worker does not boot against an old schema.
Three steps. Free tier: 3 repos, 50K indexed lines, no card.
// step 01
Pick one you already know, so you can grade the answers.
// step 02
~/.warp/.mcp.json
{
"mcpServers": {
"maguyva": {
"url": "https://maguyva.tools/mcp",
"headers": {
"Authorization": "Bearer mgv_xxxx"
}
}
}
} // step 03
Swap mgv_xxxx for your API key and save. Check that the server is running under Settings → Agents → MCP servers, then ask one question whose answer you already know.