docs.rs failed to build vigy-mcp-0.1.5
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build:
vigy-mcp-0.1.4
MCP server for vigy.
Exposes the runtime CRUD surface as MCP tools so Claude (and other MCP clients) can drive the registry from a chat. Tools mirror the REST/GraphQL/gRPC operations; semantics identical.
Implementation status
v0.1 ships the tool catalog — the JSON Schemas + tool descriptions
a host's MCP server can re-export. Transport wiring (stdio JSON-RPC
vs SSE vs http+stream) is left to the host (mado's kaname MCP
server, or a standalone vigy-mcp binary in a follow-up).
This split keeps the crate transport-agnostic — usable both as the MCP backbone of mado and as a sidecar daemon when vigy runs out-of-process.