Skip to main content

Other Clients

Enable any MCP-compatible client 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:

Setup​

MCP is an open protocol supported by many clients. Your specific client documentation can advise you how to connect to a stdio-based MCP server. The Signadot MCP server runs the command signadot mcp, and most clients let you register it by specifying the command and arguments to run.

Generic configuration​

For most MCP clients, the configuration will look similar to this:

"signadot": {
  "command": "signadot",
  "args": ["mcp"]
}

The exact structure and location of the configuration file depends on your specific client. Consult your client's MCP documentation for details on:

  • Where to place the MCP configuration file
  • What format to use (JSON, YAML, etc.)
  • Any additional client-specific settings

Common MCP clients​

Some popular MCP-compatible clients include:

  • Zed: A high-performance code editor with MCP support
  • Windsurf: AI-powered IDE with MCP support

Check your client's official documentation for specific setup instructions.

See also​