Give your AI assistant a phone line. Connect any MCP-compatible assistant to read calls, notes, and orders—and propose outreach with confirmation.
Reference
The Model Context Protocol, in plain words.
VoiceReach runs an MCP server at https://api.voicereach.app/mcp. Your assistant discovers the tools, calls one, and gets a clear result.
Discovery: AI Catalog and Server Card.
- Read first. Calls, notes, reminders, orders, and catalogs can be read without changing anything.
- Propose, then confirm. An outreach is proposed with a read-back. It only runs after an explicit confirmation.
- Revoke anytime. Keys are hashed, scoped, and can be removed from the app.
EXAMPLE ASKS
“What calls came in for my shop today?”
“Read my last note about the plumber.”
“Propose a call to Emeka at 4 PM to confirm the delivery.”
“Which leads are still waiting?”
What the assistant can use
| Tool | What it does | Access |
|---|---|---|
| search_businesses | Find a business by name, category, or city | PUBLIC |
| get_business_catalog | Read products, prices, and stock | PUBLIC |
| ask_business_workflow | Ask a business a question through its line | PUBLIC |
| vii_notes_list | Read your private notes | PERSONAL |
| vii_reminders_create | Create a reminder after confirmation | PERSONAL |
| vii_propose_outreach | Propose a call or text with a read-back | PERSONAL |
| vii_get_outreach_status | Read the outcome and transcript of an outreach | PERSONAL |
| merchant_upsert_product | Add or update a product | MERCHANT |
| merchant_list_inbox | List live leads and cases | MERCHANT |
The assistant is not the boss.
VoiceReach keeps the exact same guardrails on MCP as on the phone line.
- Scoped keys. A key can read, write notes, propose outreach, or manage the store—not all four by default.
- Confirmation for outreach. A proposed call is a draft. The confirmation step is separate and single-use.
- No destructive shortcuts. Product deletion is not exposed. Data changes are explicit.
- Useful errors. When something is blocked, the tool says why and what to do next.
CONNECT YOUR ASSISTANT
Endpoint & keys
Add the MCP endpoint to your assistant. For private tools, sign in and approve the scopes once, or generate a developer key from Profile.
https://api.voicereach.app/mcp
Developer keys start with vr_mcp_ and are shown once. Public shop tools need no key.
Connect your assistant.
Generate a key in the app and point your AI tool at the MCP endpoint.