FormsMCP

com.formsmcpPublished by formsmcp.comOfficial publisherv0.1.0Updated Oct 30, 2026

Hosted form backend for coding agents: create form endpoints, verify submissions, manage webhooks.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Hosted form backend for coding agents: create form endpoints, verify submissions and manage webhooks from the assistant.

What you can do
  • Create and manage hosted form endpoints for websites and apps
  • Verify and inspect incoming form submissions
  • Manage webhooks tied to form submissions
When to use it
Useful when an assistant is building a site or app that needs a working form backend without writing and hosting one, or when you want submissions and webhook delivery handled by a hosted service.
Requirements
A remote MCP endpoint reached over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared.
Before you install
The server handles form submissions, which may contain personal data from end users, and forwards them to a third party service and to configured webhooks. Creating or changing endpoints and webhooks modifies live configuration; review what is created before relying on it.

Installation

In SourceWeft

  1. Open FormsMCP 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/com.formsmcp%2Fformsmcp/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": {
    "formsmcp": {
      "type": "http",
      "url": "https://api.formsmcp.com/mcp"
    }
  }
}

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. v0.1.0LatestOct 30, 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.