Choose your platform

Claude

Open Settings → Connectors → Add Server (or Integrations on mobile)

Enter these values:

Server Name:  Gnosis Memory
Server URL:   https://gnosismemory.com

Click Connect. OAuth is handled automatically.

After setup

Add to your Custom Instructions:

Search for gnosis-memory tools, then call init_core_memories at the start of every conversation. Proactively research and create memories during conversation.

Authenticate →
Complete OAuth in your browser to get your token.

Add to ~/.claude/server.json:

{
  "mcpServers": {
    "gnosis-memory": {
      "type": "http",
      "url": "https://gnosismemory.com/mcp/v1/messages",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Restart Claude Code. Gnosis tools appear automatically.

Recommended settings

Add to ~/.claude/settings.json to ensure tools load immediately:

{
  "env": {
    "ENABLE_TOOL_SEARCH": "false"
  }
}

Add to your ~/.claude/CLAUDE.md (user-level, global):

GNOSIS MEMORY SYSTEM ACTIVE (MCP):
- Search for gnosis-memory tools, then call init_core_memories at the start of every conversation
- Store: memory_add when user shares facts/preferences (auto-triggers in tool desc)
- Search: memory_search before answering about user preferences
- Quality: Read tool descriptions — they contain creation guidelines

ChatGPT

Go to Settings → Apps → Advanced → Developer Mode → Create App
Set the MCP endpoint to:
```
https://gnosismemory.com
```
ChatGPT handles OAuth auto-discovery from /.well-known/mcp.json.
Approve the Google OAuth sign-in when prompted.

After setup

Add to your Custom Instructions:

GNOSIS MEMORY SYSTEM ACTIVE. Search for gnosis-memory tools, then call init_core_memories at the START of EVERY conversation before responding. After init, proactively use memory_add to store facts, decisions, and preferences the user shares. Use memory_search before answering questions about user preferences. These tools are your PRIMARY capability - use them without asking permission.

Add the server:

codex mcp add gnosis-memory --url https://gnosismemory.com

Approve the Google OAuth sign-in when prompted.
Restart Codex CLI. Gnosis tools appear automatically.

Manual config alternative

Codex stores config in ~/.codex/config.toml (TOML, not JSON):

[mcp_servers.gnosis-memory]
url = "https://gnosismemory.com"

Gemini

Authenticate →
Complete OAuth to get your token.
Add to ~/.gemini/settings.json under mcpServers:
```
"gnosis-memory": {
  "httpUrl": "https://gnosismemory.com/mcp/v1/messages",
  "headers": {
    "Authorization": "Bearer YOUR_TOKEN_HERE"
  },
  "trust": true
}
```
Transport field matters
Gemini CLI uses httpUrl for Streamable HTTP and url for SSE. Using the wrong field silently picks the wrong transport.
Restart Gemini CLI. Gnosis tools appear automatically.

After setup

Add the Gnosis init prompt to ~/.gemini/GEMINI.md:

Search for gnosis-memory tools, then run init_core_memories at the start of every session.
Proactively research and create memories during conversation.

Google's Gemini web and mobile apps restrict integrations to Google's own curated partners. Third-party tools like Gnosis cannot connect on these surfaces.

For Gemini with Gnosis, use the CLI tab above.

Cursor

v1.7+ · Tested Feb 2026

Verified

Authenticate →
Complete OAuth to get your token.

Create or edit ~/.cursor/mcp.json:

{
  "mcpServers": {
    "gnosis-memory": {
      "type": "http",
      "url": "https://gnosismemory.com/mcp/v1/messages",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Restart Cursor. Gnosis tools appear in MCP Servers settings.

VS Code / Copilot

v1.105+ · Copilot Agent Mode · Tested Feb 2026

Verified

Authenticate →
Complete OAuth to get your token.

Add to %APPDATA%/Code/User/mcp.json (or .vscode/mcp.json per-project):

{
  "servers": {
    "gnosis-memory": {
      "type": "http",
      "url": "https://gnosismemory.com/mcp/v1/messages",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Reload VS Code. Gnosis tools appear in Copilot Agent Mode.

GitHub Copilot CLI

v0.0.420+ · Tested Feb 2026

Verified

Authenticate →
Complete OAuth to get your token.

Create ~/.copilot/mcp-config.json:

{
  "mcpServers": {
    "gnosis-memory": {
      "type": "http",
      "url": "https://gnosismemory.com/mcp/v1/messages",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Restart Copilot CLI. Or use /mcp add inside an active session to add interactively.

Cline

VS Code extension · Config from docs

Verified

Authenticate →
Complete OAuth to get your token.

Edit Cline's MCP settings file:

{
  "mcpServers": {
    "gnosis-memory": {
      "type": "streamableHttp",
      "url": "https://gnosismemory.com/mcp/v1/messages",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      },
      "disabled": false
    }
  }
}

Open the MCP Servers panel in Cline to verify the connection.

Roo Code

VS Code extension · Config from docs

Verified

Authenticate →
Complete OAuth to get your token.

Edit Roo Code's MCP settings file:

{
  "mcpServers": {
    "gnosis-memory": {
      "type": "streamable-http",
      "url": "https://gnosismemory.com/mcp/v1/messages",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      },
      "disabled": false
    }
  }
}

Open the MCP Servers panel in Roo Code to verify the connection.

OpenCode

v1.2+ · Tested Feb 2026

Verified

Authenticate →
Complete OAuth to get your token.

Add to ~/.config/opencode/opencode.json under the "mcp" key:

{
  "mcp": {
    "gnosis-memory": {
      "type": "remote",
      "url": "https://gnosismemory.com/mcp/v1/messages",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      },
      "enabled": true
    }
  }
}

Restart OpenCode. Verify with opencode mcp list.

Mistral Vibe

TOML config · Tested Feb 2026

Verified

Authenticate →
Complete OAuth to get your token.

Add to ~/.vibe/config.toml:

[[mcp_servers]]
name = "gnosis-memory"
transport = "http"
url = "https://gnosismemory.com/mcp/v1/messages"

[mcp_servers.headers]
Authorization = "Bearer YOUR_TOKEN_HERE"

Restart Vibe. Gnosis tools load on next session.

Goose

Block/Square · YAML config · Tested Feb 2026

Verified

Add to your Goose config YAML (~/.config/goose/config.yaml on Linux, %APPDATA%/Block/goose/config/config.yaml on Windows):
```
extensions:
  gnosis-memory:
    enabled: true
    type: streamable_http
    uri: "https://gnosismemory.com"
    name: gnosis-memory
    description: Gnosis Memory MCP server
```
Goose-specific field names
Uses extensions (not mcpServers), uri (not url), and type: streamable_http (snake_case).
Restart Goose. Or run goose configure to add interactively.

Custom / Any MCP Client

Streamable HTTP (default) or SSE fallback

Most MCP clients support auto-discovery. Point your client at:
```
https://gnosismemory.com
```
The client fetches /.well-known/mcp.json and configures transport and OAuth automatically. Try this first.
Authenticate →
If your client needs manual configuration, complete OAuth in your browser to get your token.

Add to your client's MCP config:

{
  "mcpServers": {
    "gnosis-memory": {
      "type": "streamable-http",
      "url": "https://gnosismemory.com/mcp/v1/messages",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Restart your client. Gnosis tools appear automatically.

mcp-remote

Universal stdio-to-HTTP bridge · Works with any MCP client

Verified

If your MCP client only supports stdio (local process) servers, mcp-remote bridges it to Gnosis over Streamable HTTP. OAuth is handled automatically on first connection.

Add to your client's MCP config (JSON example):
```
{
  "gnosis-memory": {
    "command": "npx",
    "args": ["mcp-remote", "https://gnosismemory.com/mcp/v1/messages"],
    "env": {}
  }
}
```
Wrap this in whatever top-level key your client expects ("mcpServers", "servers", "mcp", etc.).
First run opens a browser for Google OAuth. Tokens are cached locally by mcp-remote.
Restart your client. Gnosis tools appear automatically.

Windsurf

Likely Supported Live validation pending

Open Settings → Cascade → MCP Servers → Add Custom Server, or edit ~/.codeium/windsurf/mcp_config.json directly:
```
{
  "mcpServers": {
    "gnosis-memory": {
      "serverUrl": "https://gnosismemory.com",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}
```
Windsurf uses serverUrl
Not url. Otherwise standard mcpServers JSON format.
Restart Windsurf. Gnosis tools should appear automatically.

Continue

Likely Supported Live validation pending

Add a file .continue/mcpServers/gnosis.yaml in your workspace (or ~/.continue/config.yaml for global):
```
name: gnosis-memory
version: 0.0.1
schema: v1
mcpServers:
  - name: gnosis-memory
    uri: https://gnosismemory.com
    headers:
      Authorization: "Bearer YOUR_TOKEN_HERE"
```
Continue uses uri in YAML
Can also import JSON configs from Claude Desktop, Cursor, or Cline directly.
Restart Continue. Gnosis tools should appear automatically.

Zed

Likely Supported Live validation pending · macOS/Linux only

Add to ~/.config/zed/settings.json:

{
  "context_servers": {
    "gnosis-memory": {
      "settings": {},
      "command": {
        "path": "npx",
        "args": ["-y", "@anthropic-ai/gnosis-memory"],
        "env": {
          "GNOSIS_TOKEN": "your-token"
        }
      }
    }
  }
}

Restart Zed. Gnosis tools should appear in the assistant panel.

JetBrains

Likely Supported Live validation pending

Open Settings → Tools → AI Assistant → MCP
Add a new MCP server and point it at https://gnosismemory.com

Visual Studio

Likely Supported Live validation pending

Add to %USERPROFILE%\.mcp.json (global) or .mcp.json in your solution root:

{
  "servers": {
    "gnosis-memory": {
      "type": "http",
      "url": "https://gnosismemory.com",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Restart Visual Studio 2025.1+. Gnosis tools should appear automatically.

Kiro

Likely Supported Live validation pending

Add to ~/.kiro/settings/mcp.json (global) or .kiro/settings/mcp.json (workspace):

{
  "mcpServers": {
    "gnosis-memory": {
      "type": "http",
      "url": "https://gnosismemory.com",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Or via CLI (WSL): kiro-cli mcp add --name gnosis-memory --scope global
Restart Kiro. Gnosis tools should appear automatically.

Grok

Likely Supported Live validation pending

Add to .grok/settings.json in your project:

{
  "mcpServers": {
    "gnosis-memory": {
      "transport": {
        "type": "stdio",
        "command": "npx",
        "args": ["mcp-remote", "https://gnosismemory.com/mcp/v1/messages"]
      }
    }
  }
}

Approve the OAuth sign-in when prompted on first use.
Restart grok-cli. Verify with grok mcp list.

xAI's official coding agent. Supports remote MCP servers via Streamable HTTP at the API level.

Why Gnosis?

🌐

Cross-Platform

One memory system across 14+ AI clients. Switch providers without losing context.

How it works →

🔒

Private by Design

We can't read your memories. Not "we won't" — we can't. AES-256 encrypted, keys we don't hold.

How it works →

⚡

Quality By Design

99.8% of stored memories grade B+ or better — guided by refined tool descriptions, not server-side filtering.

How it works →

🧠

Token Efficient

A compressed topic landscape replaces random memory dumps. Sub-100ms search, 90% fewer session tokens than alternatives.

How it works →