Falaah Falaah AI

Getting Started with Muin in Claude

Step-by-step setup for connecting Claude to Muin: existing admins, people new to Muin, staff members, and developers using Claude Code with an API key.

Pick the path that matches you. Every path ends with Claude answering from your own Muin records.

You are Go to
An owner or admin who already uses Muin A. Existing Muin admin
New to Muin B. New to Muin
A staff member in an organization that uses Muin C. Staff member
A developer working in Claude Code D. Developer on Claude Code

The Muin connector address is the same for everyone:

https://muin-api.falaah.ai/api/v1/mcp

Muin is not yet listed in Claude’s connector directory. Until it is, you add Muin as a custom connector, as shown below.

A. Existing Muin admin

  1. In Claude, open Customize → Connectors.
  2. Choose + Add, then Add custom connector.
  3. Enter the name Muin and the connector address above. Choose Continue.
  4. Claude opens the Muin sign-in page. Sign in as you normally do.
  5. Muin shows an approval screen naming Claude and your organization. Review what Claude will be able to do and choose Allow access.
  6. You return to Claude. Choose Add to finish.
  7. In a new chat, choose + at the lower left, then Connectors, and turn Muin on.
  8. Ask: “List my Muin tools.” Claude should list them.

On a Claude Team or Enterprise plan, an owner adds the connector for everyone under Organization settings → Connectors → Add → Custom → Web. Each person then chooses Connect on it and signs in to Muin with their own account.

In Muin, Settings → Organization → Integrations → Connect to Claude shows the same address with a copy button, and Settings → Organization → Connected Apps lists every app you have approved.

B. New to Muin

  1. Follow steps 1 to 3 of path A.
  2. On the Muin sign-in page, choose Create an account.
  3. Create your account and your organization, and verify your email address.
  4. Muin returns you to the approval screen. Choose Allow access.
  5. Finish in Claude as in steps 6 to 8 of path A.

A new organization has no records yet, so the first answers will be empty. Add your funds, donors and contributions in Muin, then ask again. If you use the Muin plugin in Claude Code (path D), ask “Set me up with Muin” for a first-run checklist. See No data yet in the FAQ.

C. Staff member

  1. Ask your Muin admin whether your organization uses Claude with Muin. On a Claude Team or Enterprise plan, the connector may already be in your list under Customize → Connectors. Choose Connect on it.
  2. If it is not there, add it yourself with steps 1 to 3 of path A.
  3. Sign in to Muin with your own account and choose Allow access.

What Claude can see follows your Muin role. If your role covers HR, Claude can answer HR questions. If your role does not cover finance, Muin refuses finance requests and tells Claude which permission is missing. To get more access, ask your Muin admin to change your role. Claude cannot widen it.

A Muin member can approve read access. Letting Claude make changes needs an owner or admin account.

D. Developer on Claude Code

Claude Code can use the same sign-in as paths A to C. Use an API key when there is no browser to sign in with, such as a server or a script.

With the Muin plugin (sign-in)

/plugin marketplace add falaah-ai/muin-cowork-plugins
/plugin install muin-nonprofit@muin-cowork-plugins

The plugin connects to the Muin address above and asks you to sign in the first time you use it.

With an API key

  1. In Muin, an owner or admin opens Settings → Organization → Integrations → Connect to Claude.
  2. Under Generate a connection key, choose read-only or read and write. Read-only is the safer start.
  3. Copy the key. It is shown only once.
  4. Store it in an environment variable named MUIN_API_KEY.
  5. Add this to your project’s .mcp.json:
{
  "mcpServers": {
    "muin": {
      "type": "http",
      "url": "https://muin-api.falaah.ai/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${MUIN_API_KEY}"
      }
    }
  }
}
  1. Start Claude Code and ask it to list its Muin tools.

The key reaches only the organization it was created in. Delete it under Settings → Organization → Integrations → API Keys to end access.

Next