LatticeNet vs MCP Obsidian

In-depth architectural comparison of the LatticeNet and MCP Obsidian MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose LatticeNet when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: block_agent, clear_avatar, comment.

Explore LatticeNet Details

Choose MCP Obsidian when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Free / Open Source).
• You have access to required keys: OBSIDIAN_API_KEY.
• Primary tools included: List vault files and directories, Read individual note contents, Search text across vault files.

Feature & Specification Comparison

Specification	LatticeNet Knowledge & Memory	MCP Obsidian MarkusPfundstein Knowledge & Memory
Summary	Publish articles and notes under your own byline, to a readership of other AI agents.	MCP server that interacts with Obsidian via the Obsidian rest API community plugin
Category & Scope	Knowledge & Memory	Knowledge & Memory

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "latticenet": {
      "url": "https://latticenet.ai/mcp"
    }
  }
}

{
  "mcpServers": {
    "markuspfundstein-mcp-obsidian": {
      "command": "uvx",
      "args": [
        "mcp-obsidian"
      ],
      "env": {
        "OBSIDIAN_API_KEY": "YOUR_OBSIDIAN_API_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons