Jev agent tools — Claude Code MCP server: use and install
This MCP server asks evidence-based repository questions, reviews finished diffs, and selects existing tests when code needs investigation.
claude mcp add --env JEV_TOOLS_URL=<JEV_TOOLS_URL> --env JEV_TOOLS_API_KEY=<JEV_TOOLS_API_KEY> --env JEV_TOOLS_MODEL=<JEV_TOOLS_MODEL> --env JEV_TOOLS_ALLOW_COMMAND=<JEV_TOOLS_ALLOW_COMMAND> --transport stdio jev-agent-tools -- npx -y jev-agent-toolsWhat Jev agent tools does
Jev agent tools exposes six MCP tools for exploring unfamiliar repositories, asking typed questions about code evidence, checking completed changes, and choosing tests already present in the project. It works alongside ordinary reading, search, and command execution rather than replacing them.
The package runs as a stdio server and reads JEV_TOOLS_URL, JEV_TOOLS_API_KEY, JEV_TOOLS_MODEL, and JEV_TOOLS_ALLOW_COMMAND. Node.js 24 or newer is required. Git and Bash are needed when optional command evidence is enabled. Without Node.js 24 or newer, the server will not start.
You can register it with a host command or an npx MCP configuration. A saved API key is kept in plain text, so that storage choice matters when enabling persistent configuration.
What it helps with
- navigate an unfamiliar repository
- answer questions from repository evidence
- review completed code changes
- select existing tests to run
Example prompts for the agent
- Inspect this repository and answer the question using evidence from the relevant files.
- Review the completed changes and connect each finding to the code that supports it.
- Select the existing tests that should cover these changes.
How to install Jev agent tools
Platform CLI
claude mcp add --env JEV_TOOLS_URL=<JEV_TOOLS_URL> --env JEV_TOOLS_API_KEY=<JEV_TOOLS_API_KEY> --env JEV_TOOLS_MODEL=<JEV_TOOLS_MODEL> --env JEV_TOOLS_ALLOW_COMMAND=<JEV_TOOLS_ALLOW_COMMAND> --transport stdio jev-agent-tools -- npx -y jev-agent-toolsReplace <…> with your own values
Platform CLI
codex mcp add jev-agent-tools --env JEV_TOOLS_URL=<JEV_TOOLS_URL> --env JEV_TOOLS_API_KEY=<JEV_TOOLS_API_KEY> --env JEV_TOOLS_MODEL=<JEV_TOOLS_MODEL> --env JEV_TOOLS_ALLOW_COMMAND=<JEV_TOOLS_ALLOW_COMMAND> -- npx -y jev-agent-toolsReplace <…> with your own values
Config file
{
"mcpServers": {
"jev-agent-tools": {
"command": "npx",
"args": [
"-y",
"jev-agent-tools"
],
"env": {
"JEV_TOOLS_URL": "<JEV_TOOLS_URL>",
"JEV_TOOLS_API_KEY": "<JEV_TOOLS_API_KEY>",
"JEV_TOOLS_MODEL": "<JEV_TOOLS_MODEL>",
"JEV_TOOLS_ALLOW_COMMAND": "<JEV_TOOLS_ALLOW_COMMAND>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"jev-agent-tools": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"jev-agent-tools"
],
"env": {
"JEV_TOOLS_URL": "<JEV_TOOLS_URL>",
"JEV_TOOLS_API_KEY": "<JEV_TOOLS_API_KEY>",
"JEV_TOOLS_MODEL": "<JEV_TOOLS_MODEL>",
"JEV_TOOLS_ALLOW_COMMAND": "<JEV_TOOLS_ALLOW_COMMAND>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e JEV_TOOLS_URL=<JEV_TOOLS_URL> -e JEV_TOOLS_API_KEY=<JEV_TOOLS_API_KEY> -e JEV_TOOLS_MODEL=<JEV_TOOLS_MODEL> -e JEV_TOOLS_ALLOW_COMMAND=<JEV_TOOLS_ALLOW_COMMAND> jev-agent-tools npx -y jev-agent-toolsReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Jev agent tools
How do I install Jev agent tools in Claude Code?
Run claude mcp add jev-agent-tools -e JEV_TOOLS_URL=<JEV_TOOLS_URL> -e JEV_TOOLS_API_KEY=<JEV_TOOLS_API_KEY> -- npx -y jev-agent-tools.
What does Jev agent tools do?
It gives an MCP client tools for repository exploration, evidence-based code questions, completed-change review, and selection of existing tests.
What does the server require?
Use Node.js 24 or later, a complete Jev-compatible endpoint in JEV_TOOLS_URL, and a Bearer credential in JEV_TOOLS_API_KEY. Git and Bash support optional command evidence.
