FundLoop MCP Server
A safer agent doorway into FundLoop workflows.
FundLoop MCP gives authenticated agents a small, intentional tool surface for workspace summaries, founder project status, payout readiness, and operator visibility without turning the backend into an open command console.
Connection URL
https://{supabase_project_ref}.supabase.co/functions/v1/mcpUse the approved Supabase project ref for Preview or Production. Tool traffic requires a bearer token for the FundLoop actor the agent is representing.
Streamable HTTP
The remote endpoint runs as a Supabase Edge Function while the stdio package remains the local harness for development and smoke tests.
Supabase bearer auth
POST tool traffic validates Supabase user tokens before dispatch. Operator tools additionally require the internal-admin allowlist.
Command-bound backend
Reads and writes reuse the same typed Edge Function and workflow-read boundaries as the web app.
Supported tools
Small enough for agents to reason about.
The tool catalog is intentionally compact. FundLoop exposes workflow intents, not arbitrary SQL, shell access, filesystem access, or generic private APIs.
User workspace and payout readiness
Read identity readiness, participation footprint, current results visibility, and destination-redacted payout route status for the authenticated user.
Founder project operations
List managed projects, inspect monthly-cycle status, create/update crypto contribution routes, record onchain receipts, and create payment drafts through typed Edge commands.
Project member reporting
Read attribution and reporting status for projects the actor can access without exposing private artifacts or raw backend payloads.
Operator visibility
Internal operators can inspect cycle status, observability events, reconciliation visibility, and reporting coverage through read-only tools.
Connect
Use a real FundLoop actor token. Keep the bridge narrow.
The server is designed for first-party and workspace-bound clients first. Public registry publication remains pending until hosted deploy and production smoke gates are complete.
- 1Choose the approved Preview or Production Supabase project ref.
- 2Configure the Streamable HTTP endpoint with the connection URL shown above.
- 3Provide an Authorization header using a Supabase access token for the FundLoop actor.
- 4Run initialize, tools/list, and fundloop.health before calling workflow tools.
- 5Keep fundloop.edge_command.invoke disabled unless a specific integration session explicitly allows it.
Privacy and safety
Agents get summaries, not raw secrets.
MCP outputs redact tokens and secret-like values. User resources omit raw CUBID payloads and payout destinations; operator resources stay hidden unless the actor is allowed.
Review privacy policyExample use cases
What agents can do safely today.
Prepare a founder update
Read a project’s cycle status and turn real contribution, route, and reporting blockers into a concise update.
Review user next steps
Summarize identity readiness, participation state, payout setup, and current results visibility for the authenticated user.
Operator triage
Help internal operators inspect cycle events, reconciliation queues, and reporting gaps without exposing mutation tools.
Directory status
Publication is staged, not rushed.
Changelog
Current public status.
Remote endpoint implemented
The MCP server runs over Streamable HTTP as a Supabase Edge Function and keeps the stdio package as the local harness.
Auth and safety hardened
Supabase JWT validation, operator gating, strict schemas, output redaction, resources, prompts, smoke tests, and observability are in place.
Registry metadata prepared
server.json exists, but public registry publication waits for hosted deploy, production smoke, and directory review gates.
Questions or access requests: support@fundloop.org