# timps [Health: Active]

**Category:** 🧠 Knowledge & Memory  
**Repository:** https://github.com/TIMPSs/timps  
**GitHub Stars:** 0  
**npm Downloads (last month):** 16  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/timps

## Description
Persistent memory with contradiction detection, burnout monitoring, and 69 intelligence tools.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "timps": {
    "command": "npx",
    "args": ["-y","timps-code"]
  }
}
```

## Documentation

## 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:

```bash
npm install -g @timps-ai/timps-mcp
```

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.

_Full upstream README: https://allmcps.com/mcp/timps/readme_