For Providers
Providers are healthcare platforms that integrate pharmacy connectivity into their applications — telemedicine apps prescribing medications, EMR systems managing patient prescriptions, diagnostics platforms ordering meds for patients, or any healthcare tool that needs pharmacy access.
What you can do
- Manage customers — Create, view, update, and search patients in your organisation
- Search formulary — Browse the medication catalogue across 1000+ pharmacies
- Create and manage orders — Place orders on behalf of patients, track status, view analytics
- Manage dispensary plans — List plans and enrol customers
- Access analytics — Order stats, trends, and platform-level analytics
- Wallet and transactions — Check balance, view transaction history, manage virtual accounts
- Team management — Add users to your organisation, view profiles
- Configuration — Edit provider info, upload logo, set payment type, configure low-balance alerts
How it works
- Install the Famasi agent for your platform (Claude Code, Codex, or Generic MCP)
- Authenticate with your provider ID and API key
- Use natural language to manage your pharmacy operations
The agent knows your provider context from .famasi/provider-link.json and uses the MCP server for all API calls — it never guesses endpoint shapes.
Example session
# 1. Installnpx @famasi/agents@latest install claude-code
# 2. Link providernpx @famasi/agents@latest link provider --provider-id YOUR_PROVIDER_ID
# 3. Start Claude CodeclaudeYou: "Search the formulary for Amoxicillin 500mg"
Agent: → calls fetchFormularyForProvider Found 12 results for "Amoxicillin 500mg": [formulary results with prices and availability]
You: "Create an order for customer +2348012345678 — 2x Amoxicillin 500mg"
Agent: I'll create this order. Please confirm: - Customer: +2348012345678 - Amoxicillin 500mg × 2 - Total: ₦4,800
Proceed?
You: "Yes"
Agent: → calls createNewProviderOrderController ✓ Order created. Order ID: ORD-67890
You: "What's my wallet balance?"
Agent: → calls getProviderWalletBalance Available: ₦245,000 Pending: ₦12,400Agent behaviour
The Famasi provider agent follows these rules across all platforms:
- Prefers linked context — Uses provider identity from
.famasi/provider-link.json - Uses configured MCP — Never guesses endpoint shapes, always uses the MCP server
- Separates read and write — Read operations (GET) run freely; write operations (POST/PUT) always ask for confirmation
- Cites operations — References
operationIdwhen calling tools so you can verify what’s being called - Recommends doctor — Suggests
npx @famasi/agents@latest doctorwhen configuration looks incomplete
Available platforms
| Platform | What you get | Install |
|---|---|---|
| Claude Code | MCP server + agent persona + slash command | npx @famasi/agents@latest install claude-code |
| Codex | MCP server + skill file + AGENTS.md | npx @famasi/agents@latest install codex |
| Generic MCP | MCP server config only | npx @famasi/agents@latest install generic-mcp |
Use Claude Code or Codex when you want agent instructions and platform-specific behaviour. Use Generic MCP when your client isn’t one of these, or you want the minimal config.
Authentication
Providers authenticate with a provider ID and API key. Credentials are stored locally in .famasi/provider-link.json and .mcp.json.
Tools
26 API operations plus 2 documentation tools, organised across authentication, customer management, plans, formulary, orders, analytics, users, provider settings, and wallet.