About MOVA MCP Connector
Thin MOVA MCP proxy for bindings, transport resolution, and upstream tools/call execution
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
docker run -i --rm -e MOVA_PLATFORM_URL -e MOVA_ADMIN_READ_TOKEN -e MCP_DOOR_GATEWAY_KEY_ID -e MCP_DOOR_GATEWAY_SHARED_SECRET -e MCP_DOOR_ACTOR_ID ghcr.io/mova-compact/mova-mcp-connector:0.1.0MOVA_PLATFORM_URLBase URL of MOVA State API / mcp_doorMOVA_ADMIN_READ_TOKENSecretRead token for platform connector and binding resolutionMCP_DOOR_GATEWAY_KEY_IDSecretGateway key identifier for signed mcp_door requestsMCP_DOOR_GATEWAY_SHARED_SECRETSecretGateway signing secret for mcp_door requestsMCP_DOOR_ACTOR_IDActor id used for signed gateway requestsLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
ghcr.io/mova-compact/mova-mcp-connector:0.1.0Streamable HTTPTools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
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.