Skip to content

MCP Clients Integration

Moira works with any client that supports the Model Context Protocol (MCP). This guide covers setup for 11 popular MCP clients.

Moira exposes tools via MCP over HTTP/SSE:

  • Endpoint: https://moira.witqq.ru/mcp
  • Transport: HTTP with SSE for streaming
  • Authentication: OAuth 2.0 or API Token

Recommended: Use CLI command

Terminal
claude mcp add --transport http moira https://moira.witqq.ru/mcp

Then authenticate:

OAuth Flow
# After adding, authenticate within claude
/mcp
# → Select "moira"
# → Click "Authenticate"
# → Browser opens for OAuth
Alternative: Manual JSON config
# Alternative: Manual JSON config
# ~/.config/claude/mcp.json
{
  "mcpServers": {
    "moira": {
      "type": "http",
      "url": "https://moira.witqq.ru/mcp"
    }
  }
}

# Then: /mcp → Authenticate
Authentication without OAuth

For CI/CD, Docker, or environments without a browser — use an API token instead of OAuth.

1. Log in to Moira web UI → Settings → API Tokens
2. Create a token (starts with moira_)
3. Replace moira_YOUR_TOKEN below with your token
~/.config/claude/mcp.json
{
  "mcpServers": {
    "moira": {
      "url": "https://moira.witqq.ru/mcp",
      "headers": {
        "Authorization": "Bearer moira_YOUR_TOKEN"
      }
    }
  }
}

For custom MCP client implementations, use the MCP SDK with URL: https://moira.witqq.ru/mcp

All MCP clients have access to these tools:

ToolParametersDescription
list_workflows-List available workflows
start_workflowworkflowIdStart workflow execution
execute_stepprocessId, inputSubmit step result
ToolParametersDescription
get_session_infoactionGet session/execution info
get_execution_contextexecutionIdGet execution context
ToolParametersDescription
get_helptopic (optional)Get documentation
manage_settingsaction, key, valueManage settings

Moira supports two authentication methods:

  1. Client initiates connection to MCP endpoint 2. Server returns authentication required response
  2. Client opens browser for OAuth flow 4. User authenticates with Moira 5. Client receives access token 6. Subsequent requests include token

For MCP clients that do not support OAuth (custom scripts, CI/CD pipelines, headless environments), use API tokens:

  1. Log in to Moira web UI 2. Go to Settings → API Tokens 3. Click Create Token, enter a name and expiration 4. Copy the token (shown once, starts with moira_) 5. Configure your client with the token as Bearer authorization

Example configuration for a custom MCP client:

{
"mcpServers": {
"moira": {
"url": "YOUR_MCP_ENDPOINT",
"headers": {
"Authorization": "Bearer moira_your_token_here"
}
}
}
}
{
"method": "tools/call",
"params": {
"name": "list_workflows",
"arguments": {}
}
}
{
"method": "tools/call",
"params": {
"name": "start_workflow",
"arguments": {
"workflowId": "development-flow"
}
}
}
{
"method": "tools/call",
"params": {
"name": "execute_step",
"arguments": {
"processId": "abc-123",
"input": {
"result": "Task completed successfully",
"details": { "files": ["main.ts", "utils.ts"] }
}
}
}
}

Common error responses:

ErrorCauseSolution
UNAUTHORIZEDInvalid/expired tokenRe-authenticate
NOT_FOUNDInvalid workflow/process IDVerify IDs
FORBIDDENNo access to resourceCheck permissions
VALIDATION_ERRORInvalid inputCheck input schema

For self-hosted Moira:

  1. Deploy Moira server
  2. Configure MCP endpoint URL
  3. Set up authentication (optional)
  4. Update client configuration with your endpoint
  • Check network connectivity
  • Verify endpoint URL
  • Ensure SSE is not blocked by firewall
  • Restart client after configuration
  • Verify JSON syntax in config
  • Check client logs for errors
  • Clear stored tokens
  • Check OAuth configuration
  • Verify redirect URIs