Context injection for AI agents, triggered by the codebase itself
Connect Tripwire to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Context injection for AI agents, triggered by the codebase itself. The tripwire mcp server is what makes that connection.
Tripwire is a local MCP server that auto-injects relevant context when an agent reads files in your project. Define tripwires on paths — when an agent steps on one, it gets the knowledge it needs before it can do damage.
Installation goes through your MCP client rather than a global install: point it at @tripwire-mcp/tripwire on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Ordering — When multiple tripwires match a path, they are sorted deterministically:Truncation — When max_context_length > 0, Tripwire enforces a character budget on the injected context (not tokens — different clients may truncateDependencies — Tripwires can declare depends_on: [name1, name2] to pull in other tripwires' context when they fireConflicts — Tripwire does not attempt to resolve conflicts between contexts. If two tripwires match the same path and give contradictory instructions, both areread_file — Drop-in replacement for standard file reading. Checks tripwires and prepends matched contextcreate_tripwire — Allows agents to author new tripwires. Creates a .yml file in .tripwires/list_tripwires — Returns all active tripwires, optionally filtered by path, tag, or severitycheck_tripwires — Given a file path, returns which tripwires would fire — useful for agents to preview before readingexplain — Given a file path, returns a structured breakdown of what would be injected and why: matched tripwires with their globs, resolved dependenciesdeactivate_tripwire — Soft-disables a tripwire without deleting the file. Adds active: false to the YAMLThis sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Tripwire's toolset — Ordering, Truncation, Dependencies and 7 more — is a fair guide to whether it matches your workflow. It is maintained by simonrueba; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Tripwire's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Ordering | When multiple tripwires match a path, they are sorted deterministically: |
| Truncation | When max_context_length > 0, Tripwire enforces a character budget on the injected context (not tokens — different clients may truncate independently). The separator and file content are not part of the budget. |
| Dependencies | Tripwires can declare depends_on: [name1, name2] to pull in other tripwires' context when they fire. |
| Conflicts | Tripwire does not attempt to resolve conflicts between contexts. If two tripwires match the same path and give contradictory instructions, both are injected and the agent sees both. |
| read_file | Drop-in replacement for standard file reading. Checks tripwires and prepends matched context. |
| create_tripwire | Allows agents to author new tripwires. Creates a .yml file in .tripwires/. |
| list_tripwires | Returns all active tripwires, optionally filtered by path, tag, or severity. |
| check_tripwires | Given a file path, returns which tripwires would fire — useful for agents to preview before reading. |
| explain | Given a file path, returns a structured breakdown of what would be injected and why: matched tripwires with their globs, resolved dependencies, suppressed entries, active config, and the full rendered injection. Useful f |
| deactivate_tripwire | Soft-disables a tripwire without deleting the file. Adds active: false to the YAML. |
{
"mcpServers": {
"tripwire": {
"command": "npx",
"args": ["-y", "@tripwire-mcp/tripwire", "serve", "--project", "."]
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.