memorydeveloper-toolsmcpcoding-agents
Persistent, project-scoped memory for coding agents, with local storage, recall, contradiction detection, and audit history.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
We couldn’t automatically confirm this listing starts correctly
The install command below didn't complete successfully in our automated test.
npx -y timps-codenpm notice npm notice New major version of npm available! 10.1.0 -> 12.1.0 npm notice Changelog: <https://github.com/npm/cli/releases/tag/v12.1.0> npm notice Run `npm install -g npm@12.1.0` to update! npm notice npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/@timps%2fmemory-core - Not found npm ERR! 404 npm ERR! 404 '@timps/memory-core@*' is not in this registry. npm ERR! 404 npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder, http ur
This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 13d ago.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Overview
Use cases
Recall architecture decisions across coding sessions
Preserve repository-specific conventions for agents
Track previously attempted bugs and fixes
Detect conflicting project memories
Audit what the agent stored and when
Key features
Project-scoped persistent memory
Local JSON and SQLite storage
Optional Postgres and Qdrant backends
Contradiction detection and confidence scoring
Hash-chained memory-write audit trail
stdio support for MCP clients
Capabilities & Tool Schemas
Inspect callable tools, capabilities, and parameters exposed to AI agents by Timps.
Extracted Tool Capabilities
Project-scoped persistent memory
Local JSON and SQLite storage
Optional Postgres and Qdrant backends
Contradiction detection and confidence scoring
Hash-chained memory-write audit trail
stdio support for MCP clients
How Timps works
What timps MCP server does
The timps MCP server adds persistent memory to coding agents without replacing the agent itself. It keeps a separate memory store for each project, so information from different repositories does not normally mix. The stored information can include architectural decisions, codebase-specific conventions, previously encountered bugs and their fixes, session outcomes, and an audit record explaining what was written.
Memory is divided into several layers. Working memory covers the current session and is cleared when the session ends. Episodic memory records previous sessions and their outcomes. Semantic memory holds durable facts such as patterns, conventions, and decisions promoted from past activity. An append-only, hash-chained audit trail records memory writes and when they occurred.
Additional processing includes temporal pattern detection, contradiction detection, confidence scoring, and importance-based pruning. These features help the memory store identify conflicting information and retain more relevant durable context.
How it works
The MCP server runs between an MCP-compatible coding agent and the TIMPS memory store. A client starts the server over stdio, then the agent can use its memory capabilities during work. On later sessions, the project-specific store can provide context from earlier work instead of requiring the user to repeat it.
Local JSON and SQLite storage are the default options. Postgres and Qdrant are available as optional storage choices when a shared or externally hosted setup is needed. Ollama can provide local model processing, while Claude, GPT, and Gemini are listed as optional provider choices. The README does not specify the configuration details for switching between these providers.
Setup and configuration
Install the MCP package globally with:
Then configure the client to launch timps-mcp as a stdio process. The README provides configurations for Claude Code, Cursor, and Windsurf, each using the same command. Other MCP clients can also run the command over stdio.
No API key is required when using the local Ollama path. The project also supports optional paid model providers, so provider-specific credentials may be needed when those services are selected. The supplied material does not list environment variable names or detailed storage configuration options.
Tools and capabilities
The timps MCP server supports these documented capabilities:
- Persisting memory between agent sessions
- Keeping memory isolated by project
- Recording architectural decisions and coding conventions
- Recalling prior bugs, fixes, sessions, and outcomes
- Detecting contradictions in stored information
- Assigning confidence and importance to memories
- Pruning lower-importance information
- Maintaining a hash-chained audit history of writes
- Using local JSON or SQLite storage, with optional Postgres or Qdrant support
Limitations and notes
The repository describes the MCP server and CLI as the parts used and trusted most by the author, while the desktop app, mobile app, JetBrains plugin, VS Code extension, and swarm mode are identified as less tested. Treat those additional components separately from the core MCP use case.
Published benchmark results are self-run on a synthetic corpus and are not independently verified. They should not be treated as performance guarantees for a particular codebase. The README also does not provide a complete tool list, detailed provider setup, or environment-variable reference. The timps MCP server is therefore best evaluated against the memory and client workflow your project requires.
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
npm downloads
16
Package downloads in the last 30 days.
Last commit
16d ago
Most recent push to the default branch.
Install check
Inconclusive
Install command did not finish in our automated test.
Directory activity
3 views
Config copies, upvotes, and views on AllMCPs.
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Timps
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/timps)HTML Embed
<a href="https://allmcps.com/mcp/timps"><img src="https://allmcps.com/api/badge/timps?style=directory" alt="Timps on AllMCPs" /></a>Technical Specs & Signals
CategoryKnowledge & Memory
PricingFree
7/7 checks healthy over the last 42d
43Quality signal: Fair · 43/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership10/20
Documentation & tools17/30
Adoption & activity5/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Supply-chain signal
No high-severity advisories surfaced by our automated scan.
Critical 0High 0Medium 0Low 0
Scanned 1d ago via OSV.dev · timps-code (npm)
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.