MCP Server for Lattice HQ API - Access goals, users, reviews, and feedback
If you already use Lattice Hq MCP, the lattice hq mcp mcp server is the piece that lets your assistant work with it directly. MCP Server for Lattice HQ API - Access goals, users, reviews, and feedback.
A Model Context Protocol (MCP) server for Lattice HQ that enables AI models to interact with your Lattice performance management platform.
lattice-hq-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
lattice_get_users — Get all userslattice_get_user — Get user by IDlattice_get_user_direct_reports — Get user's direct reportslattice_get_me — Get current userlattice_get_goals — Get all goalslattice_get_goal — Get goal by IDlattice_get_user_goals — Get goals for a userlattice_get_review_cycles — Get all review cycleslattice_get_review_cycle — Get review cycle by IDlattice_get_review_cycle_reviewees — Get reviewees for a cyclelattice_get_feedbacks — Get all feedbacklattice_get_feedback — Get feedback by IDConfiguration is passed through the environment: LATTICE_API_URL, LATTICE_API_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Lattice Hq MCP's toolset — lattice_get_users, lattice_get_user, lattice_get_user_direct_reports and 11 more — is a fair guide to whether it matches your workflow. It is maintained by cyrilnoah1; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| lattice_get_users | Get all users |
| lattice_get_user | Get user by ID |
| lattice_get_user_direct_reports | Get user's direct reports |
| lattice_get_me | Get current user |
| lattice_get_goals | Get all goals |
| lattice_get_goal | Get goal by ID |
| lattice_get_user_goals | Get goals for a user |
| lattice_get_review_cycles | Get all review cycles |
| lattice_get_review_cycle | Get review cycle by ID |
| lattice_get_review_cycle_reviewees | Get reviewees for a cycle |
| lattice_get_feedbacks | Get all feedback |
| lattice_get_feedback | Get feedback by ID |
| lattice_get_departments | Get all departments |
| lattice_get_department | Get department by ID |
{
"mcpServers": {
"lattice-hq": {
"command": "npx",
"args": ["-y", "lattice-hq-mcp-server", "--api-key=YOUR-TOKEN", "--stdio"],
"env": {
"LATTICE_API_URL": "https://your-company.latticehq.com"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LATTICE_API_URL | Endpoint or connection string the server talks to. | Yes |
| LATTICE_API_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.