Formmy

app.formmyPublished by formmy.appv0.1.0Updated Oct 24, 2026

Run WhatsApp AI agents: manage agents, conversations, CRM contacts, orders and RAG docs.

VerifiedSTDIODesktop onlyCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

A local MCP server for Formmy that lets an assistant manage WhatsApp AI agents, conversations, CRM contacts, orders and RAG documents.

What you can do
Manage WhatsApp AI agents and their conversations through the Formmy API, including reading and handling chats. Work with CRM contacts and customer records. Handle orders. Manage RAG documents used as agent knowledge. Limit which tool groups are exposed by choosing toolsets such as orders or contacts.
When to use it
Useful when you run Formmy WhatsApp AI agents and want an assistant to work with the same agents, conversations, contacts, orders and knowledge documents from your desktop.
Requirements
Runs as a local stdio process, installed from the npm package @formmy.app/mcp-server, so Node.js is needed. Requires a Formmy account Secret Key supplied in the FORMMY_SECRET_KEY environment variable. FORMMY_API_URL optionally overrides the API base URL, which defaults to the Formmy service. FORMMY_TOOLSETS optionally limits exposed toolsets. Network access to the Formmy API is required.
Before you install
The server needs a live Formmy account Secret Key (FORMMY_SECRET_KEY); treat it as a sensitive credential and keep it out of shared configuration. It can act on real WhatsApp conversations, CRM contacts, orders and knowledge documents, so assistant actions may change or send customer-facing data. Data is exchanged with the Formmy API over the network. Desktop only.

Installation

In SourceWeft

  1. Open Formmy in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 19, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.