Koskamo

Moltline Recall MCP MCP server

A portable knowledge-graph memory server that allows agents to perform graph operations such as upserting, searching, diffing, and linting knowledge graphs. The graph data is passed in and returned without being stored on the server side, ensuring privacy and portability for agent memory management.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Moltline Studio
MCP endpoint (Streamable HTTP)
https://mcp.moltlinestudio.com/recall
Vendor documentation

What you can do with it

  • Upsert nodes and edges into a portable knowledge graph
  • Search the graph for specific entities or relationships
  • Compute differences between two graph states
  • Lint graph structure for validity and consistency
Tools advertised by the last live check:
  • graph_upsert
  • graph_search
  • graph_diff
  • graph_lint
  • graph_at_time
  • graph_compact

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http moltline-recall-mcp https://mcp.moltlinestudio.com/recall

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add moltline-recall-mcp --url https://mcp.moltlinestudio.com/recall

Cursor

Merge this server into .cursor/mcp.json in your project, then enable moltline-recall-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "moltline-recall-mcp": {
      "url": "https://mcp.moltlinestudio.com/recall"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "moltline-recall-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.moltlinestudio.com/recall",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start moltline-recall-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "moltline-recall-mcp": {
      "type": "http",
      "url": "https://mcp.moltlinestudio.com/recall"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http moltline-recall-mcp https://mcp.moltlinestudio.com/recall

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "moltline-recall-mcp": {
      "url": "https://mcp.moltlinestudio.com/recall"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "moltline-recall-mcp": {
      "serverUrl": "https://mcp.moltlinestudio.com/recall"
    }
  }
}

Do you run Moltline Recall MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing