Cotribute MCP lets staff at your credit union or community bank ask Claude, ChatGPT, or Microsoft Copilot plain-English questions about your application pipeline — and get answers in seconds. Read-only, audited, and scoped to the same permissions your staff already have.
Works with Claude (web + desktop), ChatGPT Enterprise, and Microsoft Copilot Studio. OAuth 2.1 sign-in. Live at mcp.cotribute.co.
Three real workflows your back office runs every day — and what they look like once Cotribute MCP is wired into your AI tool.
Cotribute MCP is one URL your staff paste into their AI tool. The AI tool handles sign-in through your existing Cotribute account. No new credentials, no new portal, no admin onboarding flow.
A portal admin or staff member opens Settings → Connectors in Claude
(or the equivalent in ChatGPT / Copilot) and pastes
https://mcp.cotribute.co.
The AI tool opens a sign-in tab in the browser. The staff member uses the same email and password they already use for Cotribute. The AI tool never sees the password.
The AI tool now answers questions about your pipeline. It only sees counts and trends — never applicant names, SSNs, or account numbers.
Cotribute records who asked what and when in an append-only audit log. No applicant data is stored in the log — only metadata about the call itself.
Cotribute MCP follows the open Model Context Protocol standard, so the same connector URL works across every major AI client.
Three read-only tools, all aggregate. You won't see applicant names — you'll see counts, percentages, and per-flow distributions. More tools (origination, compliance) are on the v2 roadmap.
Total applications, new in the last 24 hours, pending decisions, unread items, breakdown by decision category (approved / denied / review / canceled / undecided), and an aging distribution by last activity.
Approved / denied / canceled out of total decisions over the last 30 days, plus per-flow application volume. Designed for the weekly "are we converting?" question.
Stalled applications (no activity 7+ days and still undecided), pending counts, and unread counts — each tagged with a severity so the AI can prioritize the answer.
One subscription covers everyone at your institution. Credits are pooled — one staff member's question doesn't burn through another's allowance. A typical user question fans out to 2–3 tool calls (one credit each), so the credit counts below translate to real usage as shown.
Each tool call costs 1 credit. Heavy tools on the v2 roadmap will cost 3 credits. At 100% of your monthly allotment, service continues — Starter shows an upgrade prompt and Plus / Enterprise show an overage notice. We don't hard-block during a busy month.
Cotribute MCP was designed for credit unions and community banks first, not retrofitted from a consumer product. The v1 boundary is deliberately narrow so the security story is short.
The three v1 tools return counts and trends. No tool returns applicant names, SSNs, dates of birth, account numbers, or addresses. There is no v1 write path — the AI tool cannot change anything in Cotribute.
Each staff member's MCP access is scoped by the same Cotribute role they use in the web portal. They can't see flows in the AI tool that they can't see in Cotribute, and they can't see another institution's data — ever.
One row per tool call in an append-only Postgres table. Records who asked, when, which tool, how long it took, the outcome, and the credit cost. No applicant data is ever written to the audit log.
PKCE plus dynamic client registration. The AI tool never sees or stores a staff password — sign-in happens at login.cotribute.co in the staff member's browser. Revoking a Cotribute session immediately revokes MCP access, no deploy required.
If you're already a Cotribute customer, your portal admin can turn this on in five minutes. If you're not, let's talk about whether your institution is a fit.
