Setup Claude Code with Wrike MCP

This guide covers setup for Claude Code — Anthropic's CLI tool for developers. Claude Code supports native OAuth for MCP servers. You do not need third-party tools like mcp-remote.

Prerequisites

Claude Code installed on your machine
A Wrike app with OAuth credentials (see Authentication setup, Step 1)
The redirect URL http://localhost:8080/callback added to your Wrike app so Claude Code can receive the OAuth callback after Wrike authorization

Step 1: Authentication and setup for administrator

All user permissions from Wrike are automatically enforced. The MCP server respects the same security boundaries as your workspace — users can only access data they have permission to view in Wrike.

OAuth 2.0 (recommended)

Step 1: Create a Wrike App (administrator, one-time per organization) on Apps & Integrations

A user with access to Apps & Integrations (preferably the account owner) performs this setup once:

In Wrike, click your profile icon and select Apps & Integrations
Click the API tab
Click Create new app
Fill in the app details:
- App name — e.g., "Wrike MCP Integration"
- App description — e.g., "Wrike App necessary to connect the Wrike MCP to AI assistants"
The OAuth Client ID and Secret key are generated automatically. Copy them securely — you will need them in the next step.
Under Redirect URLs, add the redirect URL http://localhost:8080/callback
You can add multiple redirect URLs to support several AI assistants from the same Wrike app.
Leave the remaining settings unchanged and click Save

📘
Unlike Permanent Access Token authentication, OAuth apps are organization-wide — any user in the account can authenticate through them. The admin creates the app once; individual users authenticate with their own Wrike credentials.

Step 2: Add the Wrike MCP server

Run the following command in your terminal:

claude mcp add --transport http \
    --client-id YOUR_CLIENT_ID \
    --client-secret \
    --callback-port 8080 \
    wrike https://mcp.wrike.com/app/mcp/stream

Replace YOUR_CLIENT_ID with the OAuth Client ID from your Wrike app.

After you press Enter, Claude Code will prompt you to enter your OAuth Client Secret. Claude Code hides the secret as you type and stores it securely in your system keychain.

Step 3: Authorize with Wrike

Start a Claude Code session by running claude in your terminal
Run the /mcp command inside the session to view the connection status
Claude Code will open your browser for OAuth authorization
Log in with your Wrike credentials and approve the connection
The browser will close automatically after authorization completes

Step 3: Verify the connection

In your Claude Code session, try a simple prompt to confirm the connection is working:

What Wrike tasks were assigned to me this week?

If the connection is successful, Claude Code will use the Wrike MCP tools to retrieve and display your recent tasks.

Configuration details

The MCP server configuration is stored in one of these locations:

User-level: ~/.claude.json — applies to all your Claude Code sessions
Project-level: .mcp.json — applies only to the current project directory

These files contain only non-sensitive configuration metadata. OAuth credentials are stored securely in your system keychain.

Alternative: Permanent Access Token authentication

If you prefer to use Permanent Access Token authentication instead of OAuth, add the following to your ~/.claude.json or project-level .mcp.json:

{
  "mcpServers": {
    "wrike": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.wrike.com/app/mcp/stream",
        "--header",
        "Authorization:Bearer YOUR_ACCESS_TOKEN"
      ]
    }
  }
}

Replace YOUR_ACCESS_TOKEN with your Wrike Permanent Access Token. See Alternative Authentication Setup for how to generate one.