Blueticked vs Vexa

A side-by-side look at the Blueticked and Vexa MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

B
BluetickedCommunication · Remote HTTP/SSE
Send WhatsApp, SMS and email for South African businesses: contacts, campaigns, templates, webhooks42FairAuth: not declared
Vexa logoVexaCommunication · Remote HTTP/SSEMeeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.48FairAuth: not declared

Verdict: choose Blueticked for communication work over a hosted endpoint; choose Vexa for communication over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

B
Choose Blueticked when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a remote HTTP/SSE transport.
Explore Blueticked

Vexa logoChoose Vexa when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a remote HTTP/SSE transport.
  • You have the keys it needs: API_KEY, API_BASE, TRANSCRIBE_ENABLED, RUNTIME_BACKEND.
Explore Vexa

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
B
Blueticked
Vexa logoVexa
CategoryCommunicationCommunication
Quality signal42/100 · Fair48/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSERemote HTTP/SSE
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedAPI_KEYAPI_BASETRANSCRIBE_ENABLEDRUNTIME_BACKEND
Verified ownerCommunity listingCommunity listing
GitHub stars—2,906
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Blueticked tools

No tool names declared yet. Check the project README from the listing page.

Vexa tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Blueticked

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "blueticked": {
      "url": "https://blueticked.com/mcp"
    }
  }
}

Vexa

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vexa": {
      "url": "https://api.cloud.vexa.ai/bots"
    }
  }
}

Frequently asked questions

Blueticked is categorized under Communication and uses a remote HTTP/SSE transport. Vexa belongs to Communication and uses a remote HTTP/SSE transport. Pick Blueticked for communication work and Vexa for communication.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Blueticked has no declared pricing — check the project's own site. Vexa has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add blueticked and vexa as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Blueticked has a quality signal of 42/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Vexa has 48/100 (Fair) with 2 views, 0 installs and 2,906 GitHub stars.