First, add the AdLabs MCP server configuration to your OpenClaw config. You can do this using the CLI command or by editing your config file directly.
Add the following to your OpenClaw MCP server configuration:
{
"mcp": {
"servers": {
"adlabs": {
"url": "https://mcp.adlabs.app/",
"transport": "streamable-http"
}
}
}
}You can use openclaw mcp set or edit the config file directly. After adding the server, restart OpenClaw.
mcporter is a CLI tool that handles the OAuth authentication flow for MCP servers. Install it globally using npm:
npm install -g mcporterAdd the AdLabs server to mcporter's config:
mcporter config add adlabs '{"url":"https://mcp.adlabs.app/mcp","transport":"streamable-http"}'Start the OAuth authentication flow by running:
mcporter auth adlabsThis will open a browser window where you can sign in with your AdLabs credentials. Click "Allow" to authorize access. If the browser does not open automatically, the authorization URL will be displayed in your terminal for you to copy and paste.
After authorization, retrieve the stored token by running:
mcporter config get adlabsCopy the access_token value from the output. You will need this in the next step.
Update your AdLabs MCP server configuration to include the Authorization header with the token you just retrieved:
{
"mcp": {
"servers": {
"adlabs": {
"url": "https://mcp.adlabs.app/mcp",
"transport": "streamable-http",
"headers": {
"Authorization": "Bearer PASTE_ACCESS_TOKEN_HERE"
}
}
}
}
}Replace PASTE_ACCESS_TOKEN_HERE with the actual token from Step 5. Then restart OpenClaw.
Confirm the MCP server is connected and working by running:
openclaw mcp listYou should see the AdLabs server listed. To test it out, try asking your OpenClaw agent to fetch your teams or run a simple query against your AdLabs data.
Token expiration: The access token expires after approximately 1 hour. When it expires, repeat Steps 4 through 6 to generate a new token.
Client registration: mcporter handles the OAuth client registration automatically, so you do not need to configure any client IDs or secrets manually.
Browser not opening? If the browser does not open during Step 4, check the terminal output for the authorization URL and open it manually.