Wufoo logoMCP server · Content and web

Wufoo MCP server

Wufoo in any MCP client, through Memtro: Wufoo does not publish this server. Memtro's Wufoo connector reads Wufoo through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Wufoo online forms: the account's forms with today's entry counts, a form's fields and choices, the entries submitted to a form with their structured answers (choices, ratings, numbers, dates; names, contact details and free text are withheld), entry counts by date, the team's comments on entries, and the reports. When asked, can submit an entry to a form.

Reads

  • wufoo_formsWufoo forms this key's user can see: name, hash, URL name, description, whether public, language, start and end dates, entry limit…
  • wufoo_form_fieldsA Wufoo form's fields: API id (Field1, Field105 …), title, type, whether required, page, instructions, sub-fields and choices…
  • wufoo_entriesEntries submitted to a Wufoo form, newest first by default: entry id, when created and edited, and each structured answer (checkbox, multiple choice…
  • wufoo_entry_countHow many entries a Wufoo form has, optionally only those created in a date window (Pacific time) or after an entry id.
  • wufoo_commentsComments the team has made on a Wufoo form's entries in the Entry Manager: the entry, the text, who commented and when.
  • wufoo_reportsWufoo reports this key's user can see: name, hash, URL name, description, whether public, and when created and updated.

Acts, when you ask

These change something in Wufoo. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • wufoo_submit_entrySubmit an entry to a Wufoo form, as if somebody had filled it in: it must pass the form's validation and limits…

Connect it

First connect Wufoo on Dashboard → Connections, then add Memtro to your client once. The Wufoo tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Wufoo connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › How many entries did the event sign-up form get this week?
  • › Which session did most people choose on the sign-up form?
  • › What fields does the feedback form have?
  • › What comments has the team left on recent entries?
  • › Submit a test entry to the contact form

Questions

Is this an official Wufoo MCP server?
No. It is Memtro's MCP server with Memtro's Wufoo connector behind it: the connector reads Wufoo through its API with the credentials you connect on Dashboard → Connections, and Wufoo publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Wufoo?
Only when you ask, and only what it has been granted: submit an entry to a form (recorded as a real submission; the form's notification and confirmation emails may go). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Content and web

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time