Morningform
Wire Claude Code to MorningForm so your agent can manage forms and workflows on the hosted MorningForm MCP API without custom HTTP glue.
Overview
MorningForm MCP is a Build-phase MCP server that stdio-proxies Claude Code to the MorningForm HTTPS MCP API using a settings-issued bearer token.
What is this MCP server?
- Stdio MCP proxy that forwards tool calls to the production MorningForm HTTPS MCP server
- npm package @morningform/mcp with stdio transport for Claude Code registration
- Bearer auth via MORNINGFORM_TOKEN from MorningForm settings integrations page
- Optional MORNINGFORM_URL override for local dev (controls where the token is sent)
- Version 0.1.0 in the official MCP server schema
- Server schema version 0.1.0
- npm package identifier @morningform/mcp with required secret MORNINGFORM_TOKEN
What problem does it solve?
Solo builders using MorningForm still copy context in and out of Claude because there is no first-class agent bridge to the live form service.
Who is it for?
Indie builders on Claude Code who standardize on MorningForm and want one-token MCP setup without maintaining a custom HTTP client.
Skip if: Teams that do not use MorningForm or anyone who needs form authoring, hosting, or analytics without the MorningForm product.
What do I get? / Deliverables
After registration, your agent can invoke MorningForm MCP tools locally while auth and routing stay centralized on MorningForm’s hosted server.
- Registered local MCP server that proxies to MorningForm HTTPS tools
- Agent-callable MorningForm operations without custom API scripts
Recommended MCP Servers
Journey fit
Canonical shelf is Build → integrations because the package is a stdio proxy that connects a local agent to an external HTTPS MCP endpoint. Subphase integrations fits bridge/proxy servers that register third-party SaaS capabilities inside Claude Code or Cursor.
How it compares
HTTPS-to-stdio MCP bridge, not a standalone forms skill or generic HTTP MCP template.
Common Questions / FAQ
Who is MorningForm MCP for?
Solo and indie builders who run MorningForm and want Claude Code to reach the same MCP tools via a local stdio proxy.
When should I use MorningForm MCP?
Use it when you are in the build phase and need agent-driven access to MorningForm data and actions through the official bearer-token integration.
How do I add MorningForm MCP to my agent?
Install @morningform/mcp from npm, set MORNINGFORM_TOKEN from MorningForm settings, register the stdio server in Claude Code, and only set MORNINGFORM_URL when doing local dev.