MCP server overview

Expose Velip communications APIs as MCP tools for AI agents and IDE integrations.

The Velip MCP APIs server is a Model Context Protocol (MCP) server that wraps the Velip Public API v2. AI clients (Cursor, Claude Desktop, LangGraph agents, etc.) can call Velip without writing HTTP integration code — they discover and invoke tools such as send_sms, make_tts_call, or send_whatsapp.

Architecture

AI client (Cursor, Claude, custom agent)
        │  HTTPS + Bearer token
        ▼
https://vox20.velip.com.br/mcpserver/velip
        │  MCP Streamable HTTP (JSON-RPC)
        ▼
Velip MCP APIs server
  • validates token (cd_psid)
  • filters tools by permission (cdpsid_mcp_apis)
  • proxies to Velip PHP API
        ▼
https://vox.velip.com.br/api/v2/

When to use MCP vs REST

Use MCP when…	Use REST API v2 when…
Integrating with Cursor, Claude, or an MCP-native agent	Building a traditional backend or mobile app
You want the LLM to pick tools dynamically	You need full control over every HTTP call
Quick prototyping from an IDE	You need endpoints not yet exposed as MCP tools

Both interfaces use the same account token and enforce the same business rules (balance, validation, rate limits).

What is available

13 MCP tools covering SMS, outbound voice (TTS), WhatsApp, Gmail OAuth, campaigns, destinations, and call status. See the tools index.

Tools not listed in your tools/list response are hidden because your token lacks permission for that channel — not because they do not exist.

Transport

Protocol: MCP over Streamable HTTP (stateless JSON-RPC)
Auth: Authorization: Bearer <30-char-token> on every request
Health: GET /mcpserver/velip/health (no auth)

Next steps

Getting started — token, first tools/list, first send_sms
Authentication — how tokens work
Permissions — enable SMS, telephony, WhatsApp, Gmail per token
Connect Cursor or Claude Desktop

REST equivalent

Every MCP tool maps to one or more REST API v2 endpoints. Tool pages include cross-links to the PHP API reference.