Claude Integration

This guide walks you through integrating HyperMemory with Claude Desktop for persistent memory across conversations.

Prerequisites

• Claude Desktop installed (download)
• A HyperMemory account (sign up)
• A HyperMemory API key

Installation

Step 1: Locate your config file

Find your Claude Desktop configuration file:

OS	Path
macOS	~/Library/Application Support/Claude/claude_desktop_config.json
Windows	%APPDATA%\Claude\claude_desktop_config.json
Linux	~/.config/Claude/claude_desktop_config.json

Create the file if it doesn’t exist.

Step 2: Add HyperMemory

Add HyperMemory to your MCP servers configuration:

{
  "mcpServers": {
    "hypermemory": {
      "type": "url",
      "url": "https://api.hypermemory.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY with your actual API key.

Step 3: Restart Claude Desktop

Close and reopen Claude Desktop to load the new configuration.

Step 4: Verify the connection

Ask Claude: “What memory tools do you have available?”

Claude should list tools including memory_store, memory_recall, memory_find_related, etc.

Basic usage

Storing memories

Ask Claude to remember something:

You: "Remember that our team standup is at 9 AM every Tuesday"

Claude: I'll store that in memory.
[Uses memory_store]
Done! I've saved that your team standup is at 9 AM every Tuesday.

Recalling memories

Ask Claude to recall information:

You: "When is our team standup?"

Claude: Let me check my memory.
[Uses memory_recall]
Your team standup is at 9 AM every Tuesday.

Finding related memories

You: "What do you know related to our team meetings?"

Claude: [Uses memory_find_related]
I found these related memories:
- Team standup is at 9 AM every Tuesday
- Sprint planning is biweekly on Wednesdays
- Sarah usually facilitates the retrospectives

Advanced patterns

Structuring memories with types

Guide Claude to use consistent node types:

You: "When you store memories about people, use the type 'person'. 
For meetings, use 'meeting'. For decisions, use 'decision'."

Claude: Understood! I'll categorize memories consistently.

Building relationships

Ask Claude to connect related memories:

You: "Remember that Sarah leads the API project, and connect 
this to what you know about Sarah."

Claude: [Uses memory_store with relationships]
I've stored that Sarah leads the API project and connected it 
to her existing profile in my memory.

Time-scoped queries

Ask Claude to filter by time:

You: "What do you remember from this week's discussions?"

Claude: [Uses memory_recall with time_range]
From this week, I remember:
- Monday: Decision to prioritize API performance
- Wednesday: Sarah proposed the caching solution
- Today: We discussed the implementation timeline

Prompting tips

Be explicit about memory

Claude may not automatically use memory tools. Be explicit:

✅ “Remember this for future conversations…” ✅ “What do you recall about…” ✅ “Save this to your memory…” ✅ “Check your memory for…”

Provide context for storage

Help Claude categorize effectively:

You: "Remember this as a decision: We chose PostgreSQL for the 
new service because of its JSON support and team familiarity."

Request relationships

You: "Remember that this decision is related to the database 
migration project and involves Sarah and Marcus."

Troubleshooting

Claude doesn’t use memory tools

Symptoms: Claude responds from context only, doesn’t mention using memory tools

Solutions:

1. Verify tools are listed: “What MCP tools do you have?”
2. Be explicit: “Use your memory_recall tool to check…”
3. Restart Claude Desktop
4. Check config file syntax (valid JSON)

“Unauthorized” errors

Symptoms: Claude reports authentication errors

Solutions:

1. Verify API key is correct (no extra spaces)
2. Check key hasn’t been revoked
3. Ensure format is "Bearer YOUR_KEY" (with space)

Slow responses

Symptoms: Memory operations take several seconds

Solutions:

1. Check your network connection
2. Reduce max_results for recall queries
3. Use more specific queries

Inconsistent memory

Symptoms: Claude remembers some things but not others

Solutions:

1. Check if memories were actually stored (ask Claude to list recent memories)
2. Be more specific in recall queries
3. Use node types to organize memories

Example conversation

You: "I want you to remember key information about our project. 
Our project is called 'Phoenix' and it's a customer portal 
redesign. The deadline is Q3 2026."

Claude: I'll store this information.
[Uses memory_store with node_type="project"]
Done! I've saved:
- Project name: Phoenix
- Description: Customer portal redesign
- Deadline: Q3 2026

You: "Sarah Chen is the project lead and Marcus is the 
backend developer."

Claude: [Uses memory_store with relationships]
I've added Sarah as project lead and Marcus as backend 
developer, both connected to the Phoenix project.

You: "A week later... What do you know about Project Phoenix?"

Claude: [Uses memory_recall and memory_find_related]
Here's what I know about Project Phoenix:
- It's a customer portal redesign project
- Deadline: Q3 2026
- Sarah Chen is the project lead
- Marcus is the backend developer

Security considerations

Next steps

API Reference

Full tool documentation

Core Concepts

Understand how memories are structured