How to Use the Relay Workflow Automation MCP in Claude Code

Q: How do I run Relay Workflow Automation using Claude Code?

Use the runworkflow tool via the command line. You provide the inputs, and the server handles the API call.

Q: Can Claude Code monitor Relay Workflow Automation status?

Yes. You can call listruns or getrunstatus to track your automations without ever leaving the terminal.

Q: Is it possible to cancel Relay Workflow Automation tasks in Claude Code?

Use the cancelrun tool. It provides a direct way to halt any in-progress execution from your command line.

Claude Code brings Relay automation to your terminal for headless workflow management and scripted incident response.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect Relay Workflow Automation MCP to Claude Code

Create your Vinkius account to connect Relay Workflow Automation to Claude Code — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Setup Relay Workflow Automation with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Headless Relay management

Run `list_workflows` directly from your terminal to see what is available. This is ideal for SREs who need to check status without opening a browser. Use `get_workflow` to verify configuration details on the fly. It keeps your terminal session focused and fast.

Scripted execution control

Trigger any job with `run_workflow` using standard JSON inputs. It fits perfectly into your shell scripts or CI/CD pipelines. Monitor active jobs with `get_run_status` or stop them immediately using `cancel_run`. It gives you total control over your infrastructure automation.

Automated audit logs

Pipe the output of `list_runs` into your log files for post-mortem analysis. It provides the data you need to trace execution history. This server turns your terminal into a command center for your Relay account. It makes managing automated tasks a simple text-based operation.

Setup guide

Set up Relay Workflow Automation MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see relay-workflow-automation-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Relay Workflow Automation transactions." It will automatically discover and invoke the available Relay Workflow Automation tools.

Terminal

claude mcp add --transport http relay-workflow-automation-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Relay Workflow Automation MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "relay-workflow-automation-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Relay. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.