# Lattice MCP connector

The Lattice connector brings people, departments, direct reports, goals, goal updates, feedback, and review cycles into Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent, with each person signed in as themselves and every call logged.

Source: https://elaichi.ai/connectors/lattice/

## Facts

| | |
| --- | --- |
| Application | Lattice |
| Category | HRIS |
| AI tools | 34 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Lattice is connected

- Draft a goal update for my Q3 hiring goal.
- Which of my direct reports have no goal updates this month?
- Summarize the feedback my team received during the current review cycle.

## Connect Lattice in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Lattice.
2. Optionally set Share with, then press Connect.
3. Paste a Lattice API key. One person generates a token in Lattice and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Lattice tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Lattice MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Lattice MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Lattice MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Lattice MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Lattice MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Lattice to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Lattice tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Lattice through Elaichi

### Catch up on goals before a one on one

Managers. Ask for a direct report's goals and their latest goal updates before the meeting starts. Then add a goal update in Lattice while the conversation is still fresh.

### See where a review cycle stands

People Ops. Pull up the current review cycle, the questions in it, and the feedback that has come in so far, without clicking through Lattice screen by screen.

### Roll up department goals for the exec meeting

Leadership. List the goals for each department, read the recent goal updates, and get a plain summary of what is on track and what has gone quiet.

### Log a goal update after the pipeline review

Sales. After the weekly pipeline review, post a goal update against the quarter's revenue goal in Lattice from the same chat where the numbers were discussed.

### Prepare a growth conversation with real inputs

Engineering. Look up a competency, the feedback an engineer has received, and the goals they own, so the growth conversation starts from the Lattice record rather than memory.

### Answer who reports to whom

Operations. Find a Lattice user, their department, and their direct reports in one ask, and check custom attributes like location or cost center when an org question comes up.

## Elaichi vs Zapier MCP vs Composio for Lattice

All three can connect Lattice to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Lattice tools | Allow or restrict single Lattice tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Lattice call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Lattice to Claude?

Connect Lattice in Elaichi first: the Lattice sign-in step is a single API key that you paste in, with no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and Lattice is ready to use.

### Does Lattice work with ChatGPT and Cursor as well as Claude?

Yes. Once Lattice is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent. You connect Lattice once and every client picks it up.

### What can an AI agent actually do with my Lattice data?

It can look up people, departments, and direct reports in Lattice, read goals and their updates, pull feedback, and show the questions and status of a review cycle. It can also create a goal, update one, and post a goal update on your behalf. Short, concrete asks work better than long sentences, so "show my direct reports' goals" beats a paragraph.

### Does connecting Lattice give the AI access to everyone's reviews and feedback?

No. Access in Lattice follows the person who signed in, so the agent sees the people, goals, feedback, and review cycles that person can already see in Lattice and nothing more. Elaichi can narrow that access further with roles and restrictions, and it never widens it.

### Can my team share one Lattice connection?

Yes. One person connects Lattice with the API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in as themselves, so the audit log names the person behind every Lattice call.

### Can I stop an agent from creating or changing goals in Lattice?

Yes. Restrictions in Elaichi work per action, so you can restrict creating goals, updating goals, or posting goal updates in Lattice for a role or for one person while leaving reading alone. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Lattice connection when someone leaves?

Offboarding a person in Elaichi ends their access to Lattice at once, in every client they used. A shared Lattice connection keeps working for everyone else on the team. If you disconnect Lattice in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client in one step.

### Does the Lattice MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Lattice is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Lattice?

Yes. Both let Claude, ChatGPT or Cursor use Lattice. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Lattice call.

### How is Elaichi different from Composio for Lattice?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Lattice: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 34 Lattice tools

Every tool below is callable through https://api.elaichi.ai/mcp once Lattice is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Lattice me** (List). Get the current Lattice user the API token is associated with. Returns: id, object, url, manager, directReports, department, name, preferredName, email, tasks, title, status, startDate, birthDate, timezone, gender, jobFunction, jobLevel, jobType, isAdmin, externalUserId, createdAt, updatedAt, customAttributes.
- **List all Lattice users** (List). List users in Lattice. Returns a paginated list of users with id, email, name, title, status, and manager. Active users are returned by default; a status of 'null' retrieves all users regardless of status.
- **Get single Lattice user by ID** (Get). Get a single Lattice user by id. Returns: id, object, url, manager, directReports, department, name, preferredName, email, tasks, title, status, startDate, birthDate, timezone, gender, jobFunction, jobLevel, jobType, isAdmin, externalUserId, createdAt, and 2 more fields. Required: id. Requires id. Returns a 404 if the user cannot be found.
- **Get single Lattice competency by ID** (Get). Get a single competency in Lattice by id. Returns: id, object, name, description. Required: id. A 404 is returned when no competency matches the given id.
- **Get single Lattice custom attribute value by ID** (Get). Get a single custom attribute value in Lattice by id. Returns: id, object, url, value. Required: id. Returns a 404 if the custom attribute value cannot be found.
- **Get single Lattice custom attribute by ID** (Get). Get a Lattice custom attribute by id. Returns: id, object, url, name, type, visibility. Required: id. Returns a 404 if no matching custom attribute exists.
- **List all Lattice custom attributes** (List). List a Lattice user's custom attributes. Returns each entry with its customAttribute and customAttributeValue objects. Required: user_id.
- **Get single Lattice department by ID** (Get). Get a single department in Lattice by id. Returns: id, object, url, name, description, createdAt. Returns a 404 if the department cannot be found. Required: id.
- **List all Lattice departments** (List). List all departments in Lattice. Returns a paginated list of department records with id, object, url, name, description, and createdAt.
- **List all Lattice direct reports** (List). List users who report directly to a given user in Lattice. Returns: id, object, url, manager, directReports, department, name, preferredName, email, tasks, title, status, startDate, birthDate, timezone, gender, jobFunction, jobLevel, jobType, isAdmin, externalUserId, createdAt, updatedAt, customAttributes. Required: user_id.
- **Get single Lattice feedback by ID** (Get). Get a single continuous feedback record in Lattice by id. Returns: id, object, url, author, targets, associatedValues, feedbackRequest, body, competency, visibility, isPublic, createdAt. Required: id. Returns a 404 if no matching feedback is found.
- **List all Lattice feedbacks** (List). List all continuous feedback in Lattice, newest first. Returns feedback items including: id, author, body, isPublic, and createdAt.
- **Create a Lattice goal update** (Create). Create a progress update for an existing goal in Lattice. Returns the created goal update record with its entityId, goal_id, id, comment, status, and increment. Requires goal_id, comment, and status; exactly one of increment or absolute must be provided. Required: goal_id, id, comment, status.
- **List all Lattice goal updates** (List). List all progress updates for a specific goal in Lattice. Returns: data. Required: goal_id, id.
- **Create a Lattice goal** (Create). Create a new goal in Lattice. Returns the created goal with entityId, name, okrType, priority, and tags. Requires name, startDate, dueDate, and ownerIds; key results also require amountType, startingAmount, and goalAmount. Required: name, startDate, dueDate, ownerIds.
- **Get single Lattice goal by ID** (Get). Get a single goal in Lattice by id. Returns the full goal including id, name, state, okrType, currentAmount, dueDate, owners, and tags. Required: id.
- **List all Lattice goals** (List). List goals in Lattice with pagination. Returns each goal's id, name, state, okrType, currentAmount, dueDate, owners, and tags.
- **Update a Lattice goal by ID** (Update). Update an existing Lattice goal by id (full replacement). Returns the updated goal with entityId, name, tags, and childGoals. Required: id, name, description, startDate, dueDate, priority, private, ownerIds, okrType, amountType, startingAmount, goalAmount, companyGoal, departmentId, departmentsVisibleToIds, goalCycleId, tagNames, isDraft, parentId.
- **List all Lattice goals updates** (List). List all goal updates across all goals in Lattice with pagination support. Returns: entityId, goalId, id, comment, status, increment. Max 100 per page.
- **List all Lattice goals user** (List). List all goals owned by a user in Lattice. Returns a paginated list of goals with: id, name, okrType, state, isPrivate, dueDate, owners, createdAt. Required: user_id.
- **Get single Lattice question revision by ID** (Get). Get a single Lattice question revision by id. Returns: id, object, url, body, description, ratingScale, choices, isSelectionOptional, isCommentOptional. Required: id. Returns a 404 if no matching question revision exists.
- **Get single Lattice question by ID** (Get). Get a Lattice review question by id. Returns: id, object, url, body, description, hasFreeFormText, ratingScale, choices, isSelectionOptional, isCommentOptional. Required: id. Returns a 404 if no matching question exists.
- **Get single Lattice review cycle by ID** (Get). Get a single Lattice review cycle by id. Returns the review cycle object including its id, name, stage, reviewees, reviews, and createdAt. Required: id. Returns a 404 if the review cycle cannot be found.
- **List all Lattice review cycles** (List). List all review cycles in Lattice. Returns a paginated list of review cycle objects including their id, name, stage, reviewees, reviews, and createdAt.
- **Get single Lattice reviewee by ID** (Get). Get a reviewee in Lattice by id. Returns the reviewee object including its id, user, reviewCycle, reviews, weightedScore, and createdAt. Required: id. Returns a 404 if the reviewee cannot be found.
- **List all Lattice reviewees** (List). List all reviewees in a Lattice review cycle. Returns each reviewee with its id, user, reviewCycle, reviews, weightedScore, and createdAt. Required: review_cycle_id.
- **List all Lattice reviews** (List). List all reviews for a reviewee in Lattice. Returns a paginated list of reviews including id, reviewee, reviewer, question, reviewType, and submittedAt. Required: reviewee_id.
- **List all Lattice reviews reviewcycle** (List). List all reviews for a review cycle in Lattice. Returns a paginated list where each review includes id, reviewee, reviewer, question, reviewType, response, and submittedAt. Required: review_cycle_id.
- **Get single Lattice tag by ID** (Get). Get a single Lattice tag by id. Returns the tag object including id, object, url, name, createdAt, and updatedAt. Required: id. A 404 is returned if the tag cannot be found.
- **List all Lattice tags** (List). List all tags in Lattice. Returns a paginated list of tags, each including id, name, url, createdAt, and updatedAt.
- **Get single Lattice task by ID** (Get). Get a Lattice task by id. Returns the resolved task object: id plus the task's remaining upstream fields under attributes (the upstream docs document the 200 body as an untyped object without enumerating fields). Returns a 404 when no task matches. Required: id.
- **List all Lattice tasks** (List). List tasks for a Lattice user, paginated. Returns task records; Lattice's API documents each task as an unenumerated object, exposing only the record's id plus an opaque attribute set (attributes). Required: user_id.
- **List all Lattice updates** (List). List all Updates in Lattice with pagination. Returns each update's id, url, author, manager, responses, sentiment, isPublic, and createdAt.
- **Update a Lattice update by ID** (Update). Get a single Lattice Update by id. Returns the update's id, author, manager, responses, sentiment, isPublic, and createdAt. Required: id. Returns a 404 if no matching update is found.
