Shelvia
Developer referenceAvailable

Model Context Protocol (MCP)

MCP clients call the same service functions as the REST API. There is no parallel logic, a change to the memory model propagates to both surfaces.

MCP CLIENTClaude · Cursor · …tools.call(...)shelvia_get_project_contextshelvia_search_project_memory/api/mcpStreamable HTTP + JSON-RPCAPPROVED CONTEXTstructured · scopedworkspace-boundsame service as REST

Transport

The MCP endpoint honors both SSE-framed Streamable HTTP and plain JSON-RPC, plus Mcp-Session-Id for session affinity.

POST /api/mcp
Authorization: Bearer $SHELVIA_TOKEN
Content-Type: application/json
Accept: text/event-stream   # SSE-framed, or omit for JSON-RPC

Tools

  • shelvia_get_memory_health
  • shelvia_get_project_context
  • shelvia_search_project_memory
  • shelvia_generate_context_pack
  • shelvia_create_handoff
  • shelvia_regenerate_project_summary
  • shelvia_create_memory_candidate
  • shelvia_log_continuation

Discovery metadata

  • /.well-known/oauth-protected-resource, points at the real authorization server (RFC 9728).
  • /.well-known/oauth-authorization-server, RFC 8414 metadata.

For runnable code samples and the developer reference, see /developers. For the trust model in depth, see /security.