Formeo

io.formeoPublished by formeo.iov0.2.0Updated Oct 29, 2026

Build and publish Formeo forms, read and export submissions, and get embed code from AI agents

VerifiedSTDIODesktop onlyProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Local MCP server that lets an AI assistant build and publish Formeo forms, read and export submissions, and fetch embed code.

What you can do
  • Create and publish forms in a Formeo organization
  • Read and export form submissions
  • Retrieve embed code for published forms
  • Point the server at a self-hosted Formeo instance or custom API origin
When to use it
Useful when you manage forms on Formeo and want an assistant to draft and publish them, review or export incoming submissions, or hand you embed snippets without switching to the web UI.
Requirements
Runs locally over stdio via npx from the npm package @draggable/formeo-mcp-server, so Node.js is needed. Requires a Formeo organization API key in FORMEO_API_KEY, created under Developer > API Keys. Optional overrides: FORMEO_API_URL, FORMEO_FORMS_URL and FORMEO_URL for self-hosted setups. Desktop client only.
Before you install
The API key grants access to your Formeo organization; keep it out of shared configs and logs. The server can publish forms and read or export submissions, which exposes respondent data to the assistant and its model provider. Overriding the URL variables sends your key to whatever endpoint you configure.

Installation

In SourceWeft

  1. Open Formeo 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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

1
  1. v0.2.0LatestOct 29, 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.