lattice_get_department
Get details of a specific department by ID
LABSCO SUMMARY
It reads the org chart and the performance cycle, and it changes neither.
Every tool in the list is a get: goals, cycles, feedback and updates come back as they stand, and nothing here creates, edits or closes them. The pairing is consistent — a collection tool and a by-ID tool for each record type — so most work is one listing call followed by detail lookups. lattice_get_user_direct_reports and lattice_get_user_goals are the two that start from a person rather than an object ID, which is what makes a manager-shaped question answerable without first knowing an object ID.
What it is
A read client for Lattice HQ, 16 tools over users, goals, review cycles, feedback, departments and updates.
What you get
- People: lattice_get_users for the organization, lattice_get_user by ID, lattice_get_user_direct_reports for a reporting line, and lattice_get_me for the authenticated user.
- Goals at three levels: lattice_get_goals across the organization, lattice_get_goal by ID, and lattice_get_user_goals for one person.
- Review cycles: lattice_get_review_cycles, lattice_get_review_cycle by ID, and lattice_get_review_cycle_reviewees for everyone covered by a cycle.
- Feedback and updates as separate records: lattice_get_feedbacks and lattice_get_feedback, lattice_get_updates and lattice_get_update.
- Departments: lattice_get_departments and lattice_get_department by ID.
Requirements
An API key for the Lattice HQ organization, and LATTICE_API_URL naming the Lattice API the server calls.
Setup effort
One command plus a key — LATTICE_API_URL=https://<YOUR_COMPANY>.latticehq.com npx lattice-hq-mcp-server --api-key=<YOUR_API_KEY> --stdio, then supply credentials
USE CASES
01
Preparing for a one-on-one without opening five tabs
Pull the person, the goals they own, and the feedback and updates on file, so the conversation starts from what is already recorded.
02
Working out who is still owed a review before the cycle closes
List the cycles, open the one that is running, and read out everyone it covers.
03
Walking a reporting line down from where you sit
Start from the authenticated user, expand direct reports a level at a time, and fall back to the full user list when a name is all you have.
04
Rolling goals up to the department that owns them
List departments, open the one in question, and read the organization's goals to see which sit under it.
16 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
lattice_get_departments
Get all departments in the organization
lattice_get_feedback
Get details of a specific feedback by ID
lattice_get_feedbacks
Get all feedback in the organization
lattice_get_goal
Get details of a specific goal by ID
lattice_get_goals
Get all goals in the organization
lattice_get_me
Get current user information
lattice_get_review_cycle
Get details of a specific review cycle by ID
lattice_get_review_cycle_reviewees
Get all reviewees for a specific review cycle
lattice_get_review_cycles
Get all review cycles in the organization
lattice_get_update
Get details of a specific update by ID
lattice_get_updates
Get all updates in the organization
lattice_get_user
Get details of a specific user by ID
lattice_get_user_direct_reports
Get direct reports for a specific user
lattice_get_user_goals
Get all goals for a specific user
lattice_get_users
Get all users in the organization
BEFORE YOU INSTALL
What to know first
Tools you get
16 tools when we connected. Every tool is a lattice_get_ read; nothing creates goals or writes feedback. Lattice API access is typically Enterprise-only and needs admin permissions.
Requires
- npx on PATH
- Node.js 18 or later
- LATTICE_API_TOKEN in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 16 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
LATTICE_API_URL=https://<YOUR_COMPANY>.latticehq.com npx lattice-hq-mcp-server --api-key=<YOUR_API_KEY> --stdioMCP Clients
Claude Desktop — npx
CLAUDE DESKTOP — NPX · JSON
{
"mcpServers": {
"lattice-hq": {
"command": "npx",
"args": [
"-y",
"lattice-hq-mcp-server",
"--api-key=<YOUR_API_KEY>",
"--stdio"
],
"env": {
"LATTICE_API_URL": "https://<YOUR_COMPANY>.latticehq.com"
}
}
}
}Claude Desktop — local build
Clone and build the server
Needs Node.js 18 or newer.
CLAUDE DESKTOP — LOCAL BUILD · TERMINAL
git clone https://github.com/cyrilnoah1/lattice-hq-mcp.git
cd lattice-hq-mcp
npm install
npm run buildAdd this to claude_desktop_config.json
<YOUR_PATH_TO_LATTICE_HQ_MCP> is the folder you cloned into, and <YOUR_COMPANY> is your Lattice subdomain.
CLAUDE DESKTOP — LOCAL BUILD · JSON
{
"mcpServers": {
"lattice-hq": {
"command": "node",
"args": [
"<YOUR_PATH_TO_LATTICE_HQ_MCP>/dist/index.js"
],
"env": {
"LATTICE_API_URL": "https://<YOUR_COMPANY>.latticehq.com",
"LATTICE_API_TOKEN": "<YOUR_LATTICE_API_TOKEN>"
}
}
}
}Any MCP client — global install
ANY MCP CLIENT — GLOBAL INSTALL · TERMINAL
npm install -g lattice-hq-mcp-server
LATTICE_API_URL=https://<YOUR_COMPANY>.latticehq.com lattice-hq-mcp-server --api-key=<YOUR_API_KEY> --stdio
