FrazzleCRM

com.frazzlecrmPublished by frazzlecrm.comOfficial publisherv1.0.0Updated Oct 24, 2026

CRM + visual automation builder AI agents can drive via MCP: contacts, tags, maps, email/SMS flows.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for FrazzleCRM that lets an assistant work with CRM contacts, tags, maps and email/SMS automation flows.

What you can do
  • Manage CRM contacts and apply tags to them
  • Organize and view contacts on maps
  • Build and drive visual email and SMS automation flows
  • Operate the CRM through AI agents connected over MCP
When to use it
Useful when you want an assistant to read or update a FrazzleCRM workspace — for example maintaining contacts and tags or adjusting email/SMS automation — instead of doing it by hand in the CRM.
Requirements
A remote MCP connection to the FrazzleCRM endpoint over streamable HTTP. Authentication is required: an Authorization header carrying a bearer API key minted in FrazzleCRM under Settings > API Keys, which requires a Pro plan. No local package or environment variables are needed.
Before you install
The API key is a secret sent in the Authorization header; keep it out of logs and shared configs. The server can change CRM data such as contacts, tags and automation flows, and automation may send email or SMS to real people. The key is tied to a paid Pro plan.

Installation

In SourceWeft

  1. Open FrazzleCRM in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/com.frazzlecrm%2Ffrazzlecrm/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.

{
  "mcpServers": {
    "frazzlecrm": {
      "type": "http",
      "url": "https://app.frazzlecrm.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.