Quickstart
Sign up, connect one system, point an assistant at Msharti, ask a question, and see the call in the audit log. About ten minutes end to end. Everything here works on the free plan.
1. Create your tenant
Sign up at apps.msharti.dev. Your account is a tenant: a hard boundary around your connectors, credentials, people and audit history. The free plan gives you nine connectors, 300 calls a day and one seat, which is enough to finish this guide and keep using it.
2. Connect your first system
Open Connectors and pick one. If you want the fastest possible first success, choose one that uses OAuth, such as Outlook: it is two clicks and no credentials to find.
- OAuth connectors. Click Connect. Msharti generates a one-time link for your tenant, the provider shows its own consent screen, and you approve there. Tokens land encrypted and refresh themselves. Nothing to register, no app to create.
- Credential connectors. For M-Pesa Daraja or KRA GavaConnect you paste credentials from that provider's own console. We tell you exactly which values and where to find them, then test the connection automatically before saving.
Connect at least one system before step 3. An assistant pointed at an empty tenant will connect perfectly well and then have nothing to call, which looks like a broken integration but is not.
3. Connect your AI assistant
One URL, whichever assistant you use. OAuth is discovered from it, so there is nothing to paste.
Customize → Connectors → Add custom connector.
ChatGPTDeveloper Mode, then create a connector with OAuth.
Microsoft CopilotCopilot Studio → Tools → Add tool → MCP.
Cursor & customAny MCP 2025-03-26 client. Endpoints and bearer format.
4. Ask something only your systems know
The test that matters is a question a general-purpose model could not possibly answer. If you get a real number back, the whole chain is working.
How much came in via M-Pesa yesterday?
Is supplier PIN P051234567X tax compliant?
Summarise the emails I got about the Q2 budget. 5. Verify it in the audit trail
This is the step that separates "the assistant said something plausible" from "the assistant read our data". Open Usage in the console. Within seconds you should see the call: which tool ran, who ran it, and whether it succeeded.
If the assistant answered but nothing was logged, it answered from general knowledge and never reached Msharti. Name the connector explicitly in your prompt and try again. More detail in governance and audit.
Where to go next
The access plane and the control plane, and what sits in each.
Build a scoped agentGive an agent exactly the tools it needs and prove it cannot exceed them.
Invite your teamSeats, roles and what happens when someone leaves.
Browse the catalogEvery connector and the tools it exposes.
Before you invite anyone else, decide roles. Msharti is not read-only. Some connectors can send email, create records and move money. Which of those belong in which role is a decision worth making deliberately rather than discovering later. Start with roles and permissions.