Agenten stärken
Der eigene Befehl des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
npx -y @timps-ai/[email protected]Claude Code hat keinen Installationslink für einen lokalen Befehl. Kopieren Sie den Befehl unten und führen Sie ihn in einem Terminal aus.
TIMPS_URL=<value> TIMPS_MEMORY_URL=<value> TIMPS_API_KEY=<secret> TIMPS_PROJECT_PATH=<value> claude mcp add io.github.sandeeprdy1729-timps -- npx -y @timps-ai/timps-mcp@2.0.3In einem Terminal ausführen.
{ "mcpServers": { "io.github.sandeeprdy1729-timps": { "command": "npx", "args": [ "-y", "@timps-ai/[email protected]" ], "env": { "TIMPS_URL": "<value>", "TIMPS_MEMORY_URL": "<value>", "TIMPS_API_KEY": "<secret>", "TIMPS_PROJECT_PATH": "<value>" } } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
Status: solo project, early. The MCP server and CLI are the parts I actually use daily and trust. Everything else in this repo (desktop app, mobile, JetBrains, plugin marketplace) is younger and less tested — flagged below. I'd genuinely rather you try the core and tell me it's broken than read marketing copy.
Persistent memory with contradiction detection, burnout monitoring, and 69 intelligence tools.
npx timps-code "what does this codebase do?"
No install, no config, no API key. Point it at any repo. If you have Ollama running locally, this is 100% free and nothing leaves your machine. If not, it'll walk you through picking a provider.
To actually get persistent memory in Claude Code, Cursor, or any MCP client, add the MCP server:
npm install -g @timps-ai/timps-mcp
then point your MCP client at it (config instructions in MCP Setup).
Ask Claude Code to fix a bug today. Close the session. Ask it something related tomorrow — it has no idea what you decided yesterday, what you already tried, or why you structured something the way you did. You end up re-explaining the same context every single session.
TIMPS sits between you and your agent as an MCP server and keeps a memory store per project:
That's the whole pitch. It's a memory layer, not a new agent — it works alongside whatever coding agent you already use.
Under the hood, memory is organized in a few real tiers:
There's a deeper set of subsystems on top of this (temporal pattern detection, contradiction detection, confidence scoring, importance-based pruning) for people who want to go further — full breakdown in ARCHITECTURE.md rather than here, since most people don't need to know the internals to use it.
Add to ~/.claude.json:
{
"mcpServers": {
"timps": {
"command": "timps-mcp"
}
}
}
Add to .cursor/mcp.json:
{
"mcpServers": {
"timps": {
"command": "timps-mcp"
}
}
}
Add to ~/.config/windsurf/config.json:
{
"mcpServers": {
"timps": {
"command": "timps-mcp"
}
}
}
Run timps-mcp over stdio. That's all the protocol requires.
Run yourself: npx tsx benchmark/index.ts --quick
These are self-run benchmarks on a synthetic dataset I built — not independently verified, and not a claim about how it performs on your actual codebase. Take them as "the core logic works as designed," not as a competitive claim.
The monorepo includes a VS Code extension, a desktop app (Tauri), a mobile app, a JetBrains plugin, and a multi-agent "swarm" mode for task decomposition. These exist and mostly work, but they've had far less real-world use than the CLI/MCP core — treat them as "try if you're curious," not "this is production-ready." I'd rather be upfront about that than have you find out the hard way.
This is genuinely useful to me right now: run the 30-second command above on one of your real repos, and tell me what broke, what was confusing, or what it got wrong. That feedback is worth more to this project than a star.
MIT
Persistent memory with contradiction detection, burnout monitoring, and 69 intelligence tools.
{ "mcpServers": { "io.github.sandeeprdy1729-timps": { "command": "npx", "args": [ "-y", "@timps-ai/[email protected]" ], "env": { "TIMPS_URL": "<value>", "TIMPS_MEMORY_URL": "<value>", "TIMPS_API_KEY": "<secret>", "TIMPS_PROJECT_PATH": "<value>" } } }}Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Der Herausgeber nennt diese Umgebungsvariablen: TIMPS_URL, TIMPS_MEMORY_URL, TIMPS_API_KEY, TIMPS_PROJECT_PATH.
Timps läuft lokal über stdio.
Zuletzt geprüft: 2026-11-09. Persistent memory with contradiction detection, burnout monitoring, and 69 intelligence tools.