Gnosem

connects

gnosem.dev

Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client.

https://gnosem.dev/mcpWebsiteOAuthMCP 2025-06-18v0.1.0last checked 9 Oct 2026spoke MCP on 100% of 90 checks (30 days)initialize in 148 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The authorization server advertises RFC 7591 registration, so Claude Code can register itself and sign you in through the browser.

claude mcp add --transport http gnosem https://gnosem.dev/mcp

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The authorization server advertises RFC 7591 registration, so Claude (claude.ai & Desktop) can register itself and sign you in through the browser.

Settings → Connectors → Add custom connector, then paste https://gnosem.dev/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The authorization server advertises RFC 7591 registration, so ChatGPT can register itself and sign you in through the browser.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://gnosem.dev/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The authorization server advertises RFC 7591 registration, so Cursor can register itself and sign you in through the browser.

{
  "mcpServers": {
    "gnosem": {
      "url": "https://gnosem.dev/mcp"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The authorization server advertises RFC 7591 registration, so VS Code (Copilot) can register itself and sign you in through the browser.

{
  "servers": {
    "gnosem": {
      "type": "http",
      "url": "https://gnosem.dev/mcp"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 9 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://gnosem.dev
Dynamic client registration	✓Advertised (RFC 7591)
Client ID Metadata Document	✕Not advertised
PKCE	✓S256
Grant types	authorization_code, refresh_token
Scopes	memory
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Handshake succeeds; 6 tools listable

What the probe found

6 tools usable without signing in

The server exposes a public surface before authorization: memory_write, memory_search, memory_list, memory_forget, memory_supersede, memory_write_bulk.

Tools

memory_forgetmemory_listmemory_searchmemory_supersedememory_writememory_write_bulk

Contract history

24 Aug 2026v0.1.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Set up a watch

Own this server?

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/gnosem/badge.svg)](https://mcpi.app/servers/gnosem)