Borrowing it
Nothing to install: this file belongs to jamesbrink/mcp-coroot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jamesbrink/mcp-coroot/main/CLAUDE.mdgit clone --depth 1 https://github.com/jamesbrink/mcp-corootWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/jamesbrink/mcp-coroot/claude-md)<a href="https://agentmods.dev/instructions/jamesbrink/mcp-coroot/claude-md"><img src="https://agentmods.dev/badge/instructions/jamesbrink/mcp-coroot/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01769 | $0.01769 |
| Opus 5 | $0.00885 | $0.00885 |
| Sonnet 5 | $0.00354 | $0.00354 |
| Haiku 4.5 | $0.00177 | $0.00177 |
Grade A, and why
mcp-coroot CLAUDE.md scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Check if Coroot is running: `curl http://localhost:8080/health` How it starts
The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Desktop Configuration for MCP Coroot
IMPORTANT DOCUMENTATION POLICY: This project maintains only two documentation files:
README.md- Public-facing project documentationCLAUDE.md- Internal instructions and configuration details- (Exception:
LICENSEandCHANGELOGfiles are also allowed)
Please DO NOT create any other markdown documentation files. All documentation should be consolidated into these two files.
IMPORTANT TESTING STANDARDS: This project follows professional Python testing standards:
- Test files must follow Python naming conventions:
test_*.py - Test files should be organized by the module they test (e.g.,
test_client.pyfor client functionality,test_server.pyfor server functionality) - DO NOT use unprofessional suffixes like
test_final_*.py,test_new_*.py,test_all_remaining_*.py, etc. - Consolidate related tests into appropriately named test files rather than creating multiple files with incremental names
- All tests must maintain their original functionality when moved between files
This file contains instructions for configuring the MCP Coroot server with Claude Desktop.
Overview
The MCP Coroot server provides 61 tools for interacting with Coroot observability platform:
- Authentication and user management (5 tools)
- Project creation and management (9 tools)
- Application monitoring and troubleshooting (3 tools)
- Infrastructure overview and incidents (2 tools)
- Deployment and system overviews (5 tools)
- Dashboard management (5 tools)
- Integration configuration (4 tools)
- Configuration management (9 tools)
- Advanced troubleshooting (3 tools)
- Custom cloud pricing (3 tools)
- Database instrumentation (2 tools)
- System configuration (4 tools)
- Risk overview (1 tool)
- Health checks (1 tool)
- Panel data and advanced configuration (6 tools)
Test coverage: 87% (197 tests passing)
Quick Setup
Using Published Package (Recommended)
Edit your Claude Desktop configuration:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 250 lines · 1,769 tokens per session scan A 536ffb2c8fc4
mcp-coroot CLAUDE.md is an instructions file published in the GitHub repository jamesbrink/mcp-coroot (16 stars, last pushed yesterday), licensed MIT. It adds 1,769 tokens to every session, about $0.0088 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.