Connect Wrike to Glean

Connect Wrike to Glean so users can access Wrike tools in Glean Assistant and Glean Agents. A Glean administrator configures the connection and selects which tools to make available. Each user authorizes access with their own Wrike account.

Before you begin

You need administrator access to Glean’s tools or connectors settings.
A Wrike administrator or a user with access to Apps & Integrations must create a Wrike OAuth application.
Your Glean deployment must be able to reach Wrike’s MCP server.

Check the Glean Connectors catalog

In Glean, open Admin console → Connectors and check whether Wrike is available.

If it is, follow the catalog setup flow. If Wrike isn’t listed, continue with the custom MCP setup below. Glean directs admins to its remote MCP flow for custom or unlisted servers. Glean’s Connectors setup guide

Create a Wrike OAuth application

In Wrike:

Open Profile → Apps & Integrations → API.
Select Create new app and save the application.
Keep the generated Client ID and Secret key available for Glean’s configuration.
After starting the Glean setup, add the redirect URL shown by Glean to the Wrike app’s redirect URLs.

Wrike’s OAuth endpoints are:

Authorization URL: https://login.wrike.com/oauth2/authorize/v4
Token URL: https://login.wrike.com/oauth2/token

Use the exact redirect URL Glean provides. Wrike OAuth documentation

Add Wrike MCP in Glean

In Glean, open Admin console → Platform → Tools → Vendor Provided Tools (via MCP), then choose Add → Import tools from MCP server.

Configure the server:

Server name: Wrike
Server URL: https://mcp.wrike.com/v2
Transport: Streaming HTTP
Authentication: OAuth User
Authorization URL: https://login.wrike.com/oauth2/authorize/v4
Token URL: https://login.wrike.com/oauth2/token
Client ID and client secret: From the Wrike OAuth application
Redirect URL: Copy the callback URL shown by Glean into the Wrike OAuth app

Wrike MCP v2 uses Streamable HTTP. Glean’s setup guide calls the matching transport option Streaming HTTP. Wrike MCP setup guide Glean’s remote MCP setup guide

Connect and publish tools

Connect the server so Glean can discover Wrike’s tools. Review the discovered tools, enable the ones your organization wants to offer in Assistant or Agents, and save the configuration.

The administrator connection is for tool discovery and configuration. Each user must authorize their own Wrike account before using the tools.

Verify the connection

In Glean Assistant, ask it to use a Wrike tool—for example:

Use Wrike to find tasks assigned to me this week.

Confirm that Glean invokes a Wrike tool and returns results available to the connected Wrike user. For an action that changes Wrike data, confirm the intended change before proceeding.

Permissions

Wrike MCP follows the permissions of the authenticated Wrike user. Connecting Wrike to Glean does not grant users additional access to Wrike. Glean administrators can also control which MCP tools are available in their organization. Wrike MCP setup guide Glean’s remote MCP setup guide

Editorial note: Glean’s documentation says to check the catalog first and use the custom flow for unlisted servers. I’d keep that condition in the copy rather than imply Wrike is a Glean-certified integration. The exact Glean UI labels may vary by deployment and configuration.