Is this an official Lattice MCP server?

No. It is Memtro's MCP server with Memtro's Lattice connector behind it: the connector reads Lattice through its API with the credentials you connect on Dashboard → Connections, and Lattice publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Lattice?

Only when you ask, and only what it has been granted: create a goal or key result with named owners; post a progress update on a goal. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · People and HR

Lattice MCP server

Lattice in any MCP client, through Memtro: Lattice does not publish this server. Memtro's Lattice connector reads Lattice through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Lattice people management: the people directory (name, title, department, manager), departments, goals and OKRs with their owners, status and progress, and review cycles by name and stage. Can create a goal or key result and post a progress update on a goal. Never reads reviews, feedback or check-ins.

Reads

lattice_peoplePeople in Lattice: name, work email, title, department, manager and start date.
lattice_departmentsDepartments in Lattice with their descriptions.
lattice_goalsGoals and OKRs in Lattice: name, state, status (on track, off track…), type (company, department, individual), owners, department…
lattice_review_cyclesReview cycles in Lattice by name and stage (draft, collecting reviews, calibration, ended) with when reviews opened and closed.

Acts, when you ask

These change something in Lattice. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

lattice_create_goalCreates a goal in Lattice as the key's admin: an objective, or a key result with a measured target.
lattice_post_goal_updatePosts a progress update on a Lattice goal as the key's admin: a status (green, amber, red), a comment…

Connect it

First connect Lattice on Dashboard → Connections, then add Memtro to your client once. The Lattice tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Lattice connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› Which company goals are off track?
› Who reports to Priya Sharma?
› What are the engineering OKRs this quarter?
› Is the mid-year review open?
› Post an amber update on the hiring goal: two offers out, one accepted.

Questions

Is this an official Lattice MCP server?: No. It is Memtro's MCP server with Memtro's Lattice connector behind it: the connector reads Lattice through its API with the credentials you connect on Dashboard → Connections, and Lattice publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Lattice?: Only when you ask, and only what it has been granted: create a goal or key result with named owners; post a progress update on a goal. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.