Connect an AI Client to WorkBoard MCP
There are two ways to authenticate the WorkBoard MCP connection. Choose the one that fits your setup:
Option 1: OAuth2
Claude Desktop
Step 1: Get your OAuth credentials
Go to WorkBoard → Profile → Settings → Custom Integrations → App tab. Create an app to get your client_id and client_secret.
Set the App Redirect URI to exactly: https://claude.ai/api/mcp/auth_callback
Note: A mismatch between the redirect URI registered in WorkBoard and the one Claude Desktop uses is the most common setup failure. Copy it exactly.
Step 2: Open the Connectors panel in Claude Desktop
In Claude Desktop, go to Settings → Connectors and click Add custom connector.
Note: On managed or org-level Claude accounts, the Connectors UI may be restricted to admins.
Step 3: Enter the connection details
Fill in the fields as follows:
MCP Server URL: https://www.myworkboard.com/wb/mcp
Client ID: paste the client_id from Step 1
Client Secret: paste the client hash from Step 1
Step 4: Authenticate and save
Click Connect. Claude Desktop will open a WorkBoard login page. Sign in with your WorkBoard credentials and approve the requested scopes. Once complete, the connector appears as active and WorkBoard tools become available in your Claude conversations.
OAuth2 for Workato and Custom Tools
Use these endpoints to build your own OAuth2 flow:
Purpose | URL |
Authorize | |
Token | |
User info | |
MCP server |
To call MCP with an access token:
POST https://www.myworkboard.com/wb/mcp
Authorization: Bearer <access_token>
Option 2: Personal Token
Step 1: Go to your profile menu
Click your profile photo in the top-right corner of WorkBoard. Select Settings from the dropdown.
Step 2: Generate your token
In the left sidebar, click Custom Integrations, then click the App tab. In the Instant Token section, click the link to generate your token.
Important: Your token is shown only once. Copy it immediately and store it somewhere safe (like a password manager). If you lose it, you can revoke and generate a new one from the same page.
Step 3: Add the token to your AI client
Choose your AI tool and paste in the configuration below. Replace YOUR_WB_TOKEN with the token you copied.
Claude Desktop
Go to Settings → Developer → Edit Config
This will open the config file:
Add the following to your config file:
{
"mcpServers": {
"workboard": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://www.myworkboard.com/wb/mcp",
"--header",
"Authorization: Bearer YOUR_WB_TOKEN"
]
}
}
}
3. Save the file and restart Claude Desktop.
Prerequisite: Claude Desktop requires Node.js 18 or higher. Run node --version in your terminal to check.
Cursor
Navigate to Cursor settings
Click on Tools and MCPs
Click on Add Custom MCP
Add the following:
{ "mcpServers": {
"workboard": {
"url": "https://www.myworkboard.com/wb/mcp",
"headers": {
"Authorisation": "Bearer YOUR_WB_TOKEN"
}
}
}
}
Replace with your token
Click Save
Other MCP-Compatible Clients
{
"mcpServers": {
"workboard": {
"type": "http",
"url": "https://www.myworkboard.com/wb/mcp",
"headers": { "Authorization": "Bearer YOUR_WB_TOKEN" }
}
}
}
Troubleshooting
Problem | Fix |
401 Unauthorized | Token expired or wrong environment. Regenerate your token (Option 2) or refresh via OAuth (Option 1). |
No tools listed | Your WorkBoard role may not have access to OKRs, Scorecards, or other features. Contact your WorkBoard admin. |
Claude Desktop won't connect | Make sure Node.js 18+ is installed. |
Redirect URL error (OAuth) | Make sure the redirect URI in WorkBoard (Step 1) matches exactly what the AI client uses. |
Security & Privacy
MCP access is scoped to each user's authorization - your token only exposes your own data.
Your token is scoped to MCP only and cannot be used for other WorkBoard APIs.
The MCP server never stores your access token - it verifies and discards it on each request.