Developer · Local MCP server
Mova Flat Runner
Governed AI workflows with human approval gates and audit trails for Claude and MCP clients.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.mova-compact/mova-flat-runner- Version
- 2.0.6
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-04-17
- Updated
- 2026-04-17
- Publisher
- mova-compact (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/mova-compact) · how
- Repository
- github.com/mova-compact/mova-flat-runner
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: node | mova-mcp | 2.0.6 | stdio |
How to connect Mova Flat Runner
Mova Flat Runner runs locally from a Node.js package published to the npm registry: mova-mcp version 2.0.6. 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 mova-mcp@2.0.6; the entry names node as the runtime. It reads these environment variables: MOVA_API_KEY, LLM_KEY, LLM_MODEL and MOVA_API_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": {
"mova-flat-runner": {
"command": "npx",
"args": [
"-y",
"mova-mcp@2.0.6"
],
"env": {
"MOVA_API_KEY": "<value>",
"LLM_KEY": "<value>",
"LLM_MODEL": "<value>",
"MOVA_API_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 from mova-compact (GitHub)
| Server | Runs |
|---|---|
| MOVA MCP ConnectorThin MOVA MCP proxy for bindings, transport resolution, and upstream tools/call execution. | Local · HTTP |
More developer servers
| Server | Runs |
|---|---|
| MooringGit and GitHub operations - repo status, diffs, branches, PRs, issues, and Actions. | Local · stdio |
| MorningformStdio MCP proxy for MorningForm - bridges Claude Code to MorningForm HTTPS MCP server. | 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 |
| MowgliProduct canvas: iterate on your product's design with your coding agent, synced to code. | Remote · HTTPLive check: sign-in required |
| Moxie DocsLiving docs and MCP context for GitHub repos - conventions, gaps, and source-cited pages on merge. | Remote · HTTPLive check: ✓ handshake |
| Moxt WorkspaceBrowse and manage files in your Moxt AI workspace from any MCP client. | Remote · HTTPLive check: sign-in required |