Model Context Protocol (MCP)
Enable your AI agents to interact directly with Signadot by using our MCP server.
The Signadot Model Context Protocol (MCP) server exposes a set of tools that AI agents can use to work with your Signadot environment, managing sandboxes, route groups, and other related resources.
Prerequisites
Before connecting to the Signadot MCP server, make sure you have:
- Signadot account (sign up here)
- Signadot CLI v1.4.0+ (installation instructions)
Supported clients
Signadot's MCP server works with any MCP-compatible client. Select your client below for specific setup instructions:
📄️ Cursor
Connect Signadot to Cursor using the Model Context Protocol (MCP).
📄️ Claude Code
Connect Signadot to Claude Code using the Model Context Protocol (MCP).
📄️ VS Code
Connect Signadot to VS Code using the Model Context Protocol (MCP).
📄️ Other Clients
Connect Signadot to any MCP-compatible client using the Model Context Protocol (MCP).
Common use cases
With the Signadot MCP server connected, you can use natural language prompts to manage Signadot entities like sandboxes. Here are some examples:
"Create a sandbox with a local mapping for my frontend service running on port 3000"
Set up development sandboxes that connect to services running locally on your machine, enabling you to test changes in an isolated environment alongside your cluster services.
"Create a sandbox to test a new version of the api-service deployment using the docker image myorg/api:v2.1.0 and set the LOG_LEVEL env var to debug"
Spin up isolated environments to test new versions of your services with specific docker images and environment variables before deploying to production.
"Add the DEBUG_MODE=true environment variable to the api-service fork in my sandbox"
Apply specific modifications to individual forks within existing sandboxes, such as adding or updating environment variables, without recreating the entire environment.
"Update my sandbox to include a new fork of the payment-service using the image myorg/payment:v3.0.0"
Add new service forks to existing sandboxes, allowing you to test additional service versions without recreating the entire sandbox environment.
Tools
The server exposes a suite of tools for managing your Signadot environment. These tools provide operations for:
- Sandboxes: Create, list, retrieve, and update sandboxes.
- Route groups: Create, list, retrieve, and update route groups.
- Clusters: List available clusters.
- Workloads & Services: Discover in-cluster workloads and endpoints.
- Resource Plugins: List available resource plugins.
- Devboxes: List devboxes.
- Authentication: Check your authentication status.
- Help: Get information about core Signadot concepts.
These tools are designed to simplify the management of sandboxes and route groups.
Sandbox management
With sandboxes, you can:
| Action | Description |
|---|---|
| Add or update fork workloads | Use AI assistance to determine required fork changes, including workload resolution, patch definitions and environment variables |
| Add or update local mappings | Automatically discover in-cluster workloads and target ports, and link them to your connected devboxes |
| Add or update virtual workloads | Create and manage virtual workloads |
| Resolve preview endpoints | Easily resolve preview endpoints for your sandboxed workloads |
| Use resources | Define sandbox resources through resource plugins, automatically injecting the corresponding environment variables into sandboxed workloads |
| Monitor status | Check sandbox status and get access information |
Route group management
For route groups, you can:
| Action | Description |
|---|---|
| Manage sandbox labels | Automatically match sandbox labels to route groups. The AI can assist with label management to ensure the correct sandboxes are targeted |
| Modify existing route groups | Update route groups |
| Define preview endpoints | Configure preview endpoints for route groups |