Connect your AI

You register one URL with your assistant. Every connector in your tenant becomes available behind it, filtered by the role of whoever is asking. Adding a connector later does not require going back to the assistant, because the endpoint has not changed.

MCP server URLhttps://mcp.msharti.dev/mcp
AuthOAuth 2.1, auto-discovered · no API key to paste
TransportStreamable HTTP · MCP revision 2025-03-26

Pick your assistant

Claude

Customize → Connectors → Add custom connector. OAuth is discovered automatically.

3 steps ChatGPT

Developer Mode, then create a connector with OAuth. Nothing to paste but the URL.

3 steps Microsoft Copilot

Copilot Studio with dynamic discovery, or an API key where DLP policy blocks OAuth.

2 options Cursor & custom MCP

Any MCP 2025-03-26 client. Endpoint table, discovery document and bearer format.

Reference

Before you start

  1. A Msharti account. Sign up free at apps.msharti.dev. The free plan includes nine connectors and 300 calls a day.
  2. At least one connector configured. An assistant with no connectors will connect successfully and then have nothing to call. Start with M-Pesa or KRA, or connect Outlook in a click. See the quickstart.
  3. A role decided. Whoever signs in gets their role's tools, not everything. If you are testing, sign in as an admin; if you are rolling out to a team, read roles and permissions first.

Why there is usually nothing to paste

Modern MCP clients discover the authorisation flow themselves from the server's /.well-known/oauth-authorization-server document. You give the assistant a URL, it works out where to send you to sign in, and you approve the connection in Msharti's own screen. No client secret, no config file, no key in a text editor.

That also means the tool calls run as you. The audit log records a person, the role filter applies to that person, and revoking their seat revokes their assistant's access at the same time. An API key cannot do that, which is why it is the fallback rather than the default.

ℹ️

The "elevated risk" warning is normal. Assistants show it for any custom MCP server, ours included. It reflects that you are adding a third-party tool source, not that something is wrong with the connection.

Verifying it worked

Ask the assistant something only your business systems could answer. If the connection is live, you get a real figure. If it is not, the assistant will answer from general knowledge or say it has no access, which is the tell.

  • "How much came in via M-Pesa yesterday?"
  • "Is supplier PIN P051234567X tax compliant?"
  • "What are my next three calendar events?"

Then confirm it from the other side: the call should appear in Usage and in the audit log within seconds. If the assistant answered but nothing was logged, it did not actually call Msharti. See governance and audit.

Common problems

SymptomUsual cause
Assistant connects, but lists no toolsNo connectors configured yet, or your role's allowlist is empty. Tool discovery returns the list after the role filter.
Some tools missing that a colleague can seeWorking as intended. Their role includes tools yours does not.
Sign-in loop, never completesPop-ups or third-party redirects blocked in the browser, or the assistant pinned to the older SSE transport.
Worked yesterday, fails todayA connector's OAuth token was revoked upstream, or the key was rotated. Check Connectors in the console for an expiry flag.
Calls refused with a quota messageDaily plan quota reached. See limits and plans.