EXIGYN AI
Exigyn MCP Server
Give your AI assistant direct, audit-ready access to your Exigyn budget, forecast, workforce, clinical, revenue, and runway data — query everything in natural language, no dashboard navigation required.
Works with
DEMO
Watch it work.
Watch: an AI agent builds a complete BvA dashboard from live Exigyn data in under 60 seconds.
OVERVIEW
What the MCP server does.
Exigyn provides a hosted Model Context Protocol (MCP) server that gives AI assistants direct, role-scoped access to your financial planning model. Once connected, you can build scenarios, push forecast lines, ingest CRO budgets and EDC actuals, recompute runway, and generate board decks using natural language — without ever opening the dashboard.
A typical workflow looks like:
• Discover — list your scenarios, accounts, departments, projects and studies
• Ingest — load CRO budgets, site fees, enrollment actuals, GL actuals and roster
• Plan — write forecast lines, allocations, workforce, CapEx, BD deals, financing
• Report — compute P&L / BS / CF, runway, BvA, clinical accruals and board decks
TOOLS
Exigyn AI Agent capabilities.
Ask in plain language and Exigyn handles the rest — plans and forecasts, headcount, clinical trials, revenue, and cash runway. What you get access to follows your plan: Sandbox is read-only on demo data, Core covers everyday planning, and Full Suite adds clinical, revenue, allocations and CapEx.
CONNECT
Connect in minutes.
All organizations share a single multi-tenant endpoint. Auth determines which org and projects you can see.
PRODUCTION
https://start.exigyn.com/api/mcp
Permissions & Access
MCP authenticates with your Exigyn account. All existing role and per-department/project scopes apply — the MCP client can only see and write data the connected user can already access in the dashboard.
• Admin — full read/write on all modules
• Editor — write within their scoped departments and projects
• Viewer — read-only on scoped data; write tools are blocked
Module availability follows plan tier: Sandbox = read-only on demo data, Core unlocks core planning, Full Suite adds clinical, revenue, allocations and CapEx.
Connecting to the MCP Server
The Exigyn MCP server uses standard OAuth — sign in with your Exigyn credentials and authorize the client. No tokens to copy, no service accounts to manage.
Claude Desktop
Settings → Connectors → Add Custom Connector. Paste the URL below and complete the Exigyn OAuth flow:
https://start.exigyn.com/api/mcp
Claude Code
claude mcp add --transport http exigyn https://start.exigyn.com/api/mcp
Then run /mcp inside Claude Code and complete the OAuth flow in your browser.
ChatGPT
Settings → Connectors → Advanced → enable Developer Mode → add a custom connector with MCP Server URL https://start.exigyn.com/api/mcp and Authentication = OAuth.
Cursor / Other JSON-configured clients
Open ~/.cursor/mcp.json (or your client's MCP config) and add:
{
"mcpServers": {
"exigyn": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://start.exigyn.com/api/mcp"]
}
}
}
Save the file — Cursor will prompt you to authorize with Exigyn on first connect.
SECURITY & AUDIT
Scoped, logged, auditable.
When connected, your AI assistant can read and write to Exigyn on your behalf, scoped to the connected user's role and access. Your Exigyn data is sent to whichever AI provider you choose (Claude, ChatGPT, etc.) — review that provider's data handling policies before connecting.
• Every MCP write is logged to the org audit trail (who, what tool, when, payload)
• Row-Level Security in Supabase enforces org isolation server-side
• Destructive tools (delete_*, full-roster replace) require explicit confirmation and respect dept/project scope
• Budget versions, amendments and accruals are immutable — old versions remain for auditors
Rate Limits
A maximum of 600 MCP requests per hour per user. Bulk-ingestion tools (CRO budgets, enrollment actuals, roster) chunk automatically to stay within payload limits.