Aloware MCP

Use this reference to set up Aloware's MCP server, pick how your client signs in, and see what it can do and what it costs.

Overview

The Model Context Protocol (MCP) lets an AI assistant work inside your Aloware account. You describe what you want in plain language and the assistant performs the action for real, with no tool switching and no hand-written API calls.

From your AI client you can text, call, create leads, enroll contacts in sequences or manage power dialer lists, and Aloware carries out each request immediately.

Example: ask "Send an SMS to +18185551234 confirming the appointment tomorrow at 2pm" and Aloware sends it right away. Credits are charged exactly as for an action done by hand or through the API.

Finding the MCP page

Open Integrations → MCP in Aloware. It has the server URL, the configuration to copy into your client, and the list of every tool.

How your client signs in

OAuth 2.1 (recommended)

Give your client the server URL. It handles sign-in and authorization itself, so there's no token to copy or manage. Marketplace integrations, such as the Claude Connectors Directory and the ChatGPT Apps directory, use it too: the user grants access on a standard consent screen, and each connection carries its own user identity, rate limiting and audit trail.

Bearer token (being deprecated)

Bearer tokens are being retired: they aren't secure enough and don't meet compliance requirements. A client that still signs in with one sends your account API token in the Authorization header, and it reaches only 14 of the 166 tools. Move it to OAuth: give it the server URL and sign in.

Server

One endpoint gives your client every tool, across communication, contacts and operations:

https://app.aloware.io/mcp

Client configuration

If your client supports OAuth, paste the server URL. For a client set up with a JSON file, add this to its MCP config:

{
    "mcpServers": {
        "aloware": {
            "url": "https://app.aloware.io/mcp"
        }
    }
}

Architecture

Your AI client talks to Aloware through streaming servers. MCP doesn't follow the usual API pattern of one request and one response: it keeps a persistent HTTP Streaming (SSE) connection open, so the client can run actions live while you chat.

An MCP action is treated like the same action in the Aloware UI or API for billing, rate limits and logging.

What the tools do

The server has 166 tools. Show tools on the MCP page lists them all; the tables below cover the main ones, grouped by what they do.

Communication tools

These tools cover outreach to contacts: outbound SMS, ringless voicemails and phone calls.

For example, asking the assistant to send a confirmation, call a lead or drop a voicemail runs through these tools.

Everything here is a live operation billed by usage. No simulation or test mode exists.

Request rules

Format every phone number in E.164 format (e.g. +18185551234). Each request also needs a from phone number or a line_id so Aloware knows which line to send from.

When the recipient's number isn't in the account yet, Aloware creates the contact first and then sends the communication.

Example prompts

1. Appointment confirmation
   "Text John Smith confirming his demo tomorrow at 3pm."
   An SMS goes out from the assigned Aloware line.
2. Follow-up voicemail
   "Leave a voicemail for everyone who didn't answer today's outbound list."
   RVMs are sent to those contacts.
3. Warm transfer
   "Call the contact at +18185551234 and bridge them to the sales ring group."
   A two-legged call connects the contact with an available agent.
4. AI-driven outreach
   "Have the AloAi sales bot call the new leads from this morning."
   AloAi places outbound calls to those contacts.

Logging and cost

The contact timeline records every action with Creator Type: MCP, which keeps MCP activity apart from manual and API activity. These are real operations that use credits; there's no sandbox or dry-run mode.

Contact tools

These tools let the assistant create, edit and manage Aloware contact records, and attach them to sequences, tags and power dialer lists.

Request rules

Identify the contact by at least one of: phone number, Aloware contact ID, or CRM ID (HubSpot, Zoho, Guesty, or Pipedrive). Phone numbers must be in E.164 format.

Example prompts

1. Lead capture from a conversation
   "Create a lead for Jane Smith, phone +18185551234, email jane@example.com, tag her as 'Event Signup', assign her to Mark, and add her to the Q2 Outreach sequence."
   A single request does every part.
2. Contact enrichment
   "Look up the contact at +18185551234."
   You get the whole contact record back, with its tags, notes and custom fields.
3. CRM-driven enrollment
   "Enroll HubSpot contact 12345 into the Renewal sequence."
   The HubSpot ID is matched to its Aloware contact, which is then enrolled.
4. Pre-call validation
   "Run an LRN lookup on this list of numbers."
   Before any SMS goes out, you learn which numbers are mobile, landline or VoIP.
5. Sequence cleanup
   "Remove +18185551234 from all active workflows."
   The contact is disenrolled straight away.

Logging and cost

Contacts that MCP creates get the intake source mcp. Nearly every contact tool is free; Number Lookup (LRN) is the only operation that uses credits.

Operations tools

These tools show the assistant your users, agent status and power dialer lists. It helps with decisions like routing and list cleanup, and never contacts anyone itself.

Example prompts

1. Smart routing check
   "Who is available on the Support inbox right now?"
   Live agent availability comes back before a supervisor hands out a call.
2. Routing diagnostic
   "Why isn't Maria receiving calls in the Sales inbox?"
   An Inbox Availability check returns the routing reasons, such as outside operating hours or at concurrency limit.
3. Power dialer cleanup
   "Clear the 'April Outreach' Power Dialer list."
   The list is emptied and its configuration stays as it was.
4. Agent reset
   "Clear all Power Dialer lists assigned to John."
   Every list for that user is removed in a single action.
5. Remove a single contact
   "Take +18185551234 out of all Power Dialer lists."
   The contact comes off every list that contains it.

Logging and cost

These tools cost nothing to use. Power dialer requests run asynchronously: Aloware confirms as soon as it accepts the request.

Billing

An operation that uses credits through MCP is one that uses credits in the UI or API too.

Everything that isn't communication (creating contacts, enrolling in sequences, managing power dialer, checking availability) is free.

Important: an AI assistant can run paid operations on its own from your prompts, and there's no sandbox mode. That's why the MCP Integrations page shows a billing warning before anyone connects.

Auditing MCP activity

Messages and calls made through MCP carry Creator Type: MCP. They sit in the contact timeline with everything else, and you can filter and report on them apart from manual, API or workflow communications.

Contacts MCP creates show mcp in their intake source field.

Compatible clients

Because MCP is an open standard, any client that implements it can use Aloware's MCP server.

Claude Desktop (Anthropic) and Cursor are the most common, both with full MCP support, and Windsurf works too. Claude AI (web) and ChatGPT connect with their OAuth 2.1 marketplace connectors, and other clients that follow the MCP specification can connect as well.

If your client supports OAuth, give it the server URL. For clients set up with a JSON file, the MCP page in Aloware gives you the configuration to copy.