🧠

Memory / Knowledge Graph

Persistent long-term memory for your assistant.

Category: Cognitive
Difficulty: Easy
Rank: #10

Quick Configuration

Choose the setup that matches your environment.

Before You Start

  • Confirm you have the account, endpoint, or API key required for Memory / Knowledge Graph.
  • Start with minimum scopes and read-only access where possible.
  • Keep secrets in environment variables instead of hardcoding them in JSON.

Hosted / Remote

JSON
Hosted Config json
{
  "memory": {
    "url": "https://YOUR_MEMORY_MCP_ENDPOINT"
  }
}

Local CLI (npx)

JSON
Local Config json
{
  "memory": {
    "command": "npx",
    "args": ["-y", "mcp-remote", "https://YOUR_MEMORY_MCP_ENDPOINT"],
    "env": {
      "MEMORY_API_KEY": "YOUR_MEMORY_API_KEY"
    }
  }
}

Common Pitfalls & Fixes

  • âš ī¸ Watch out: Explain benefits; show before/after conversations.
  • 🔑 Always store API keys in environment variables, never hardcode them in JSON.
  • đŸ›Ąī¸ Start with read-only scopes if available to verify connection safely.

Example Prompts

Once connected, try these prompts to test capabilities:

  • Break down a complex task into clear steps.
  • Compare two approaches and list tradeoffs.
  • Draft a decision checklist for a new MCP setup.

Verification Checklist

  • Run 1-2 real prompts to confirm Memory / Knowledge Graph returns usable data.
  • Check that error messages are clear enough for troubleshooting.
  • Document the required scopes, dependencies, and env vars for future reuse.