Runtime visibility for Python MCP servers. Captures tool calls, session lifecycle, module imports (SHA-256), and subp...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Universal
Model
Multiple
Fastest way to find out if bluerock belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add bluerock -- npx bluerockRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove bluerockNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ bluerock ← registers here
Runtime visibility for Python MCP servers. Captures tool calls, session lifecycle, module imports (SHA-256), and subprocess execution as structured NDJSON. No code changes.