Analysis updated 2026-05-18
Run causality experiments on a language model's internal layers from a coding assistant.
Probe whether a concept is represented at a specific layer and position in a model.
Steer a model's output by injecting directions into its internals.
Publish interpretability findings to a shared research registry.
| openinterpretability/openinterp-mcp | 0xhassaan/nn-from-scratch | 3ks/embedoc | |
|---|---|---|---|
| Stars | 0 | 0 | — |
| Language | Python | Python | Python |
| Last pushed | — | — | 2023-06-08 |
| Maintenance | — | — | Dormant |
| Setup difficulty | hard | moderate | hard |
| Complexity | 4/5 | 4/5 | 1/5 |
| Audience | researcher | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires a Colab or similar GPU compute session plus an ngrok or cloudflared tunnel.
openinterp-mcp is a Python toolkit for researchers studying mechanistic interpretability, the field that tries to understand what is actually happening inside AI language models when they process information, rather than treating the model as a black box. The toolkit exposes eight tool primitives that an AI coding assistant, such as Claude Code, Cursor, Cline, or any tool that speaks the MCP protocol, can call to run experiments. The primitives cover: attaching to a running compute session, checking its health, listing loaded probes, extracting activations (the internal numerical signals a model produces at specific layers), evaluating a probe against a stored capture, steering the model's behavior by injecting a direction into its internals, looking up SAE features from a stored activation, and running a standardized causality protocol. That protocol checks whether an observed signal is genuinely causing a behavior or only correlated with it, and returns one of five verdicts, including causal, weak causal, or an epiphenomenal category. Two additional Python modules, not exposed as MCP tools, handle publishing results to a shared registry and running replication checks. The architecture is built to be privacy first. The MCP server runs as a stateless process on the researcher's own laptop, while the actual model runs on the researcher's own compute, for example Google Colab, vast.ai, or runpod, and is reached through an ngrok or cloudflared tunnel. No inference happens on the project's own servers, no API keys are collected, and no queries pass through the project's infrastructure. Setup involves running one cell in a Colab notebook to install the package and launch a session, then connecting an MCP-compatible coding assistant to that session's URL. The toolkit is still early, described as v0.1.0 beta, with the project noting the API may change before a 1.0 release. It is released under the Apache-2.0 license.
A privacy-first toolkit that lets AI coding assistants run mechanistic interpretability experiments on language models.
Mainly Python. The stack also includes Python, MCP, FastAPI.
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly researcher.
This repo across BitVibe Labs
Verify against the repo before relying on details.