AiSensy MCP by usefulapi

MCP server · hosted · v1.0.0 · io.usefulapi/aisensy

Online · tested 57m agoNEW · 2h agoSeen in the registry 1h ago

Read AiSensy contacts, templates and campaigns; add contacts, send WhatsApp messages on approval.

What it does

AiSensy MCP by usefulapi is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES

Local installNO

Live checkOnline · 16 tools

Version1.0.0

PriceNot in the registry

First seen24 Oct 2026

Last checked1h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 57m ago (live check)

Hosted endpoint

https://aisensy.usefulapi.io/mcp streamable-http

In Claude Code: claude mcp add --transport http aisensy-mcp-by-usefulapi https://aisensy.usefulapi.io/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "aisensy-mcp-by-usefulapi": {
      "url": "https://aisensy.usefulapi.io/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 57m ago

ONLINE AiSensy MCP by usefulapi answered an MCP connection on 24 Oct 2026 and introduced itself as aisensy-mcp 1.0.0 (MCP protocol 2025-06-18).

16 tools offered to AI assistants

aisensy_get_project · The AiSensy project (WhatsApp account) this key belongs to: name, status, plan and renewal date, monthly active user quota and usage, credit balance (raw units as AiSensy reports them), WhatsApp number, display name status, quality rating a
aisensy_list_templates · List the WhatsApp template messages of the project with name, language, status (PENDING, APPROVED, REJECTED), category, text and parameter count. Only APPROVED templates can be sent. Pages by record id: pass next_after from the previous rep
aisensy_get_template · One WhatsApp template by id, with status, rejection reason, buttons and text. GET /project/{project_id}/wa_template/{id}.
aisensy_list_campaigns · List campaigns (API campaigns, broadcasts or both) with name, type, status, audience size, submitted count, template and creation time. Pages with skip + limit. POST /project/{project_id}/campaigns (a read: it only queries).
aisensy_list_api_campaigns · List the project's API campaigns (the campaigns messages can be sent through) with status and template. A campaign must be LIVE to send. GET /project/{project_id}/campaign/api.
aisensy_get_api_campaign · One API campaign by id: status, template, parameters and counts. GET /project/{project_id}/campaign/api/{campaign_id}.
aisensy_get_campaign_analytics · Daily delivery and credit-usage statistics of one campaign (sent, delivered, read, failed counts and message credit usage), optionally within a date range. POST /project/{project_id}/campaign/analytics/{campaign_id} (a read: it only queries
aisensy_list_campaign_audience · Who a campaign was sent to, with name, number and sent/delivered/read times, optionally filtered by outcome (SENT, DELIVERED, READ, FAILED, REPLIED, CLICKED) and date range. Pages by cursor: pass next_after from the previous reply as `after
aisensy_create_api_campaign · WRITE: create an API campaign that binds a name to an APPROVED WhatsApp template. It sends nothing; messages go out only when aisensy_send_campaign_message is called for it. Not idempotent: calling twice with the same name may create two ca
aisensy_find_contact · Look up a contact by phone number: id, name, tags, attributes, opt-in/chat state and last activity. 404 means no such contact. GET /project/{project_id}/contact?action=FetchContact&mobile_number=.
aisensy_get_contact · One contact by id: name, phone number, tags, attributes, chat state and last activity. GET /project/{project_id}/contact/{contact_id}.
aisensy_create_contact · WRITE: add a contact (name and phone number with country code). AiSensy opts new contacts in to WhatsApp notifications automatically, so only add people who agreed to be messaged. A number that already exists returns a 409 conflict. POST /p

Show 4 more

aisensy_update_contact · WRITE: change a contact's name, custom attributes, WhatsApp opt-in status or blocked status. Setting opted_in=false stops campaign messages to that person; blocked=true blocks them. Only the fields you pass change. PATCH /project/{project_i
aisensy_get_message · One WhatsApp message by id: status (SENT, DELIVERED, READ), sent/delivered/read times, sender, campaign, content and price. GET /project/{project_id}/messages/{message_id}.
aisensy_send_campaign_message · WRITE, SENDS A WHATSAPP MESSAGE TO A CUSTOMER AND SPENDS AISENSY CREDIT: send the template of a LIVE API campaign to one phone number (a new contact is created if the number is unknown). Not idempotent: every call sends again. template_para
aisensy_send_message · WRITE, SENDS A WHATSAPP MESSAGE TO A CUSTOMER AND MAY SPEND AISENSY CREDIT: send either a free-text message (type=text; WhatsApp only delivers it inside the 24-hour window after the customer last wrote) or an approved template (type=templat

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.

Fact	Value	Evidence	Source	Last confirmed
Hosted endpoint	https://aisensy.usefulapi.io/mcp	DECLARED	SRC-001 Official MCP Registry	1h ago
Local install (package)	no	DECLARED	SRC-001 Official MCP Registry	1h ago
Remote access (hosted)	yes	DECLARED	SRC-001 Official MCP Registry	1h ago
Website	https://usefulapi.io/aisensy/	DECLARED	SRC-001 Official MCP Registry	1h ago
Repository	https://github.com/m190/usefulapi-mcp	DECLARED	SRC-001 Official MCP Registry	1h ago
Registry status	active	DECLARED	SRC-001 Official MCP Registry	1h ago
Version	1.0.0	DECLARED	SRC-001 Official MCP Registry	1h ago
MCP server	yes	DECLARED	SRC-001 Official MCP Registry	1h ago

Change history

NEW24 Oct 2026
first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Is AiSensy MCP by usefulapi still online?

Free alerts · no account

Questions about AiSensy MCP by usefulapi

How do I connect AiSensy MCP by usefulapi?

Use the hosted endpoint https://aisensy.usefulapi.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does AiSensy MCP by usefulapi offer?

When Electra Index connected on 24 Oct 2026, it listed 16 tools: aisensy_get_project, aisensy_list_templates, aisensy_get_template, aisensy_list_campaigns, aisensy_list_api_campaigns, aisensy_get_api_campaign, aisensy_get_campaign_analytics, aisensy_list_campaign_audience and more. The full list is in "Live check" above.

Is AiSensy MCP by usefulapi online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 57m ago.