
MOVA MCP Connector
io.github.mova-compactPublished by GitHub account mova-compactv0.1.0Updated Oct 24, 2026
Thin MOVA MCP proxy for bindings, transport resolution, and upstream tools/call execution.
Overview
A thin MOVA proxy that resolves bindings and transport, then forwards tool calls to upstream MOVA services.
- What you can do
- Acts as a proxy between an assistant and MOVA: it resolves platform bindings and transport settings, then executes upstream tools/call requests on the assistant's behalf. It signs gateway requests using a configured actor id, key id and shared secret, and uses a read token to resolve connectors and bindings against the MOVA State API. No individual tools are listed in the manifest, so the available actions depend on the upstream MOVA services it is pointed at.
- When to use it
- Use it when you already work with a MOVA platform deployment and want an assistant to reach its upstream tools through a single proxy rather than connecting to each service directly.
- Requirements
- Runs locally as a process, or via the published container image with Docker over streamable HTTP. Needs MOVA_PLATFORM_URL plus MCP_DOOR_ACTOR_ID and MCP_DOOR_GATEWAY_KEY_ID, and the secrets MCP_DOOR_GATEWAY_SHARED_SECRET and MOVA_ADMIN_READ_TOKEN. Network access to the MOVA State API and gateway is required.
Installation
In SourceWeft
- Open MOVA MCP Connector in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.