LocalTry AI CRM

A working server exists but somebody other than the vendor built it. It can be abandoned without the vendor noticing. The status was established on 2026-09-12 and the MCP URL has not been probed live yet.

mcp_status, verbatim from the file:

community

mcp_url, verbatim from the file:

https://github.com/philly88r/localtry-mcp

• https://github.com/philly88r/localtry-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_or_update_crm_record
  Create or update a validated CRM record.
  evidence: in a README table · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• create_workflow_agent
  Describe and save a tenant-owned AI agent for use in Flow Studio workflows.
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_recent_activity
  Review recent CRM, workflow, and customization activity.
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_workspace_customization_status
  Read the latest customization conversation, progress, questions, and result.
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_workspace_overview
  Inspect the connected business's pages, modules, fields, workflows, integrations, and customization history.
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• list_workspace_versions
  Review the workspace's customization history.
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• request_workspace_customization
  Submit the same tenant-scoped engineering request as the Customize Workspace prompt.
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• restore_workspace_version
  Restore an approved earlier version for the connected workspace.
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• run_localtry_command
  Use LocalTry Command for verified, multi-step CRM and business operations.
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• run_social_research
  Start one public social or web research search and save it in the connected workspace.
  evidence: in a README table · calling it writes · from a third party repo, so these are that author's tools, not the vendor's published surface
• run_workflow
  Run one of the business's saved workflows.
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• search_crm
  Search tenant-scoped CRM records without exposing raw SQL.
  evidence: in a README table · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• search_localtry_features
  Find the exact registered LocalTry page, action, agent, integration, or tenant addition before acting.
  evidence: in a README table · 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.

No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.

api_gate, verbatim from the file:

unknown

949 of 1252 entries carry an unknown gate. Unknown is a legal answer and it ships as unknown rather than as a guess.

https://localtry.com/docs

No documentation text is reproduced anywhere on this site. Read the vendor page for the prose. The structured docs digest specced in SPEC section 3 has not been built or crawled: docs_digest is null on every entry in this build.

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/philly88r/localtry-mcp

No GitHub organisation could be tied to localtry.com with evidence on 2026-09-15.

Recorded by the harvest: not checked: gh CLI missing or not logged in.

No job tag on this entry.

981 of 1,252 entries are untagged. An empty list here means nobody has tagged this, not that the tool does nothing. The vocabulary is closed, so a tool whose job is genuinely not in it stays blank rather than being forced into the nearest tag.

• https://localtry.com/mcp
• https://localtry.com/docs
• https://localtry.com/developers
• https://github.com/philly88r/localtry-mcp

4 source URLs. Raw sources field, verbatim:

https://localtry.com/mcp, https://localtry.com/docs, https://localtry.com/developers, https://github.com/philly88r/localtry-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.