Website & Embed
MCP Server
Permission-scoped nonprofit data via Model Context Protocol
The production Gratona MCP endpoint lets deliberately configured compatible clients retrieve permitted nonprofit records through structured tools. Authentication, scopes, and Gratona permissions all apply. The public tool surface is read-only by default; hidden mutation tools are not part of the current connector launch.
The Problem
AI tools are transforming how organizations work, but without a structured integration point, connecting AI agents to your nonprofit data requires custom API wrappers and complex prompt engineering.
The Solution
With the Gratona MCP server, compatible clients use governed, structured tools to query permitted nonprofit data without building a separate API wrapper for every question.
How it works
Connect a compatible client
Deliberately configure an MCP-compatible client against the Gratona endpoint and authenticate with your Gratona account.
Query with natural language
Ask questions like "Which donors gave more than $1,000 last quarter?" or "Show me all unsponsored children in the Guatemala program."
Review permitted results
The client receives only records allowed by the connected user's scopes and Gratona permissions. Operational changes remain in supported Gratona workflows.
How this feeds Tali's work queue
Every mcp server signal becomes an owned, reviewed action on your team's queue
In Gratona, the context this captures lives on one record and rolls up into Tali's daily queue. Tali, your AI development teammate, turns it into an owned next action with a deadline, prepares the next step in your voice with citations, and your team reviews and approves before anything goes out. Tali adds development capacity and does not replace your team.
Gratona is the platform underneath: donor records, giving pages, sponsorships, communications, reporting, tasks, approvals, and audit history on one system.
Source context, owner, deadline, AI draft, your approval