Developer · Local MCP server
Morningform
Stdio MCP proxy for MorningForm - bridges Claude Code to MorningForm HTTPS MCP server.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.contactxyz-admin/morningform- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-05-14
- Updated
- 2026-05-14
- Publisher
- contactxyz-admin (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/contactxyz-admin) · how
- Repository
- github.com/contactxyz-admin/morning-form
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @morningform/mcp | 0.1.0 | stdio |
How to connect Morningform
Morningform runs locally from a Node.js package published to the npm registry: @morningform/mcp version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @morningform/mcp@0.1.0. It reads these environment variables: MORNINGFORM_TOKEN (required, secret) and MORNINGFORM_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"morningform": {
"command": "npx",
"args": [
"-y",
"@morningform/mcp@0.1.0"
],
"env": {
"MORNINGFORM_TOKEN": "<secret>",
"MORNINGFORM_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| MonitoringGoogle reviews API - fetch reviews from Google, Trustpilot, TripAdvisor, G2 + 50 platforms. | Remote · HTTPLive check: sign-in required |
| Monitoring AIopsGoverned SolarWinds Orion + PRTG + Zabbix ops: SWQL, alert rollup, health, 42 tools. | Local · stdio |
| Monte CarloData + AI observability - monitor and troubleshoot production-grade agents and the context they use. | Remote · HTTPLive check: sign-in required |
| MooringGit and GitHub operations - repo status, diffs, branches, PRs, issues, and Actions. | Local · stdio |
| Mosta Net1 MCP server, 13 databases, zero config. Multi-protocol transport with Auth + RBAC. | Local · stdio |
| MotionSpec - verified web motion (reduced-motion / WCAG)Deterministic motion compiler + validator: reports WCAG 2.2.2 pause-path candidates, fail-closed. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Mova Flat RunnerGoverned AI workflows with human approval gates and audit trails for Claude and MCP clients. | Local · stdio |
| MOVA MCP ConnectorThin MOVA MCP proxy for bindings, transport resolution, and upstream tools/call execution. | Local · HTTP |