Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@PacedLoop MCP Servershow me the status of my most recent workflow runs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
pacedloop-mcp-server
Standalone MCP server for the hosted PacedLoop API.
This package is for users who want PacedLoop tools inside an MCP-capable client without running the full PacedLoop app locally.
What users need
a PacedLoop account
a PacedLoop API token
Node.js 18+ installed locally
Hosted default:
https://www.pacedloop.comWhat it exposes
workflow CRUD
run list, detail, start, advance, and repair
analytics overview
step analytics
recent-run analytics
Quick start
Clone this repository.
Install dependencies:
npm installSet environment variables:
export PACEDLOOP_BASE_URL=https://www.pacedloop.com
export PACEDLOOP_API_TOKEN=your_pacedloop_tokenPowerShell:
$env:PACEDLOOP_BASE_URL="https://www.pacedloop.com"
$env:PACEDLOOP_API_TOKEN="your_pacedloop_token"Start the server:
npm startOpenClaw / NemoClaw setup
Use this process definition in your MCP client configuration:
Command:
npmArgs:
startWorking directory:
/path/to/pacedloop-mcp-serverEnvironment:
PACEDLOOP_BASE_URL=https://www.pacedloop.com
PACEDLOOP_API_TOKEN=your_pacedloop_tokenIf your MCP client supports launching a script directly, use:
Command:
nodeArgs:
/path/to/pacedloop-mcp-server/bin/pacedloop-mcp-server.mjsExample OpenClaw-style config
OpenClaw/NemoClaw config shapes can vary by version, but this is the command block you want to represent:
{
"command": "npm",
"args": ["start"],
"cwd": "/path/to/pacedloop-mcp-server",
"env": {
"PACEDLOOP_BASE_URL": "https://www.pacedloop.com",
"PACEDLOOP_API_TOKEN": "your_pacedloop_token"
}
}If your OpenClaw build expects direct script execution, use:
{
"command": "node",
"args": ["/path/to/pacedloop-mcp-server/bin/pacedloop-mcp-server.mjs"],
"env": {
"PACEDLOOP_BASE_URL": "https://www.pacedloop.com",
"PACEDLOOP_API_TOKEN": "your_pacedloop_token"
}
}Publish as its own GitHub repo
From the parent directory:
cd pacedloop-mcp-server
git init
git add .
git commit -m "Initial standalone PacedLoop MCP server"Then create a new GitHub repository and push:
git remote add origin git@github.com:YOUR_ORG_OR_USER/pacedloop-mcp-server.git
git branch -M main
git push -u origin mainNotes
The server uses stdio and MCP JSON-RPC framing.
The token is sent as a Bearer token to the PacedLoop API.
Keep the API token on the local machine running the MCP client.
This package is a thin adapter over the hosted PacedLoop backend, not a standalone workflow engine.
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.