Connect to Claude

This guide walks you through connecting Lattice to Claude Desktop using mcp-remote.

Prerequisites

  • Node.js 18+ — needed for npx to run mcp-remote
  • Claude Desktop — requires a Pro, Max, Team, or Enterprise plan

Configuration

Add the following to your Claude Desktop config file:

claude_desktop_config.json
{
  "mcpServers": {
    "lattice": {
      "command": "npx",
      "args": ["mcp-remote@latest", "https://mcp.ferrisletter.dev/mcp"]
    }
  }
}

Config file location

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

If the file doesn't exist, create it. If you already have other MCP servers configured, merge the lattice entry into your existing mcpServers object.

Why mcp-remote?

Claude Desktop currently supports stdio-based MCP servers. The mcp-remote package bridges the gap — it connects to the remote Lattice server over SSE/HTTP and presents it to Claude Desktop as a local stdio server. No local installation of Ferrisletter is required.

Alternative: Settings → Integrations

If Claude Desktop supports remote MCP servers natively (via Settings → Integrations), you can add the URL directly:

https://mcp.ferrisletter.dev/mcp

This method doesn't require Node.js.

Verify the connection

After restarting Claude Desktop, ask:

"What topics are available on Lattice?"

If you see a list of topics, the connection is working.