Falaah Falaah AI

Connecting Claude to Muin

Connect Claude to your Muin organization so it can read your records and answer from live data, by signing in to Muin or with an API key.

Muin speaks the Model Context Protocol, so Claude can work directly against your organization’s live records instead of a copy you paste in. You ask Claude a question, Claude calls Muin, and the answer comes back grounded in what your organization actually has.

This page covers the customer-facing setup. For step-by-step instructions, start with Getting started with Muin in Claude. If you are building your own client and want the JSON-RPC handshake, error codes and rate limits, read the MCP Server reference instead.

What is available, and when

Way to connect Status What it means
Add Muin as a custom connector in Claude, sign in to Muin, approve a consent screen, and manage the connection under Connected apps Available The default. Steps in Getting started.
Paste the Muin endpoint into your MCP client and authenticate with an organization API key Available For Claude Code and scripts. Set up in Settings → Integrations → Connect to Claude.
Install Muin from Claude’s connector directory Not yet available Muin is not listed yet. Until it is, you add Muin as a custom connector.

We would rather tell you which row you are in than let you discover it at setup time. The availability column is the only thing that decides what you can do today.

Connect by signing in

  1. In Claude, open Customize → Connectors, choose + Add, then Add custom connector.
  2. Enter the name Muin and the address https://muin-api.falaah.ai/api/v1/mcp.
  3. Sign in to Muin, check the organization on the approval screen, and choose Allow access.

Claude then works as you, with your Muin role. The getting started guide covers new organizations, staff members and Claude Team or Enterprise plans.

Connect with an API key

  1. In Muin, go to Settings → Integrations → API Keys.
  2. Create a key, give it a name that says which assistant it is for, and grant it read permission.
  3. Copy the key immediately. It is not shown again.
  4. In your MCP client, point at the Muin endpoint and send the key as a bearer token:
POST https://muin-api.falaah.ai/api/v1/mcp
Authorization: Bearer muin_your_api_key_here

Ask the assistant to list its Muin tools to confirm the connection.

What Claude can do once connected

The tools below, limited to the Muin modules your organization has turned on:

Family Tools Examples
Non-profit 11 fundraising progress, fund balances, donor stewardship signals, the grant pipeline, Form 990 readiness, saving a grant you found, importing past gifts
Workflow 4 what is pending approval, where a run has reached, advancing an instance
Documents 3 find a document, summarize it, pull an extracted field
Finance 3 spend to date, overdue invoices, account balances
HR and compliance 3 compliance score, policy gaps, expiring certifications
Grounding 3 answer a plain-language question from your own records
Vendor tools arrive when the Vendors module is released.

All but five are read-only. Five can change your records: one records a contribution, one saves a grant to your pipeline, one imports a spreadsheet of past gifts, one advances a workflow instance, and one starts an agent. Everything else looks and never touches.

Claude’s changes wait for your approval in Muin. When Claude calls one of the five, Muin returns a preview of the change and stores it in your Inbox under Waiting for your approval, and tells Claude the change is waiting. It runs only when you approve it in Muin, on the web or in the Muin Go app. Nothing Claude sends counts as approval: not calling the tool again, not a token, and not an accept you click inside Claude. Calling the tool again returns the change’s status. A contribution or an import of gifts, like any money, always needs your click. See Approving Agent Changes.

What stays true regardless of how you connect

  • Scoped to your organization. A credential reaches the organization it was created in and nothing else.
  • Scoped to the person. The assistant sees what the person whose credential it uses is allowed to see, at the level of modules and features.
  • Revocable. Delete the key, or disconnect the app, and access stops immediately.
  • Auditable. Every call is recorded, and you can tag which assistant made it. A change records who approved it, or which of your standing rules did.