DevTime — Claude Code MCP server: what it does, how to install
Verifies architectural claims against repository code, tests, and configuration locally. Helps discover unproven implementations during review.
claude mcp add devtime -- uvx devtime-eiWhat DevTime does
DevTime inspects a repository to check whether file paths actually deliver what they promise. A webhook file returning a 404 response will not pass as implemented logic; the server flags it as CONTRADICTED or WEAK. The tool tracks six specific concept groups: authentication, billing webhooks, background jobs, data exports, admin permissions, and file uploads. Other custom domain concepts remain unsupported.
The server operates strictly read-only, never executes project code, and transmits zero telemetry. It calculates an Understanding Score and watches file edits: when an underlying file shifts, previously proven claims drop into a STALE state. The server requires uvx to launch.
What it helps with
- catch stub handlers disguised as completed features
- verify whether test files cover specified API routes
- detect when code modifications invalidate recorded decisions
- evaluate pull request changes against existing architectural claims
Example prompts for the agent
- Run DevTime verification to check if our billing webhooks have test backing
- Inspect repository claims with DevTime and list any weak or contradicted concepts
- Review the diff against origin/main using DevTime to check for destabilized claims
How to install DevTime
Platform CLI
claude mcp add devtime -- uvx devtime-eiuvx runs the command named after the package; if the README names another one, use uvx --from devtime-ei <command>
Platform CLI
codex mcp add devtime -- uvx devtime-eiuvx runs the command named after the package; if the README names another one, use uvx --from devtime-ei <command>
Config file
{
"mcpServers": {
"devtime": {
"command": "uvx",
"args": [
"devtime-ei"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from devtime-ei <command>
Config file
{
"servers": {
"devtime": {
"type": "stdio",
"command": "uvx",
"args": [
"devtime-ei"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from devtime-ei <command>
Platform CLI
gemini mcp add devtime uvx devtime-eiuvx runs the command named after the package; if the README names another one, use uvx --from devtime-ei <command>
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 DevTime
How to install DevTime in Claude Code?
Run claude mcp add devtime -- uvx devtime-ei in your terminal. This requires the uvx runner on your system.
What does DevTime verify?
It verifies repository structure across six predefined areas: auth, billing webhooks, background tasks, data export, admin rights, and file uploads. It cross-references file contents, configs, and tests.
Does DevTime execute code or send data to cloud APIs?
No, it works entirely offline in read-only mode. DevTime does not run tests or scripts, calls no external language models, and sends no telemetry.
