Memoth.ai docs

MCP server

Connect a client

Every client below speaks Streamable HTTP with OAuth. Paste the URL, sign in once in the browser, done. Use /mcp/readonly anywhere you want a connection that can only read.

Claude Code

shell
claude mcp add --transport http memoth https://mcp.memoth.ai/mcp

Then run /mcp inside Claude Code and choose memoth to complete sign-in. To scope a project to read-only:

shell
claude mcp add --transport http memoth-readonly https://mcp.memoth.ai/mcp/readonly

Claude.ai and Claude Desktop

  1. Open Settings → Connectors.
  2. Choose Add custom connector.
  3. Name it Memoth and enter https://mcp.memoth.ai/mcp as the URL. Leave the client id and secret empty: Memoth registers the client itself.
  4. Click Connect and finish sign-in in the tab that opens.

Cursor

Add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json in a project:

mcp.json
{
  "mcpServers": {
    "memoth": {
      "url": "https://mcp.memoth.ai/mcp"
    }
  }
}

Cursor shows a Needs login badge next to the server; click it to sign in.

VS Code

Run MCP: Add Server from the command palette and choose HTTP, or write .vscode/mcp.json directly:

.vscode/mcp.json
{
  "servers": {
    "memoth": {
      "type": "http",
      "url": "https://mcp.memoth.ai/mcp"
    }
  }
}

ChatGPT

  1. Open Settings → Connectors and enable Developer mode.
  2. Choose Create, name it Memoth, and enter https://mcp.memoth.ai/mcp.
  3. Pick OAuth as the authentication method and complete sign-in.

Windsurf, Zed and other clients

Clients that support remote HTTP servers with OAuth take the URL directly, as above. For a client that only runs local (stdio) servers, bridge with mcp-remote:

mcp_config.json
{
  "mcpServers": {
    "memoth": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.memoth.ai/mcp"]
    }
  }
}

mcp-remote performs the browser sign-in on the client’s behalf and keeps the token in ~/.mcp-auth. Delete that folder to sign out.

Headless agents and scripts

An agent with no browser and no person behind it authenticates with client credentials rather than a sign-in. See Authentication → Headless agents. The server address and the tools are the same.

Registering the client

You never register anything by hand. The server advertises support for Client ID Metadata Documents (URL-shaped client ids) and, for older clients, Dynamic Client Registration. Your client picks whichever it implements; both end at the same consent screen.