Connect an MCP host

Available now @automatalabs/workflows@0.43.0 includes the consolidated MCP command.

Register AgentPrism as a local stdio MCP server. Use the released consolidated command.

Copy the server entry

Add this entry to your host MCP configuration:

AgentPrism server entry · MCP host configuration

{
  "command": "npx",
  "args": ["-y", "@automatalabs/workflows", "mcp"]
}

Use the field names that your host requires. Do not change the command or its arguments.

For hosts that use an mcpServers map, use this full entry:

AgentPrism server map · MCP host configuration

{
  "mcpServers": {
    "agentprism": {
      "command": "npx",
      "args": ["-y", "@automatalabs/workflows", "mcp"]
    }
  }
}

The npx process downloads the current released package when the local npx cache does not contain it. The mcp subcommand starts the embedded MCP server with stdio transport.

Restart the host

Save the MCP configuration. Restart or reconnect the MCP host.

Open the host MCP status view. The result must show the AgentPrism server as connected.

Open the host tool list. The result must include one tool named workflow.

Hosts with MCP prompt support also show the author-workflow MCP prompt; hosts without prompt support do not.

Use the equivalent server package

The standalone MCP server remains an equivalent alternative:

Standalone MCP server · shell command

npx -y @automatalabs/mcp-server

The standalone package is optional for the first-use path. We have not deprecated it.

If the server does not connect

Run the consolidated help command in a shell:

Consolidated MCP help · shell command

npx -y @automatalabs/workflows mcp --help

The result must show Usage: agentprism-workflows mcp.

If the command works in a shell, read the MCP host process log. Keep stdout reserved for MCP JSON-RPC messages.

Next step

Obtain a workflow script with the published guide.