These docs cover the S6S workflow engine — the developer playground layer underneath the product. For the main AI Visibility product (brand monitoring, the unified Report, fix actions), start at /docs/ai-visibility.
MCP Server
Give any MCP-compatible AI agent the ability to deploy, monitor, and manage workflows.
What is MCP?
The Model Context Protocol (MCP) is an open standard that lets AI agents use external tools. The S6S MCP server gives your agent workflow superpowers — deploy persistent multi-step automations, check run status, manage credentials, and more. All from natural language.
Works with Claude Desktop, Claude Code, Cursor, OpenClaw, and any MCP-compatible client.
Quick Start
Setup by Platform
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"s6s": {
"command": "npx",
"args": ["@s6s/mcp-server"],
"env": {
"S6S_API_KEY": "s6s_your_key_here",
"S6S_BASE_URL": "https://s6s.ai"
}
}
}
}Claude Code
Add to .claude/settings.json in your project or ~/.claude/settings.json globally:
{
"mcpServers": {
"s6s": {
"command": "npx",
"args": ["@s6s/mcp-server"],
"env": {
"S6S_API_KEY": "s6s_your_key_here",
"S6S_BASE_URL": "https://s6s.ai"
}
}
}
}Cursor
Add to .cursor/mcp.json in your project:
{
"mcpServers": {
"s6s": {
"command": "npx",
"args": ["@s6s/mcp-server"],
"env": {
"S6S_API_KEY": "s6s_your_key_here",
"S6S_BASE_URL": "https://s6s.ai"
}
}
}
}OpenClaw
Add as an MCP plugin in your OpenClaw configuration:
{
"mcpServers": {
"s6s": {
"command": "npx",
"args": ["@s6s/mcp-server"],
"env": {
"S6S_API_KEY": "s6s_your_key_here",
"S6S_BASE_URL": "https://s6s.ai"
}
}
}
}Environment Variables
| Variable | Required | Description |
|---|---|---|
| S6S_API_KEY | Yes | Your S6S API key (starts with s6s_) |
| S6S_BASE_URL | No | API base URL. Defaults to https://s6s.ai. Set this if you are self-hosting. |
Available Tools
The MCP server exposes 15 tools. Tools annotated as read-only will not prompt for confirmation in Claude Desktop. Tools annotated as destructive will always prompt.
| Tool | Description | Annotations |
|---|---|---|
| s6s_get_catalog | Discover all node types, triggers, expressions, and flow syntax | read-only |
| s6s_deploy_workflow | Deploy a workflow from a Recipe JSON — single call, auto-runs | — |
| s6s_validate_workflow | Pre-flight check: credentials, config, schedule, structure | read-only |
| s6s_run_workflow | Manually trigger a run for a deployed workflow | — |
| s6s_get_run_status | Check run progress and step-by-step results | read-only |
| s6s_get_workflow | Get a single workflow by ID, including its full definition | read-only |
| s6s_list_workflows | List all deployed workflows | read-only |
| s6s_list_runs | List recent runs with optional status filter | read-only |
| s6s_cancel_run | Cancel an active run | destructive |
| s6s_retry_run | Retry a failed or cancelled run | — |
| s6s_delete_workflow | Permanently delete a workflow | destructive |
| s6s_update_workflow | Update workflow name or enabled status | — |
| s6s_list_credentials | List connected service credentials (no secrets exposed) | read-only |
| s6s_list_integrations | List all platform integrations S6S can connect to | read-only |
| s6s_get_integration | Get full details for a specific integration | read-only |
Prompts
The server also exposes MCP prompts — guided workflows that help your agent accomplish common tasks.
| Prompt | Description | Arguments |
|---|---|---|
| create-workflow | Guided workflow creation — step-by-step help from catalog to deploy | description — what the workflow should do |
| debug-run | Systematic debugging of a failed or stuck run | run_id — the run ID to debug |
Resources
| URI | Description |
|---|---|
| s6s://catalog | Full workflow catalog (actions, triggers, expressions, flow patterns). Cached for 5 minutes. |
Example
Tell your AI agent:
The agent will:
- Call
s6s_get_catalogto learn available node types - Build a Recipe with a schedule trigger, HTTP fetch, transform, and Slack post
- Call
s6s_deploy_workflowto deploy and start it - S6S runs it persistently — survives restarts, retries on failure, fully observable
Self-Hosting
If you are running S6S on your own infrastructure, set S6S_BASE_URL to your instance URL in the MCP configuration:
"env": {
"S6S_API_KEY": "s6s_your_key_here",
"S6S_BASE_URL": "https://workflows.mycompany.com"
}See Self-Hosting for full deployment instructions.
Ready to connect your agent?
Create an API key and configure your MCP client in under a minute.