Thin MOVA MCP proxy for bindings, transport resolution, and upstream tools/call execution.
{
"mcpServers": {
"io-github-mova-compact-mova-mcp-connector": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Thin MOVA MCP proxy for bindings, transport resolution, and upstream tools/call execution.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Commit history unknown.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for io.github.mova-compact/mova-mcp-connector and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
mova-mcp-connector is the thin Rust MCP server that sits above the existing MOVA platform connector model.
Current role:
mcp_doormcp_doormcp_doorThis service is intentionally separate from:
mova-tool-sdk which stays Python-first and user-facingmova-state-1.5 which remains the operational truthCurrent release state:
mcp_doorendpoint_ref and secret_ref can be resolved from local transport mapsPublic docs:
Current endpoints:
GET /healthGET /v1/connectors/:connector_idGET /v1/bindings/:binding_idPOST /v1/proxy/preparePOST /v1/proxy/invokePOST /mcpCurrent MCP methods:
initializetools/listtools/callCurrent MCP tools:
mova.connectors.getmova.bindings.getmova.proxy.preparemova.proxy.invokeinitialize and then tools/callendpoint_ref through MOVA_MCP_CONNECTOR_ENDPOINT_REFS_JSONsecret_ref through MOVA_MCP_CONNECTOR_SECRET_REFS_JSON/access/connectors and /access/vault-bindings to enrich business bindings with real platform access metadataupstream_url and headers still work as override or fallbackendpoint_ref and secret_refupstream_urlEnvironment:
MOVA_PLATFORM_URLMCP_DOOR_BASE_URLMOVA_DOOR_BASE_URLMOVA_ADMIN_READ_TOKENMCP_DOOR_GATEWAY_KEY_IDMCP_DOOR_GATEWAY_SHARED_SECRETMCP_DOOR_ACTOR_IDMCP_DOOR_ACTOR_ROLEMCP_DOOR_ACTOR_TYPEMOVA_MCP_CONNECTOR_ENDPOINT_REFS_JSONMOVA_MCP_CONNECTOR_SECRET_REFS_JSONMOVA_MCP_CONNECTOR_BIND_ADDRSee .env.example for a local bootstrap shape.
This repo is the future home of the single MCP connector/proxy mentioned in the production planning work. The current implementation establishes:
mcp_door