vigy-mcp 0.1.2

MCP server for vigy — exposes runtime CRUD as MCP tools so Claude (and other MCP clients) can drive the registry.

Coverage
57.14%
4 out of 7 items documented0 out of 3 items with examples
Size
Source code size: 93.51 kB This is the summed size of all the files inside the crates.io package for this release.
Documentation size: 915.41 kB This is the summed size of all files generated by rustdoc for all configured targets
Ø build duration
this release: 34s Average build duration of successful builds.
all releases: 35s Average build duration of successful builds in releases after 2024-10-23.
Links
pleme-io/vigy
0 0 0
crates.io
Dependencies
Versions
Owners

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.