ChatGPT App Connector

Gratona exposes an agent connector for authenticated Gratona admins. ChatGPT, Codex, and other MCP clients can use it to search and summarize donor, recipient, sponsorship, donation, dashboard, note, activity, saved-view, and report data that the connected admin is allowed to view. The connector can also expose actions that create or change records when the connected admin has the required scopes and permissions.

Use the production MCP endpoint for public ChatGPT and Codex connections:

https://api.helpyousponsor.com/mcp

Use staging or a short-lived HTTPS tunnel for private developer-mode tests:

https://api-staging.helpyousponsor.com/mcp
What admins can ask

Useful prompts include:

Find a donor by name or email and summarize their profile, giving, sponsorships, notes, and recent activity.

Summarize donations for the last 90 days and fetch one donation record.

Show sponsorship health for a program and fetch one sponsored recipient.

List saved donor views, donation views, reports, and scheduled reports that can help staff plan follow-up work.

Show notes and activity for a specific donor or recipient.

Explain what the connected admin can access in the current Gratona workspace.

When a prompt does not include enough information for a record-specific lookup, the assistant should ask a short follow-up question instead of guessing.

Read tools

Depending on your access, read tools include donor lookup, donor list/search/get, recipient/entity list/get, donation list/get/summary, sponsorship summary, notes list, activity-log list, saved filters/listed views, reports list, dashboard snapshot, dashboard brief, forms list, programs list, system context, standard connector-style search, and record fetch.

Create, update, delete, and archive tools require appropriate scopes and permissions, and may be exposed to full-scope admins.

Authentication and permissions

Production ChatGPT connections should authenticate with OAuth account linking. Private developer-mode smoke tests may use a scoped Gratona API key or bearer token, but production API keys must not be placed in query strings.

Gratona enforces access in layers:

Authentication resolves the admin, API key or OAuth token, scopes, and Gratona workspace.

The primitive registry filters discovery and invocation by primitive scope.

Each primitive applies Gratona group permission sets such as donor forms, program access, reports, notes, activity logs, and dashboard permissions.

Record queries always use the server-derived workspace boundary.

Admins can receive donor PII, custom fields, notes, activity, reports, and saved views when their Gratona permissions allow them. The connector does not redact permitted admin data at the app layer; it avoids exposing secrets, request tokens, API keys, payment processor identifiers, trace IDs, and unrelated internal diagnostics.

MCP discovery endpoints

GET /mcp — public server manifest.

POST /mcp — MCP JSON-RPC requests.

GET /mcp/health — public health check.

GET /.well-known/oauth-protected-resource — protected-resource metadata used for account linking.

GET /.well-known/oauth-authorization-server — OAuth authorization-server metadata.

Unauthenticated tools/list and tools/call requests include OAuth connection guidance with the protected-resource metadata URL. Depending on the MCP protocol version, this appears in MCP error metadata or an HTTP WWW-Authenticate header. The public manifest and discovery endpoints do not require an admin connection.