# 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.

Source: https://elaichi.ai/connectors/tithely/

## Facts

| | |
| --- | --- |
| Application | Tithe.ly |
| Category | Payment Gateway |
| AI tools | 21 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Tithe.ly is connected

- 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

## Connect Tithe.ly in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Tithe.ly.
2. Optionally set Share with, then press Connect.
3. Paste a Tithe.ly API key. One person generates a token in Tithe.ly and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Tithe.ly tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Tithe.ly MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Tithe.ly MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Tithe.ly tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Tithe.ly through Elaichi

### Find a charge and issue the refund

Finance. 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.

### See every recurring gift in one list

Giving. Ask for all recurring charges in Tithe.ly, grouped by frequency, and spot the ones that were set up or dropped this month.

### Take a one-off gift at the front desk

Front office. Save a new payment method for a visitor who wants to give today, run the quick charge, and confirm it went through.

### Reconcile the week's giving before the board meeting

Finance. List every Tithe.ly charge for the week, total it by account, and have the summary written before Monday morning.

### Answer a giver's question on the phone

Pastoral care. Look up a donor's recent charges and recurring gifts while they are on the line, and confirm exactly what Tithe.ly received.

### Keep organizations and accounts straight across campuses

Operations. 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.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Tithe.ly connection?

Yes. One person connects Tithe.ly in Elaichi and shares it with the finance or giving team, and nobody else ever sees or handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names who issued a refund or changed a payment method, not the person who first connected Tithe.ly.

### 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.

## All 21 Tithe.ly tools

Every tool below is callable through https://api.elaichi.ai/mcp once Tithe.ly is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Tithe.ly account** (Create). Create an account. Accounts are donor or organization-manager logins; password and pin are the new account's. Required: email, password, pin, first_name, last_name.
- **Get single Tithe.ly account by ID** (Get). Retrieve an account. Required: id.
- **List all Tithe.ly accounts** (List). List all accounts. Every account the API keys can see; api_accounts.list returns only the accounts created through the API. The connector pages through all results (starting_after; limit sets the page size, Tithe.ly's default 10).
- **Update a Tithe.ly account by ID** (Update). Update an account. Required: id.
- **List all Tithe.ly API accounts** (List). List accounts created via API. Only accounts created through the API; accounts.list returns all of them. The connector pages through all results (starting_after; limit sets the page size, Tithe.ly's default 10).
- **Create a Tithe.ly charge refund** (Create). Refund a charge. Refunds the whole charge. Required: charge_id.
- **Create a Tithe.ly charge** (Create). Create a charge. Donor account, payment method, and organization must be setup first. Charges the donor's stored payment method (pm_id from payment_methods.list). amount is in cents. Required: account_id, pm_id, organization_id, amount, giving_type.
- **Get single Tithe.ly charge by ID** (Get). Retrieve a charge. Required: id.
- **List all Tithe.ly charges** (List). List all charges. Either donor or organization must be used to query a list of charges. Pass account_id (the donor) or organization_id. created_after / created_before filter by date. The connector pages through all results (starting_after; limit sets the page size, Tithe.ly's default 10).
- **Get single Tithe.ly organization by ID** (Get). Retrieve an organization. Required: id.
- **List all Tithe.ly organizations** (List). List all organizations. The connector pages through all results (starting_after; limit sets the page size, Tithe.ly's default 10).
- **Create a Tithe.ly payment method** (Create). Create a payment method. Donor account must be setup first. Tokens are generated from Tithely.js. The token is made in the donor's browser, so card details never reach the connector. Required: account_id, token.
- **Delete a Tithe.ly payment method by ID** (Delete). Delete a payment method. Required: id, account_id.
- **Get single Tithe.ly payment method by ID** (Get). Retrieve a payment method. Required: id, account_id.
- **List all Tithe.ly payment methods** (List). List all payment methods. Required: account_id.
- **Update a Tithe.ly payment method by ID** (Update). Update a payment method. Required: id, account_id.
- **Create a Tithe.ly quick charge** (Create). Quick charge. Charge a donor without creating a donor account or storing a payment method. You'll also need a token from Tithely.js. amount is in cents. Required: email, first_name, last_name, token, organization_id, amount, giving_type.
- **Create a Tithe.ly recurring charge** (Create). Create a recurring charge. Donor account, payment method, and organization must be setup first. term: weekly, monthly, bimonthly or fortnightly; start_date a Unix timestamp. amount is in cents. Required: account_id, pm_id, organization_id, amount, giving_type, term, start_date.
- **Delete a Tithe.ly recurring charge by ID** (Delete). Cancel a recurring charge. Note that this will not refund previous charges, but will cancel future recurring charges. Required: id.
- **Get single Tithe.ly recurring charge by ID** (Get). Retrieve a recurring charge. Required: id.
- **List all Tithe.ly recurring charges** (List). List all recurring charges. Either donor or organization must be used to query a list of charges. Pass account_id (the donor) or organization_id. The connector pages through all results (starting_after; limit sets the page size, Tithe.ly's default 10).
