Docs/AI & agents

Raiz’d MCP server

Connect your own AI agent to query your Raiz’d analytics and act on it, over a standard MCP endpoint.

Raiz’d ships an MCP (Model Context Protocol) server so your own AI assistant can read your fundraising data and take actions on your behalf — for example, “which investors opened my deck this week, and draft a follow-up.”

Endpoint & protocol

The server is JSON-RPC 2.0 over HTTP POST (Streamable HTTP, JSON responses) at /api/mcp. It implements the standard initialize, ping, tools/list, and tools/call methods.

Authentication

Use your own access token
Authenticate with your Raiz’d Supabase access token as a Bearer token. The server runs every tool as you — it scopes to your auth.uid(), never the service role — so an agent can only ever see and act on your own data.

Available tools

  • engagement_overview — your overall deck engagement.
  • network_benchmarks — the “you vs. the network” aggregates.
  • list_documents — your uploaded decks.
  • list_links — your links, including agent-view counts.
  • link_analytics — per-slide analytics for a link.
  • list_investors — your pipeline.
  • create_link — create a new trackable link.

Point any MCP-capable client (such as Claude) at the endpoint with your token, and these tools appear automatically.

PreviousAgent-ready decksNextAI brief drafting