MCP - How to set up MCP in Workpath – Workpath Help Center

Prerequisites

You need administrator access in Workpath.
A supported MCP-compatible application (e.g. Claude Desktop).

Claude Desktop

Step 1: Create MCP credentials in Workpath

Go to Organization Settings > Integrations > Connections.
Click the MCP entry.
Click Setup MCP.
Enter a name for your MCP application.
Click Submit.
Copy the URL, Client ID, and Client Secret - you'll need these in the next step.

Step 2: Connect your application

Using Claude Desktop as an example:

Click the briefcase icon.
Under Connectors, click Add custom connector.
Enter a name (e.g. "Workpath").
Paste the URL from Step 1.
Under Advanced settings, paste the Client ID and Client Secret.

Step 3: Authorize the connection

The new connector will show as Not Connected.
Click Connect.
Sign in with your Workpath credentials.
Approve the application to read and write data on your behalf.
The connector should now show as successfully authenticated.

Claude Code

claude mcp add --scope user --transport http --client-id "<CLIENT_ID>" --client-secret "workpath" "https://mcp.workpath.com/mcp"

In case you'd need to remove the workpath MCP (e.g. due to failing authentication caused by a faulty setup), here's a quick snippet:

claude mcp remove workpath

Codex App

Codex stores its MCP configuration in a single file shared by both the desktop app and the CLI: ~/.codex/config.toml (macOS/Linux) or %USERPROFILE%\.codex\config.toml (Windows). Because Codex has no field for pasting pre-registered OAuth credentials, the Workpath connection is configured in this file via the mcp-remote helper, which performs the sign-in and refreshes your token automatically.

Prerequisite: Node.js must be installed (it provides the npx command).

Step 1: Add Workpath to your Codex config

Open ~/.codex/config.toml (create it if it doesn't exist) and add the following block, pasting the Client ID and Client Secret from "Create MCP credentials" above:

toml
[mcp_servers.workpath]
command = "npx"
args = [
   "-y",
   "mcp-remote@latest",
   "https://mcp.workpath.com/mcp",
   "--static-oauth-client-info",
   "{\"client_id\":\"<CLIENT_ID>\",\"client_secret\":\"<CLIENT_SECRET>\"}",
]
startup_timeout_sec = 60.0

If Codex reports that it can't find npx (common when Node is managed by nvm), replace "npx" with its full path. Find it by running which npx in a terminal, e.g. /Users/you/.nvm/versions/node/v24.14.0/bin/npx.

Step 2: Restart and authorize

Save the file and fully quit and reopen Codex. Then ask Codex to use a Workpath tool, for example "list my cycles". The first time, a browser window opens - sign in with your Workpath credentials and approve access. Your token is cached locally and refreshed automatically from then on, so you only sign in once.

Codex CLI

The Codex CLI uses the same ~/.codex/config.toml as the Codex app (see above). If you've already completed the Codex App setup above, the CLI works with no additional steps.

If you use only the CLI, add the same [mcp_servers.workpath] block shown in the Codex App section to ~/.codex/config.toml, then trigger the one-time sign-in by running any prompt that uses a Workpath tool:

codex exec "List my Workpath cycles using the workpath MCP server."

The first run opens a browser for sign-in; afterwards the token refreshes automatically. To confirm the server is registered, run:

codex mcp list

Troubleshooting: if you ever get an authentication error, clear the cached tokens and try again:

rm -rf ~/.mcp-auth/mcp-remote-*

Copilot Studio

It is possible to wrap Workpath MCP connection as a tool for your custom agent in Copilot Studio.

Navigate to your agent, find "Tools" and click "Add tool"
Select "Model Context Protocol"
Enter basic app details:
Server name: Workpath (you can choose this freely)
Server description: Read and write Goal and Initiative data from Workpath. (you can choose this freely)
Server URL: https://mcp.workpath.com/mcp
Enter authentication details:
Authentication: OAuth 2.0
Type: Manual
Client ID & Client secret: Copy these from MCP connection settings inside Workpath
Authorization URL: https://mcp.workpath.com/authorize
Token URL template: https://mcp.workpath.com/token
Refresh URL: https://mcp.workpath.com/token
Scopes: public
In the next step, you'll be asked to connect using your personal Workpath account, and grant access.

Done! You should now be able to explore Workpath data from your Copilot agent:

What's included

The MCP integration provides ~30 read-only tools, including:

Search and retrieve Goals, Key Results, and Initiatives
Get alignment suggestions and contribution requests
Look up cycles, teams, KPIs, and labels
Access notes and quality checks

You can use these tools to ask questions about your Workpath data, create presentations, or integrate Workpath context into your preferred AI-powered workflow.