4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Ably MCP Server

Bring Pub Sub
to CrewAI

Learn how to connect Ably to CrewAI and start using 14 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Batch PresenceBatch PublishBatch Push PublishGet Channel MetadataGet MessageGet MessagesGet PresenceGet Presence HistoryGet StatsList ChannelsPublish MessagePush PublishRevoke TokensUpdate Message

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Ably

What is the Ably MCP Server?

Connect your Ably account to any AI agent to orchestrate real-time communication infrastructure through natural language. This server provides full access to the Ably REST API for robust pub/sub messaging and presence management.

What you can do

  • Messaging — Publish messages to single or multiple channels, retrieve message history, and update or delete existing messages.
  • Presence Tracking — Monitor real-time member status and history within specific channels to see who is online.
  • Push Notifications — Send direct push notifications to devices or client IDs for mobile and web engagement.
  • Channel Management — List active channels, fetch metadata, and monitor usage statistics across your application.
  • Security & Tokens — Revoke tokens before expiry to maintain tight control over your real-time infrastructure access.

How it works

  1. Subscribe to this server
  2. Enter your Ably API Key
  3. Start managing your real-time streams from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Backend Developers — Debug real-time message flows and check channel states directly from the terminal or IDE.
  • DevOps Engineers — Monitor application stats and manage API key security without leaving the command line.
  • Product Engineers — Test push notification payloads and presence logic during feature development.

Built-in capabilities (14)

batch_presence

Get presence for multiple channels

batch_publish

Publish messages to multiple channels at once

batch_push_publish

Publish batch push notifications

get_channel_metadata

Get metadata for a specific channel

get_message

Get a specific message by serial

get_messages

Retrieve message history for a channel

get_presence

Get current presence members for a channel

get_presence_history

Get presence history for a channel

get_stats

Retrieve application usage statistics

list_channels

Enumerate all active channels

publish_message

Publish a message to a specific channel

push_publish

Publish a direct push notification

revoke_tokens

Requires revocableTokens: true on the API key. Revoke Ably tokens before their expiry

update_message

Update, delete, or append to a message

Why CrewAI?

When paired with CrewAI, Ably becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Ably tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

Ably in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Ably and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Ably to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Ably in CrewAI

The Ably MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 14 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Ably
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Ably for CrewAI

Every tool call from CrewAI to the Ably MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I see who is currently active in a specific channel?

Yes. Use the get_presence tool with the target Channel ID to retrieve a list of all members currently connected and their status.

02

How do I send a single message to multiple channels at once?

You can use the batch_publish tool. Provide a comma-separated list of channel IDs and the data payload to broadcast to all of them in one request.

03

Is it possible to retrieve the history of messages sent to a channel?

Absolutely. Use the get_messages tool to fetch the message history for any channel, with options to filter by timestamp or limit the number of results.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →