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.
- Connects with an API key
- Free 14-day trial
- No credit card
Draft a goal update for my Q3 hiring goal.
Working in Lattice with Elaichi
-
List all Lattice me
-
List all Lattice users
-
Get single Lattice user by ID
How to connect Lattice to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Lattice MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Lattice MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Lattice through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Lattice is logged.
-
Managers
Catch up on goals before a one on one
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.
-
People Ops
See where a review cycle stands
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.
-
Leadership
Roll up department goals for the exec meeting
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.
-
Sales
Log a goal update after the pipeline review
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.
-
Engineering
Prepare a growth conversation with real inputs
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.
-
Operations
Answer who reports to whom
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.
Try asking
- “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.”
What connecting Lattice gets you
6 screens from Elaichi, each doing one job for your Lattice account.
Ask Elaichi to work across your apps.
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.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about goals and get live Lattice answers.
Type a plain question and the agent reads goals, feedback, and review cycles from Lattice.
Copy the endpoint
AI apps
One endpoint puts Lattice in every client.
Claude, ChatGPT, and Cursor reach Lattice through one endpoint, no SDK, no shared API key.
Tool catalog
34 Lattice tools, ready without writing code.
Users, departments, goals, goal updates, feedback, and review cycles, covered with no custom code.
Toolboxes
Every team gets its own Lattice toolbox.
Managers get goals and direct reports, People Ops gets review cycles, each scoped to its team.
Shared connections
Share one Lattice connection, never a credential.
One person connects Lattice, teammates work through it, and nobody else sees the API key.
Audit log
Every Lattice call lands in the audit log.
See who created a goal, when, and on which record, in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Lattice digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch goals
Lattice
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Lattice
Queued
Workflows
A schedule runs Lattice work end to end.
Goal updates are fetched, grouped, drafted into a digest, a person approves, it posts to Lattice.
Lattice health
Refreshed 4 minutes ago · every 15 minutes · from the goals collection
Goals
1,284 ↓ 12%
Goal updates
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Goals created
Last 14 days
By team
Share of activity
People Ops 34%
Leadership 27%
Engineering 21%
Sales EMEA 18%
Collections and dashboards
Lattice goal health, computed without a model.
Four metrics, fourteen days of goals created, and a breakdown by team, refreshed on a schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Lattice tools for your AI agents
34 tools are ready to call through Elaichi's MCP endpoint the moment you connect Lattice, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
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 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.
Put Lattice in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot