Skip to content
MCP-Bridge
ProductivityAuto-generatedScore: 34

Control API v1 MCP Server

The Control API v1, provided by Ably, is a comprehensive programmatic interface designed for the administrative management and automation of Ably’s real-time messaging infrastructure.

Quick Start Summary

The Control API v1 MCP server is a Model Context Protocol bridge that connects AI assistants — including Claude Desktop, Cursor, Windsurf, and VS Code Copilot — to the Control API v1 API through natural language. It exposes 10 API endpoints as callable tools, such as Lists apps, Creates an app, Lists app keys, and more. No authentication is required — setup takes approximately 30 seconds. The server uses STDIO transport and can be installed by running npx -y @mcp/ably-net-control. This integration is sourced from the auto Control API v1 OpenAPI specification (v1.0.14) and has a quality score of 34/99 (fair documentation coverage).

10Endpointstools mapped
NoneAuthopen access
34/99Qualityfair
~30 secSetupno auth
View Hosted Config URLClaude Desktop Setup Guide

Server Details

Category
Productivity
Authentication
None
Endpoints
10 operations
Transport
STDIO
Spec Version
v1.0.14
Install Command
npx -y @mcp/ably-net-control

Environment Variables

CONTROL_API_V1_API_KEY

Example: your_control_api_v1_api_key

Top Endpoints

GET
/accounts/{account_id}/apps

Lists apps

POST
/accounts/{account_id}/apps

Creates an app

GET
/apps/{app_id}/keys

Lists app keys

POST
/apps/{app_id}/keys

Creates a key

PATCH
/apps/{app_id}/keys/{key_id}

Updates a key

Own this API?

Verify ownership of this listing to control the description, configuration details, and documentation links. Choose between free manual verification or instant premium placement.

Option 1: Free Verification

Slow manual review. Requires creating a GitHub issue with verified documentation or domain verification.

  • • Verified badge on page
  • • Standard search sorting
  • • 2-3 business days review
Start Free Claim →
Instant & Boosted

Option 2: Featured Upgrade($9/mo)

Instant verification plus premium styling, featured badges, and directory placement boost.

  • • ★ Featured star & amber highlight border
  • • Top of directory search placement
  • • Instant activation via claim token

📖 Detailed MCP Integration Guide

A technical breakdown of capabilities, agent workflows, and security/configuration best practices.

⚡Capabilities & Use Cases
The Control API v1, provided by Ably, is a comprehensive programmatic interface designed for the administrative management and automation of Ably’s real-time messaging infrastructure. It serves as the central nervous system for controlling core resources within an Ably account, enabling developers and platform engineers to dynamically provision and configure applications, manage authentication credentials (keys), organize message flow with namespaces, and establish operational rules. Its primary function is to transition infrastructure management from manual, dashboard-driven tasks to scalable, code-first operations. This makes it indispensable for enterprise use cases such as automated environment provisioning for development and testing, multi-tenant SaaS platforms requiring isolated customer channels, and large-scale IoT deployments where device groups (represented by namespaces) or security credentials (keys) must be managed programmatically in response to dynamic demand. The API currently operates in a Beta state, indicating it is feature-rich but subject to refinement based on developer feedback.
🤖AI Agent Value
When integrated as tools for an AI coding assistant via the Model Context Protocol (MCP), the Control API unlocks a powerful paradigm of infrastructure-as-conversation, dramatically accelerating development workflows and reducing context-switching. An AI agent, armed with these tools, becomes a co-pilot capable of directly querying and modifying your Ably topology based on natural language instructions. This transforms abstract architectural decisions into immediate, executable actions. For instance, a developer can instruct the AI to "list all applications in our account and generate a new API key scoped to the 'production' namespace for the payments service," bypassing manual dashboard navigation and potential configuration errors. The value lies in the AI's ability to understand context, chain operations (e.g., "find the app ID for 'user-service', then list its keys, and finally create a new key with read-only permissions"), and act as a contextual expert, thereby compressing development cycles and enhancing operational accuracy.
💬Example Workflows
Practical workflows enabled by this MCP server are numerous and directly impactful. An AI agent can perform dynamic resource auditing by querying all keys and their permissions to generate a security report, stating, "AI agent can query all keys to audit privilege distribution across namespaces." It can automate environment cleanup by instructing, "AI agent can delete all test namespaces older than 30 days to reduce clutter and costs." In a CI/CD pipeline context, a developer could prompt, "AI agent can create a temporary, restricted key for a staging environment and then revoke it after tests complete," ensuring ephemeral credentials and enforcing security hygiene. For multi-tenant management, the AI can handle customer onboarding by executing, "AI agent can create a new namespace for a new tenant, generate a scoped key, and provide the configuration details back to the provisioning system."
🛡️Security & Auth
Critical to the deployment of this API is the absence of a built-in authentication method, which mandates that developers implement and enforce robust security controls externally. Authentication and authorization must be rigorously applied, ideally using Ably API keys with the smallest possible set of privileges required for the specific task, adhering strictly to the principle of least privilege. For an MCP server integration, this means the server should be configured with a high-privilege key only in a secure, isolated backend environment, while exposing a minimal set of safe, well-vetted tools to the AI. Additional security best practices include using short-lived tokens where possible, enforcing IP allowlists on API keys, and meticulously logging all API actions for audit trails. Developers must treat the Control API as a powerful and sensitive management plane, where a misconfigured tool or overly broad permission could lead to significant operational or security incidents.

