* feat: support for gemini-3-pro and gpt-5.2 * feat: support for gemini-3-pro and gpt-5.2 * feat: support for gemini-3-pro and gpt-5.2 * feat: support for gemini-3-pro and gpt-5.2 * feat: add local mcp server * docs * docs
3.7 KiB
| sidebar_position |
|---|
| 2 |
Local MCP Server
Hindsight provides a fully local MCP server that runs entirely on your machine with an embedded PostgreSQL database. No external server or database setup required.
This is ideal for:
- Personal use with Claude Code — Give Claude long-term memory across conversations
- Development and testing — Quick setup without infrastructure
- Privacy-focused setups — All data stays on your machine
Quick Start
With uvx (recommended)
uvx hindsight-api@latest hindsight-local-mcp
With pip
pip install hindsight-api
hindsight-local-mcp
Claude Code Configuration
Add to your Claude Code MCP settings (~/.claude/claude_desktop_config.json):
{
"mcpServers": {
"hindsight": {
"command": "uvx",
"args": ["hindsight-api@latest", "hindsight-local-mcp"],
"env": {
"HINDSIGHT_API_LLM_API_KEY": "your-openai-key"
}
}
}
}
With Custom Bank ID
By default, memories are stored in a bank called mcp. To use a different bank:
{
"mcpServers": {
"hindsight": {
"command": "uvx",
"args": ["hindsight-api@latest", "hindsight-local-mcp"],
"env": {
"HINDSIGHT_API_LLM_API_KEY": "your-openai-key",
"HINDSIGHT_API_MCP_LOCAL_BANK_ID": "my-personal-memory"
}
}
}
}
Environment Variables
All standard Hindsight configuration variables are supported.
Local MCP Specific
| Variable | Required | Default | Description |
|---|---|---|---|
HINDSIGHT_API_MCP_LOCAL_BANK_ID |
No | mcp |
Memory bank ID to use |
Available Tools
retain
Store information to long-term memory. This is a fire-and-forget operation — it returns immediately while processing happens in the background.
| Parameter | Type | Required | Description |
|---|---|---|---|
content |
string | Yes | The fact or memory to store |
context |
string | No | Category for the memory (default: general) |
Example:
{
"name": "retain",
"arguments": {
"content": "User's favorite color is blue",
"context": "preferences"
}
}
Response:
{
"status": "accepted",
"message": "Memory storage initiated"
}
recall
Search memories to provide personalized responses.
| Parameter | Type | Required | Description |
|---|---|---|---|
query |
string | Yes | Natural language search query |
max_tokens |
integer | No | Maximum tokens to return (default: 4096) |
budget |
string | No | Search depth: low, mid, or high (default: low) |
Example:
{
"name": "recall",
"arguments": {
"query": "What are the user's color preferences?",
"max_tokens": 2048,
"budget": "mid"
}
}
How It Works
The local MCP server:
- Starts an embedded PostgreSQL (pg0) on an automatically assigned port
- Initializes the Hindsight memory engine with local embeddings
- Connects via stdio to Claude Code using the MCP protocol
Data is persisted in the pg0 data directory (~/.pg0/hindsight-mcp/), so your memories survive restarts.
Troubleshooting
"HINDSIGHT_API_LLM_API_KEY required"
Make sure you've set the API key in your MCP configuration:
{
"env": {
"HINDSIGHT_API_LLM_API_KEY": "sk-..."
}
}
Slow startup
The first startup may take longer as it:
- Downloads the embedding model (~100MB)
- Initializes the PostgreSQL database
Subsequent starts are faster.
Checking logs
Set HINDSIGHT_API_LOG_LEVEL=debug for verbose output:
{
"env": {
"HINDSIGHT_API_LOG_LEVEL": "debug"
}
}
Logs are written to stderr and visible in Claude Code's MCP server output.