MCP Servers

RaisinDB can expose your content and server-side logic as one or more Model Context Protocol (MCP) servers. You declare a server as content — a raisin:McpServer node — and the database serves it over the MCP Streamable HTTP binding. Agents then call its tools to read/write your data and run your functions, under your access control.

You declare what the server exposes; RaisinDB handles the protocol, tool generation, auth, and dispatch.

MANDATORY: After creating or modifying any .yaml / .node.yaml file in package/, run:

npm run validate

When to use this

• Zero-onboarding data server — auto-generated tools (and optional live resources) over your NodeTypes, no code to write.
• Custom app server — your own tools (RaisinDB functions) exposed to an agent for your end-users.
• A repository can hold many servers, each with its own slug, policy, and auth.

The endpoint