Similar APIs

Other APIs in the Productivity category.

Notion API

Create and manage Notion pages, databases, and blocks through your AI agent.

OAuth2

Linear API

Manage issues, projects, and workflows in Linear through your AI agent.

API Key

Platform API

The Platform API is a comprehensive RESTful interface provided by Ably, a leading provider of real-time messaging and presence infrastructure, designed to give developers granular, programmatic control over their Ably applications and resources. Its core capabilities extend beyond simple pub/sub messaging, enabling the management and inspection of channels, the retrieval and publishing of messages, the manipulation of presence state for users across those channels, and the configuration of push notification subscriptions. Typical use cases span enterprise and consumer applications where real-time functionality is critical, such as live activity feeds for e-commerce platforms, collaborative tools requiring synchronized state, multi-user gaming, real-time chat, and IoT device status monitoring. This API serves as the foundational control plane for any application built on the Ably ecosystem, allowing for dynamic, server-side orchestration of real-time behaviors.

Adyen Test Cards API

The Adyen Test Cards API, provided by the global payment platform Adyen, is a specialized utility designed to streamline the payment integration development and testing lifecycle. Its core capability is the programmatic generation of custom test card numbers, a critical requirement for developers and QA engineers building and validating payment flows in sandbox or test environments. By exposing a dedicated endpoint, `POST /createTestCardRanges`, the API eliminates the manual process of sourcing static test card numbers from documentation or community lists. This is particularly valuable for enterprise-scale applications where testing must cover a complex matrix of scenarios, including various card schemes (Visa, Mastercard, etc.), card types (credit, debit, prepaid), issuer countries, and specific transaction outcomes like approvals, declines, and 3D Secure challenges. Typical use cases span from automated continuous integration (CI) pipelines that require unique test data for each run, to teams developing payment interfaces that must simulate a wide array of real-world customer payment methods.

Related MCP Server Integrations

Notion API MCP Setup

Create and manage Notion pages, databases, and blocks through your AI agent.

ProductivityConfigure →

Linear API MCP Setup

Manage issues, projects, and workflows in Linear through your AI agent.

ProductivityConfigure →

Platform API MCP Setup

The Platform API is a comprehensive RESTful interface provided by Ably, a leading provider of real-time messaging and presence infrastructure, designed to give developers granular, programmatic control over their Ably applications and resources. Its core capabilities extend beyond simple pub/sub messaging, enabling the management and inspection of channels, the retrieval and publishing of messages, the manipulation of presence state for users across those channels, and the configuration of push notification subscriptions. Typical use cases span enterprise and consumer applications where real-time functionality is critical, such as live activity feeds for e-commerce platforms, collaborative tools requiring synchronized state, multi-user gaming, real-time chat, and IoT device status monitoring. This API serves as the foundational control plane for any application built on the Ably ecosystem, allowing for dynamic, server-side orchestration of real-time behaviors.

ProductivityConfigure →

Adyen Test Cards API MCP Setup

The Adyen Test Cards API, provided by the global payment platform Adyen, is a specialized utility designed to streamline the payment integration development and testing lifecycle. Its core capability is the programmatic generation of custom test card numbers, a critical requirement for developers and QA engineers building and validating payment flows in sandbox or test environments. By exposing a dedicated endpoint, `POST /createTestCardRanges`, the API eliminates the manual process of sourcing static test card numbers from documentation or community lists. This is particularly valuable for enterprise-scale applications where testing must cover a complex matrix of scenarios, including various card schemes (Visa, Mastercard, etc.), card types (credit, debit, prepaid), issuer countries, and specific transaction outcomes like approvals, declines, and 3D Secure challenges. Typical use cases span from automated continuous integration (CI) pipelines that require unique test data for each run, to teams developing payment interfaces that must simulate a wide array of real-world customer payment methods.

ProductivityConfigure →

Amazon Lex Runtime V2 MCP Setup

Amazon Lex Runtime V2 is a sophisticated conversational AI service provided by Amazon Web Services that enables developers to manage and interact with chatbot sessions in real time. This API serves as the runtime interface for Amazon Lex bots, allowing applications to communicate with bots that have already been built and published. The service is designed to handle natural language understanding and dialogue management at scale, supporting multiple languages and locales within a single bot configuration. Typical enterprise use cases include deploying intelligent virtual agents for customer service portals, automating FAQ responses in e-commerce platforms, integrating voice and text-based conversational interfaces into enterprise applications, and powering interactive voice response systems for contact centers. Consumer-facing applications often leverage Lex V2 for personal assistant functionality, appointment scheduling bots, and interactive troubleshooting guides. The Runtime V2 API is distinct from the Build-time API, as it focuses exclusively on session-based interactions rather than bot creation or training, making it the critical endpoint for any production deployment that requires real-time user engagement.

ProductivityConfigure →