About mova-flat-runner
Governed AI workflows with human approval gates and audit trails for Claude and MCP clients
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y mova-mcpMOVA_API_KEYSecretMOVA API key. Use test-key-001 to get started without registration.LLM_KEYSecretOpenRouter API key (sk-or-v1-...). Required for LLM analysis steps.LLM_MODELOpenRouter model ID for analysis steps.MOVA_API_URLOverride the MOVA API base URL.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
7Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| inputs | object | Yes | Contract inputs per the DataSpec in the manifest. Read mova://contracts/{contract_type}/manifest first. |
| contract_type | string | Yes | Built-in type: invoice | po | trade | aml | complaint | compliance | credit | supply_chain | churn | contract_gen |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.