LocalTry AI CRM

io.github.philly88rPublished by GitHub account philly88rv1.0.1Updated Oct 25, 2026

Operate and customize one tenant-isolated LocalTry CRM. ChatGPT plugin coming soon.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

A remote MCP server for operating one LocalTry CRM workspace in plain language, with OAuth-bound, tenant-isolated access to records, workflows and customisation

What you can do
Search tenant-scoped CRM records such as customers, companies, contacts, leads, jobs, estimates and invoices, and create or update validated records without raw SQL access. Inspect the workspace architecture and find registered pages, actions, agents, integrations and tenant additions. Create tenant-owned AI agents for Flow Studio and run saved workflows or multi-step LocalTry Command operations. Submit workspace customisation requests, check their status, review version history and restore an earlier version. Read recent activity and audit history, and start a public social or web research search saved into the workspace.
When to use it
Useful when you want an assistant to work inside an existing LocalTry CRM account: looking up and updating business records, running saved workflows, or requesting and tracking workspace customisations, while keeping each business isolated.
Requirements
Remote streamable HTTP endpoint at mcp.localtry.com; no local runtime or package needed. OAuth 2.1 sign-in to LocalTry is required, with PKCE, dynamic client registration and short-lived access and refresh tokens; the user approves one visible workspace. No LocalTry API key is copied into the client.
Before you install
The server can create and update CRM records, run workflows, submit workspace customisations and restore earlier workspace versions, so changes affect real business data. Restoring a version and customisation requests are consequential workspace changes. Access is bound to the approved user, business, role and permissions, and the client cannot choose a tenant. Research searches are saved into the connected workspace.

Installation

In SourceWeft

  1. Open LocalTry AI CRM in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.philly88r%2Flocaltry-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "localtry-ai-crm": {
      "type": "http",
      "url": "https://mcp.localtry.com/mcp"
    }
  }
}

README

LocalTry MCP

Use LocalTry from ChatGPT and other MCP clients while keeping every business strictly isolated.

LocalTry MCP is a remote Model Context Protocol server for operating a LocalTry CRM with plain-language instructions. It runs on Cloudflare Workers, uses OAuth 2.1, and binds every connection to one verified LocalTry user, business, role, and permission set.

What it enables

  • Search customers, companies, contacts, leads, jobs, estimates, and invoices.
  • Create and update validated CRM records.
  • Create tenant-owned AI agents that become available in Flow Studio.
  • Inspect the complete tenant workspace architecture.
  • Search every registered page, action, agent, integration, and tenant addition.
  • Submit tenant-only workspace customizations through LocalTry Builder.
  • Run saved workflows.
  • Ask LocalTry Command to carry out multi-step business operations.
  • Review customization versions and restore an earlier version.
  • Read a tenant-scoped activity and audit history.

Available tools

ToolPurpose
get_workspace_overviewInspect the connected business's pages, modules, fields, workflows, integrations, and customization history.
search_localtry_featuresFind the exact registered LocalTry page, action, agent, integration, or tenant addition before acting.
search_crmSearch tenant-scoped CRM records without exposing raw SQL.
create_or_update_crm_recordCreate or update a validated CRM record.
create_workflow_agentDescribe and save a tenant-owned AI agent for use in Flow Studio workflows.
request_workspace_customizationSubmit the same tenant-scoped engineering request as the Customize Workspace prompt.
get_workspace_customization_statusRead the latest customization conversation, progress, questions, and result.
list_workspace_versionsReview the workspace's customization history.
restore_workspace_versionRestore an approved earlier version for the connected workspace.
run_workflowRun one of the business's saved workflows.
run_social_researchStart one public social or web research search and save it in the connected workspace.
run_localtry_commandUse LocalTry Command for verified, multi-step CRM and business operations.
get_recent_activityReview recent CRM, workflow, and customization activity.

The tenant boundary

There is one shared MCP service, but every authorization is logically private. The client cannot supply or change a tenant identifier.

text
MCP client  -> LocalTry OAuth consent  -> token bound to user + business + role + scopes  -> LocalTry MCP Worker  -> private Cloudflare service binding  -> LocalTry domain services  -> business-scoped data and workspace runtime

The MCP Worker does not receive a database binding. It can reach LocalTry only through the private service contract in docs/localtry-bridge-contract.md.

Remote endpoint

The production endpoint is live:

text
https://mcp.localtry.com/mcp

Health check:

text
https://mcp.localtry.com/health

Clients discover OAuth 2.1 metadata automatically. Authorization supports PKCE, dynamic client registration, short-lived access tokens, and refresh tokens. Users sign in to LocalTry and approve one visible workspace; no LocalTry API key is copied into the MCP client.

Local development

Requirements: Node.js 20 or newer and a Cloudflare account.

bash
npm installnpm run typesnpm run checknpm run dev

Create an OAuth KV namespace and replace the placeholder namespace ID in wrangler.jsonc:

bash
npx wrangler kv namespace create OAUTH_KV

The LOCALTRY_API service binding must point to the named LocalTryMcpBridge WorkerEntrypoint exported by the LocalTry CRM deployment.

See the bridge contract for the exact trust boundary.

ChatGPT

ChatGPT supports remote MCP apps through developer mode. See docs/chatgpt.md for the connection flow and current plan requirements. Creating a private custom app connects this server to a ChatGPT account or workspace; publishing in the public ChatGPT app directory is a separate OpenAI review process.

The non-secret public-review listing, starter prompts, test cases, and release notes are maintained in docs/openai-submission.md.

Design principles

  • No raw SQL tool.
  • No tenant ID tool argument.
  • No secret-reading tool.
  • Goal-oriented tools instead of mirroring the entire API.
  • Explicit approval for consequential workspace changes.
  • Versioning, audit events, and restore support.
  • Permission checks in both the MCP Worker and the CRM domain layer.

Status

Production is deployed at mcp.localtry.com. OAuth authorization, refresh tokens, MCP initialization, tool discovery, tenant binding, and a live workspace read have been verified end to end. The public Worker reaches the CRM only through a private Cloudflare service binding and has no database binding.

License

MIT

Source: README.md at commit 6384213

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts