Tithe.ly MCP connector
The Tithe.ly connector brings giving accounts, charges, refunds, payment methods and recurring gifts into Elaichi, so Claude, ChatGPT, Cursor and Microsoft Copilot can look them up and act on them within each person's own Tithe.ly access.
- Connects with an API key
- Free 14-day trial
- No credit card
List every recurring charge that was created this month
Working in Tithe.ly with Elaichi
-
Get single Tithe.ly account by ID
-
List all Tithe.ly accounts
-
List all Tithe.ly API accounts
How to connect Tithe.ly to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Tithe.ly MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Tithe.ly MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Tithe.ly MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Tithe.ly MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Tithe.ly MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Tithe.ly to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Tithe.ly through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Tithe.ly is logged.
-
Finance
Find a charge and issue the refund
Pull up a giver's Tithe.ly charge by amount and date, confirm it is the right one, and issue the refund without leaving the chat.
-
Giving
See every recurring gift in one list
Ask for all recurring charges in Tithe.ly, grouped by frequency, and spot the ones that were set up or dropped this month.
-
Front office
Take a one-off gift at the front desk
Save a new payment method for a visitor who wants to give today, run the quick charge, and confirm it went through.
-
Finance
Reconcile the week's giving before the board meeting
List every Tithe.ly charge for the week, total it by account, and have the summary written before Monday morning.
-
Pastoral care
Answer a giver's question on the phone
Look up a donor's recent charges and recurring gifts while they are on the line, and confirm exactly what Tithe.ly received.
-
Operations
Keep organizations and accounts straight across campuses
List every Tithe.ly organization and its accounts, update account details when a campus changes, and set up a new account for a new site.
Try asking
- “List every recurring charge that was created this month”
- “Refund the duplicate charge from Sunday for the Johnson family”
- “Set up a monthly recurring gift for a new giver”
What connecting Tithe.ly gets you
6 screens from Elaichi, each doing one job for your Tithe.ly account.
Ask Elaichi to work across your apps.
List every recurring charge that was created this month
Refund the duplicate charge from Sunday for the Johnson family
Set up a monthly recurring gift for a new giver
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about giving in plain language.
Charges, refunds and recurring gifts answered from live Tithe.ly records, no report to run.
Copy the endpoint
AI apps
One Tithe.ly endpoint for every MCP client.
Claude, ChatGPT and Cursor connect to Tithe.ly through one org endpoint, no SDK, no shared key.
Tool catalog
21 Tithe.ly tools, no code to write.
Accounts, charges, refunds, payment methods and recurring charges, listed and ready without custom code.
Toolboxes
Every team gets its own Tithe.ly toolbox.
Finance refunds, the office takes gifts, each team sees only the Tithe.ly tools it needs.
Shared connections
Share Tithe.ly without sharing the key.
One person connects Tithe.ly, teammates work through it, and nobody else sees the API key.
Audit log
Every Tithe.ly refund has a name on it.
Who issued a charge, refunded a gift or removed a payment method, logged and kept.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Tithe.ly digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch charges
Tithe.ly
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Tithe.ly
Queued
Workflows
A schedule starts the giving digest itself.
Tithe.ly charges are fetched, grouped and drafted into a digest, approved, then posted back.
Tithe.ly health
Refreshed 4 minutes ago · every 15 minutes · from the charges collection
Charges
1,284 ↓ 12%
Refunds
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Charges created
Last 14 days
By team
Share of activity
Finance 34%
Giving 27%
Front office 21%
Main campus 18%
Collections and dashboards
Giving numbers that arrive before anyone asks.
Charges created over 14 days, by team, pulled from Tithe.ly on a schedule with no model.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Tithe.ly
All three can connect Tithe.ly to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Tithe.ly tools | Allow or restrict single Tithe.ly tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Tithe.ly call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Tithe.ly tools for your AI agents
21 tools are ready to call through Elaichi's MCP endpoint the moment you connect Tithe.ly, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Tithe.ly to Claude?
Connect Tithe.ly in Elaichi first: paste your Tithe.ly API key when asked and the connection is ready, with no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and your Tithe.ly accounts, charges and recurring gifts are available in the chat.
Does Tithe.ly work with ChatGPT and Cursor as well as Claude?
Yes. Once Tithe.ly is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Tithe.ly once and every client you use sees it.
What can an AI agent actually do with my Tithe.ly data?
With Tithe.ly connected, an agent can look up a giver's charges, list recurring gifts, create a charge or a quick charge, issue a refund, and add, update or remove a payment method. It can also list your Tithe.ly organizations and accounts and update account details. Short, concrete asks work best, such as refund the fifty dollar charge from Sunday for Maria Lopez.
Does connecting Tithe.ly give the AI access to every organization and account?
No. Every call runs inside the access the connected Tithe.ly key already has, on behalf of the person signed in to Elaichi, so an agent reaches only the Tithe.ly organizations and accounts that access covers. Elaichi can narrow that further with restrictions, and it can never widen it beyond what Tithe.ly already allows.
Can I stop an agent from deleting or changing things in Tithe.ly?
Yes. In Elaichi you can restrict any Tithe.ly action, such as refunding a charge, deleting a payment method or deleting a recurring charge, for a role or for one person. A restricted action still shows in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Tithe.ly connection when someone leaves?
Offboarding someone in Elaichi ends their access to Tithe.ly at once, from every client. A shared Tithe.ly connection keeps working for everyone else on the team. If you want the connection gone, disconnecting Tithe.ly once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Tithe.ly MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Tithe.ly is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Tithe.ly?
Yes. Both let Claude, ChatGPT or Cursor use Tithe.ly. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Tithe.ly call.
How is Elaichi different from Composio for Tithe.ly?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Tithe.ly: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Tithe.ly in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot