Connect Claude

Claude discovers Msharti's OAuth flow from the server URL, so the whole setup is three steps and nothing sensitive is copied anywhere. Works in the desktop app and at claude.ai.

Server URLhttps://mcp.msharti.dev/mcp
AuthOAuth 2.1 · auto-discovered
Config fileNot required

Add the connector

  1. Open Claude settings. Launch the desktop app or open claude.ai, then go to Customize → Connectors.
  2. Add the Msharti connector. Click Add custom connector, name it Msharti, and paste the server URL: https://mcp.msharti.dev/mcp
  3. Connect and sign in. Click Add → Connect. Claude redirects you to Msharti. Sign in with your account, choose an access level, then click Allow access.
ℹ️

No API key needed. OAuth is discovered from the URL itself. If a guide somewhere tells you to edit claude_desktop_config.json and paste a token, that is the older pattern; you do not need it here.

Check it works

Start a new conversation and ask something only your systems could answer. A real figure means the connection is live.

claude 
How much came in via M-Pesa yesterday, and were there
any suppliers with an expired TCC?

Then open Usage in the Msharti console. The call should appear within seconds, attributed to your name. If Claude answered but nothing was logged, it answered from general knowledge and did not actually reach Msharti.

What Claude can see

Claude is shown the tools your role allows, and nothing else. It does not receive a full list with some entries disabled: tools outside your allowlist are absent from discovery entirely. If a colleague can do something you cannot, that is the role difference, working as designed. See roles and permissions.

Using an API key instead

Only if your environment cannot complete an interactive OAuth flow. Generate a key under Settings → API Keys → New key → Claude, copy the msh_cla_… value, and supply it as a bearer token in the client's connector configuration.

header 
Authorization: Bearer msh_cla_xxxxxxxxxxxxxxxx
⚠️

A key identifies a machine, not a person. The audit log will name the key rather than a human, and permissions come from the role bound to the key at creation. Prefer OAuth wherever it is possible. See OAuth or a key?

Disconnecting

Remove the connector in Claude, and revoke the connection in the Msharti console under Connect. Doing both matters: removing it in Claude alone leaves the authorisation live on our side.