Skip to content

MCP Connectors

Claude, ChatGPT, and Codex support PowerMemory natively through the open Model Context Protocol (MCP). Grok support is experimental and under compatibility testing (see below). One vault, one OAuth login per platform, your memories available wherever you work.

Your MCP endpoint:

https://powermemory.ai/mcp/mcp

Authentication happens through OAuth — you sign in once per platform, and your vault stays scoped to your account.

Which path is right for you?

MCP is the native route for Claude, ChatGPT, and Codex. For Gemini, Copilot, and Perplexity, use the Chrome Extension instead — those platforms don't yet support MCP.

Before you start

  • A PowerMemory account (create one free).
  • The platform you want to connect (Claude, ChatGPT Plus, or Codex; Grok is experimental).
  • The MCP URL above.

Claude

Claude supports custom MCP connectors directly in settings.

  1. Open Customize → Connectors.
  2. Click + Add to open the "Add custom connector" dialog.
  3. Enter the details:
  4. Name: Power Memory
  5. URL: https://powermemory.ai/mcp/mcp
  6. Click Add.

Adding the Power Memory custom connector in Claude

  1. When prompted, sign in through OAuth to link your vault.
  2. Power Memory now appears connected. You can review tool permissions — the 8 tools default to "Needs approval", so Claude asks before each use.

Power Memory connected in Claude with its 8 tools

ChatGPT

ChatGPT requires Plus and Developer Mode to add custom MCP connectors.

  1. Open Settings → Apps and toggle Developer mode ON. ChatGPT shows an "elevated risk" notice — this is standard for any custom MCP connector.

Enabling Developer mode in ChatGPT settings

  1. Still under Settings → Apps, click Create app.
  2. In the New App dialog, enter:
  3. Name: Power Memory
  4. Server URL: https://powermemory.ai/mcp/mcp
  5. Authentication: OAuth
  6. Tick "I understand and want to continue" to acknowledge that OpenAI hasn't reviewed third-party MCP servers.
  7. Click Create.

Configuring the Power Memory MCP server in ChatGPT

  1. Sign in through OAuth when prompted. Power Memory now appears under Enabled apps (and in Drafts, marked DEV).

Power Memory enabled in ChatGPT

Why the 'DEV' label?

Custom MCP connectors added through Developer Mode are marked as developer apps. This is expected — it doesn't affect functionality.

Grok

Experimental — compatibility testing

Grok's connector attaches and shows Connected, but write persistence is not yet reliable: Grok can report a save succeeded without actually storing it. Treat Grok as read/testing only until confirmed.

Grok supports custom connectors directly.

  1. On the Connectors page, click New Connector (top right).
  2. In the "Custom Connector" dialog, enter:
  3. Name: Power Memory
  4. Server URL: https://powermemory.ai/mcp/mcp
  5. Click Add Connector.

Adding the Power Memory custom connector in Grok

  1. Sign in through OAuth when prompted. Power Memory now shows as Connected with its 8 tools available.

Power Memory connected in Grok

Note

Third-party connectors aren't built or maintained by xAI and are subject to the xAI Privacy Policy — standard for any custom connector.

Codex

Codex connects as a custom (manual) MCP client. Generate an API key from your dashboard, then add PowerMemory as a custom MCP server pointing to https://powermemory.ai/mcp/mcp with your API key. Codex uses the same 8 tools as the other MCP clients, and writes persist normally.

What you get — the 8 tools

Once connected, your AI has access to these PowerMemory tools:

Memory operations Session flow (V POWER)
memory_read — recall context v_power_start — begin a session
memory_write — save new memory v_power_save — capture session memories
memory_evolve — update existing v_power_refresh — re-anchor mid-session
memory_delete — remove memory v_power_stop — close and archive

See the Extension Guide for how the V POWER session flow works in practice, and Memory Categories for what's worth saving.

Trouble connecting?

If OAuth doesn't open, the connector won't link, or tools don't appear, see Troubleshooting.