Muin in Claude FAQ: Data, Permissions and Troubleshooting

What data does Claude see?

Claude sees only what Muin returns to a question it asks.
Each answer comes from one of Muin’s tools, such as fund balances or expiring certifications. Claude sees only the tools for Muin modules your organization has turned on.
Claude reaches one organization: the one you approved on the Muin approval screen.
Claude does not get your Muin password.

Your Muin role does. Access is inherited from the role grants of the person who connected, at the level of modules and features.

If your role can see donors, Claude can answer donor questions.
If your role cannot see payroll, Muin refuses payroll requests and tells Claude which permission is missing.
Access is set per module and feature. Muin does not set access record by record.
To change what Claude can see, an admin changes your role in Muin.

A few of Muin’s tools change data. Every other tool only reads. For example:

Tool	What it does
`nonprofit_record_contribution`	Records a contribution
`workflows_transition`	Moves an approval or process instance to its next step

Every tool that changes data returns a preview and waits in your Muin Inbox. The change runs only when you approve it in Muin, on the web or in the Muin Go app. Approving inside Claude, or Claude calling the tool again, does not run it.
Only an owner or admin can approve a connection that is allowed to change data.
A member can approve a read-only connection.
With an API key, the key’s own setting decides: read-only, or read and write.

The full list is in the MCP Tools Reference.

Any of these ends access:

In Muin: Settings → Organization → Connected Apps, then Revoke access and End access now. Claude’s next request is refused.
In Claude: Customize → Connectors, then Remove next to Muin. Team and Enterprise owners can also remove it under Organization settings → Connectors.
For an API key: delete the key in Settings → Organization → Integrations → API Keys.

An approved connection lasts 90 days unless Claude reconnects.

Muin receives only the tool requests Claude sends: which tool, and the inputs for it.
Muin does not receive the rest of your conversation.
Muin records each tool request (tool name, inputs, result summary and time) for your organization.

How Anthropic handles your conversations is covered by Anthropic’s own terms. How Muin handles your data is covered by the Muin privacy policy.

Not yet. Today you add Muin as a custom connector with the address https://muin-api.falaah.ai/api/v1/mcp. The getting started guide has the steps.

Finish the Muin approval screen and choose Allow access. Not now ends the attempt.
Check the Organization line on the approval screen. To use a different organization, choose Not this organization? and switch first.
After you approve, return to Claude within 5 minutes. After that the approval expires and you start again.
If you see You cannot approve this request, your role cannot grant what Claude asked for. Ask an owner or admin to connect, or ask them to change your role.
If you see We do not recognize the app making this request, remove the connector in Claude and add it again.

A new organization has no records, so Claude’s answers come back empty.

Add your funds, donors and contributions in Muin, or import them.
Then ask Claude again.
If you use the Muin plugin in Claude Code, ask “Set me up with Muin” for a first-run checklist.

Your Muin role does not cover that area. Ask your Muin admin for access to the module, then ask again.

In the chat, choose + at the lower left, then Connectors, and check that Muin is turned on.