Merge's whole premise is that you write against one schema instead of twenty HR and ATS APIs, and the server carries that through: the tool list is derived from the Linked Account, so the same setup serves a Workday customer and a Greenhouse customer. The flip side is that you cannot read the tool list from this page — it depends on the account you connect.
The official MCP server for Merge. It talks to the Merge API on behalf of one Linked Account, and the tools it offers are generated from that account's schema — so an HRIS account gets employee tools, an ATS account gets candidate and job tools.
- Tools built at startup from your Merge API schema: retrieve an entity, list entities, create and update — the exact set depends on the category and the scopes your Linked Account allows
- Scope control on the launch command — pass `--scopes` with entries shaped `<category>.<CommonModel>:<permission>`, for example `hris.Employee:read` or `ats.Candidate:write`. With no scopes given, everything available is enabled
- Scopes are validated against the Linked Account, so a scope the account cannot serve produces no tools rather than failing calls later
- Download tools are not supported yet
Python 3.10 or higher and `uv`. Run with `uvx merge-mcp` — if `uvx` is not on your client's PATH, use its absolute path. Two environment variables are required: `MERGE_API_KEY` and `MERGE_ACCOUNT_TOKEN` (the Linked Account token). `MERGE_TENANT` is optional and accepts `US`, `EU` or `APAC`, defaulting to `US`. Package version 0.1.4.
One command plus a key — uvx merge-mcp, then supply credentials