Connectors & tools
A connector is an isolated server that speaks to exactly one business system. A tool is one specific thing an AI can ask that connector to do. Msharti ships 26 connectors exposing 149 tools, and the unit of governance is the tool, not the connector.
Anatomy of a connector
Take M-Pesa Daraja. The connector is one container. Inside it are 9 tools, each of which is a named, individually callable operation:
mpesa_pull_register
mpesa_pull_transactions
mpesa_collection_summary
check_mpesa_balance
mpesa_c2b_register
mpesa_b2c_payment
mpesa_check_transaction
mpesa_reverse_transaction
mpesa_remit_taxThose names matter. They are what a role's allowlist is written against, what appears in the audit log, and what the assistant sees during tool discovery. When you scope an agent, you are choosing from this list, not from a checkbox marked "M-Pesa".
| Property | What it means |
|---|---|
| Isolation | One isolated container per connector. It decrypts only the credentials for its own system. A fault or compromise in one connector does not expose another. |
| Credentials | Encrypted with AES-256-GCM before storage. The encryption key is held separately from the ciphertext. |
| Auth style | Either OAuth via a Connect Link, or credentials you paste once from the provider's own console. See Connect Links below. |
| Discovery | The gateway asks the connector what tools it has. Adding a tool ships it to every assistant without a client change. |
| Status | Live, beta or roadmap. Shown honestly in the catalog and never presented as more than it is. |
Read tools and write tools
This is the distinction to get right before you invite anyone into the tenant. Msharti is not read-only. Some tools genuinely change the world.
Read
Fetch and return. Safe to hand broadly, and the bulk of the catalogue.
- Query transaction history or balances
- Verify a KRA PIN or check TCC status
- Search a mailbox, read a calendar
- Run a
SELECTagainst a database - Summarise a CRM pipeline
Write
Change something outside Msharti. Scope these deliberately.
- Initiate an M-Pesa B2C payment
- Remit tax, reverse a transaction
- Send or reply to email
- Create a deal, a ticket or a record in a CRM
- Post a message to a channel
Databases are the exception, not the rule. SQL connectors are read-only and the gateway rejects write statements outright. Every other connector can do whatever the underlying system permits, which is why the role allowlist is the real control. See roles and permissions.
Connect Links
For connectors that use OAuth (Microsoft 365, Salesforce, Google, Meta Ads, Sage, Zoho and others) Msharti uses a Connect Link rather than asking you to register an OAuth application of your own.
- Click Connect in the console. Msharti generates a one-time OAuth link scoped to your tenant. There is no app registration step.
- Sign in with the third-party service. Its own consent screen lists exactly what Msharti is asking for. You approve it there, not here.
- Tokens land in your tenant, encrypted. AES-256-GCM, with the key stored separately. Msharti refreshes them before expiry, so you do not reconnect unless you revoke access.
Connect Links use delegated permissions. The assistant can only reach data the signed-in person could already reach. It cannot elevate its own permissions, and connecting it does not grant it more than the human has.
The catalogue
Coverage leans deliberately toward the systems East African businesses actually run on. M-Pesa and KRA are first-class connectors because no global MCP provider models a Daraja transaction, a KRA PIN or a TCC check.
Core Kenya
| Connector | Tools | Status |
|---|---|---|
| M-Pesa Daraja | 9 | live |
| KRA GavaConnect | 16 | live |
Microsoft 365
| Connector | Tools | Status |
|---|---|---|
| Outlook | 8 | live |
| Dynamics 365 | 5 | beta |
| SharePoint | 4 | live |
| Teams | 4 | live |
CRM & Support
| Connector | Tools | Status |
|---|---|---|
| Salesforce | 5 | beta |
| Zendesk | 5 | live |
| HubSpot | 5 | live |
| Zoho CRM | 5 | beta |
Collaboration
| Connector | Tools | Status |
|---|---|---|
| WhatsApp Business | 4 | live |
| Notion | 5 | live |
| Jira | 5 | live |
| Confluence | 4 | beta |
| GitHub | 8 | live |
| Gmail | 8 | live |
| Google Drive | 7 | live |
Database
| Connector | Tools | Status |
|---|---|---|
| PostgreSQL | 5 | live |
| MySQL / MSSQL | 5 | live |
Marketing & Analytics
| Connector | Tools | Status |
|---|---|---|
| Mailchimp | 4 | live |
| Google Analytics | 4 | live |
| Google Sheets | 5 | live |
| Meta Ads | 4 | beta |
| YouTube | 7 | live |
Finance & IT
| Connector | Tools | Status |
|---|---|---|
| Sage | 4 | live |
| ManageEngine | 4 | roadmap |
Systems we do not list
If the system you need is in-house or simply not in the catalogue, a custom connector is built as an engagement rather than something you configure yourself. It arrives governed on the same terms as everything above: isolated container, encrypted credentials, role-scoped tools, audit logging. Typical turnaround is two to five business days.
A self-serve builder that would let you turn an internal API into a governed MCP server without us is Roadmap and is not available today. Tell us what you need in the meantime.