Describe the feature
Add a kival-mcp binary that exposes Kival through the Model Context Protocol.
kival-mcp should act as a forwarding adapter rather than implementing Kival domain logic itself. It connects to an existing Kival server using a normal API key and translates MCP operations into the existing Kival API/SDK surface.
The adapter should inherit the permissions and identity of its configured API key. Authorization, validation, auditing, and other application semantics remain authoritative in kival-server.
Where practical, equivalent MCP and API operations should have consistent behavior and errors.
Additional context
kival-mcp should not introduce a privileged or parallel access path into Kival.
It should be deployable independently from kival-server and require only the Kival server endpoint and an API key.
Describe the feature
Add a
kival-mcpbinary that exposes Kival through the Model Context Protocol.kival-mcpshould act as a forwarding adapter rather than implementing Kival domain logic itself. It connects to an existing Kival server using a normal API key and translates MCP operations into the existing Kival API/SDK surface.The adapter should inherit the permissions and identity of its configured API key. Authorization, validation, auditing, and other application semantics remain authoritative in
kival-server.Where practical, equivalent MCP and API operations should have consistent behavior and errors.
Additional context
kival-mcpshould not introduce a privileged or parallel access path into Kival.It should be deployable independently from
kival-serverand require only the Kival server endpoint and an API key.