Connect Wrike MCP as a custom connector

Wrike provides a remote Model Context Protocol (MCP) server that you can connect to from MCP-compatible AI assistants and applications.

Use custom connector setup when:

Wrike is not available in your AI assistant's connector marketplace
you want to configure the MCP connection manually
you are building or testing your own MCP client
your organization requires a custom MCP configuration

If Wrike is already available in your AI assistant's connector marketplace, we recommend using the official Wrike connector instead.

Wrike MCP server

Use the following server URL:

https://mcp.wrike.com/v2

Wrike MCP v2 uses Streamable HTTP.

Authentication options

Wrike MCP supports two authentication approaches:

OAuth 2.0

Recommended for interactive user connections.

An administrator creates a Wrike OAuth application once. Individual users then authenticate using their own Wrike accounts.

OAuth is recommended when multiple users will connect to Wrike or when your MCP client supports OAuth authentication natively.

Permanent Access Token

Recommended for individual testing, automation, and environments where interactive OAuth is not appropriate.

Each Permanent Access Token belongs to an individual Wrike user and inherits that user's permissions.

See Permanent Access Token authentication for setup instructions.

Set up OAuth 2.0

Step 1: Create a Wrike OAuth application

A user with access to Apps & Integrations creates the application:

In Wrike, click your profile icon and select Apps & Integrations.
Open the API tab.
Click Create new app.
Enter an application name, for example:

Wrike MCP Integration
Optionally enter a description, for example:

OAuth application for connecting an MCP client to Wrike
Wrike generates an OAuth Client ID and Secret key. Store both securely.
Add the OAuth redirect URL required by your MCP client.
Click Save.

You can add multiple redirect URLs to the same Wrike OAuth application if you use it with several MCP clients.

The Wrike OAuth application only defines the integration. It does not give users additional access to Wrike. Each user authenticates with their own Wrike account, and their existing Wrike permissions are enforced.

Step 2: Configure the custom connector

In your MCP client, create a new custom connector or MCP server connection.

Use:

Server URL

https://mcp.wrike.com/v2

Authentication

OAuth 2.0

Client ID

Enter the OAuth Client ID generated by your Wrike application.

Client Secret

Enter the Secret key generated by your Wrike application.

Redirect URL

Use the callback or redirect URL required by your MCP client. Make sure the exact same URL is also configured under Redirect URLs in your Wrike OAuth application.

The exact names of these settings may vary between MCP clients.

Step 3: Authenticate with Wrike

After you configure the connector:

Connect or enable the Wrike MCP server in your AI assistant.
Your browser opens the Wrike authorization flow.
Sign in to Wrike.
Approve access.
Return to your AI assistant.

The Wrike MCP connection now operates with the permissions of the authenticated Wrike user.

Step 4: Verify the connection

Try a simple request such as:

What Wrike tasks are assigned to me this week?

If the connection is working, your AI assistant should use Wrike MCP to retrieve your tasks.

You can also try:

Find my overdue Wrike tasks.

Show me the projects I am responsible for.

Permissions

Wrike MCP respects your existing Wrike permissions.

Connecting through MCP does not grant users additional access. Users can only access data and perform actions that they are already authorized to access or perform in Wrike.

Alternative: Permanent Access Token authentication

If OAuth is not appropriate for your use case, you can authenticate using a Wrike Permanent Access Token.

Permanent Access Tokens are useful for:

individual testing
scripts and automation
headless or non-interactive environments
MCP clients that support custom authorization headers but not OAuth

See Permanent Access Token authentication for instructions on generating a token and configuring your MCP client.

Treat Permanent Access Tokens like passwords. Never commit them to source control.

Troubleshooting

Authentication fails

Check that:

the server URL is exactly https://mcp.wrike.com/v2
your OAuth Client ID and Secret key are correct
the redirect URL configured in your Wrike OAuth application exactly matches the redirect URL used by your MCP client
you are signing in with the intended Wrike account

I cannot create a Wrike OAuth application

Make sure you have access to Apps & Integrations in Wrike. Your organization's account owner can also create the application.

The connector works, but some Wrike data is unavailable

Wrike MCP follows your Wrike permissions. Confirm that your Wrike user has access to the requested data.

Some MCP tools are missing

Your MCP client may cache the available MCP tools.

Reconnect or refresh the Wrike connector to load the current tool list.

See Available tools on Wrike MCP for the current set of supported tools.