Unify

A working server exists but somebody other than the vendor built it. It can be abandoned without the vendor noticing. The status was established by hand on 2026-08-24. On 2026-09-04 the recorded URL was a reachable repository or package: a server you install and run on your own machine over stdio. Callable after an install, not a remote endpoint.

mcp_status, verbatim from the file:

community

mcp_url, verbatim from the file:

https://github.com/footcarts/unify-mcp

• https://github.com/footcarts/unify-mcp

A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything.

This list came from a repo the vendor does not own. Those are that author's tools for the vendor's API, not the vendor's own published surface, and the two must not be read as the same thing.

• create_unify_task
  Create a follow-up task on a Unify person. Type is the task category (PHONE_CALL, EMAIL, etc), priority is HIGH/MEDIUM/LOW, dueAt is an ISO timestamp.
  evidence: in the server source · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_unify_company
  Fetch a Unify company by id or domain. Returns full record: address, industry, description, revenue, employeeCount, intent, recordOwner, social links, plus all custom fields.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_unify_current_user
  Identity of the logged-in user (id, email, role, tenant, full permission flags).
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_unify_person_draft_note
  Get the current draft note (if any) for a Unify person.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_unify_play
  Fetch a play definition (publishedObjectType, owner, isPaused, settings, retrigger config).
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_unify_unseen_task_count
  Number of unseen tasks for the current user.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• list_unify_folders
  List folder tree for an entity type (LIST, AUDIENCE, SEQUENCE). Use to navigate organization structure.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• list_unify_mailboxes
  List sending mailboxes (id, emailAddress, displayName, primaryUser, provider, isPaused, isUnauthorized).
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• list_unify_plays
  List plays. Filter by objectType to get only PERSON-targeting or COMPANY-targeting plays.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• list_unify_snippets
  List snippets (reusable content blocks for emails, including SMART snippets with AI prompts).
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• post_unify_person_note
  Publish a note on a Unify person record. Reuses an existing draft if one is open for the current user; otherwise creates+publishes. The body is HTML - wrap text content in <div class=
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• search_unify_companies
  Free-text search Unify companies by name/domain. Returns id, name, domain, address, employee count, revenue, intent.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• trigger_unify_play
  Trigger a play for one or more people/companies (object ids). Returns immediately; the play runs async.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface

141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the tools index.

This is a third party's CLI. It was published by somebody other than the vendor, so it is that author's surface for the vendor's API and not the vendor's published surface. The two must not be read as the same thing.

Install, as the source shows it:

pip install unify-cli

quoted from https://pypi.org/project/unify-cli/ on 2026-09-27, via pypi, a third party source

Packages seen, with the version on 2026-09-27:

• pypi: unify-cli 3.6.2, third party
• pypi: unify-cli 3.6.2, third party

A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27.

api_gate, verbatim from the file:

paid, self-serve for the app (Free/$0, Base $20/seat/mo, Pro $60/seat/mo); "Open API + webhooks" is gated to the custom-priced Business tier only

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:

• https://github.com/footcarts/unify-mcp

github.com/unifygtm tied to the vendor by rule 3, account website https://unifygtm.com has the vendor's domain, confidence strong

The five most recently pushed, on 2026-09-08:

Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.

• Search people by criteria
• Build a target account list
• Fetch buyer intent signals
• Track job changes
• Detect a company's tech stack
• Detect a funding or news event
• Run an email sequence
• Draft personalized outreach

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.

• https://www.unifygtm.com
• https://www.unifygtm.com/pricing
• https://github.com/footcarts/unify-mcp

3 source URLs. Raw sources field, verbatim:

https://www.unifygtm.com, https://www.unifygtm.com/pricing, https://github.com/footcarts/unify-mcp

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.