Connect Lattice to Claude Code

Let Claude draft review feedback and update goals in Lattice. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Lattice to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Lattice, you add a Lattice MCP server: a small hosted service that exposes Lattice's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Lattice account. No API keys pasted into config files.

claude mcp add --transport http lattice https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Lattice once connected?

Full read-write Lattice access lets Claude draft review feedback against the right competencies, submit a completed review for the active cycle, and update goal and OKR progress, all once you approve. It also reads continuous feedback and review cycles for context. The writing that meant tabbing back into Lattice happens where the people data already lives.

Draft performance review feedback for a direct report against the active review cycle
Submit a completed review for the active cycle once you approve the wording
Update progress, status, or check-in notes on a goal or OKR
Summarize the continuous feedback already logged for a specific person
Look up a review cycle, its questions, and the competencies tied to a role

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Lattice access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Lattice API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Lattice changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Lattice connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Lattice connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Lattice account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Lattice's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Lattice?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Lattice account it signs in with. Revoking access is one click in Lattice.

More on the Lattice connector

Lattice connector for claude.ai Deel + Claude Code Justworks + Claude Code Paychex + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us