MCP servers · cloudcorprecords

formchime: contact forms and webhooks via Formgong's hosted MCP server

A local MCP bridge to Formgong's hosted server for creating website contact forms, getting embed snippets, reading submissions and managing webhooks.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

formchime is a local bridge to Formgong's hosted MCP server. It exposes tools to list and create contact forms, return ready-to-paste form code with the access key, read recent submissions without IP or browser data, and list, add or delete webhooks that POST each new submission as signed JSON to a public HTTPS URL. It also lists Formgong's free, MIT-licensed website templates, each with a contact or quote form already wired to Formgong, filterable by topic. The bridge keeps no state of its own: it forwards each tool call upstream and returns the result unchanged.

It suits a site owner or developer who wants to set up a contact form on a website, place its embed code on a page, review incoming submissions, or forward them to an endpoint they control. Spam submissions are excluded from listings unless requested.

It runs as a stdio MCP server, can be called from the command line with one JSON argument per tool, and is also available as a Docker container whose default command starts the MCP server. Failed upstream calls are returned as errors whose text begins with "formchime error:". The test suite runs against a stubbed upstream and makes no live network calls.

Limitations and requirements

Form and webhook changes act on the caller's own Formgong workspace. The upstream endpoint defaults to Formgong's hosted server and can be overridden with FORMGONG_MCP_URL. FORMGONG_API_KEY is optional: when set, requests carry a Bearer token for clients using a personal API token instead of OAuth; when unset, no auth header is sent. Webhook URLs must be public HTTPS endpoints.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.CloudCorpRecords/formchime

    Create contact forms, get embed snippets, and read recent submissions and webhooks.

    v0.1.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
cloudflare

Cloudflare MCP servers

Cloudflare's hosted MCP servers for its products: documentation search, sandbox containers, browser rendering, Radar internet data, logs and analytics, Workers and more.

4.5K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
microsoft

Playwright MCP (browser automation)

Microsoft's MCP server that lets an AI assistant open web pages, click, type and read them through a real browser, using the page structure instead of screenshots.

39.6K GitHub starsTesting & QAWeb, search & browser
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026