WrikeWay Back to WrikeWay
Documentation

Copilot Studio Wrike MCP Agent

Connect a Microsoft Copilot Studio agent to Wrike through the XtendMCP (WPP Media) PROD gateway.

Overview

This guide walks you through creating a Copilot Studio agent that talks to Wrike over MCP (Model Context Protocol). Each user signs in with their own Wrike account, so the agent's results follow that user's Wrike permissions.

About 8–10 minutes to set up

Pilot terms of use

Xtend MCP Gateway — please read these terms before you connect an agent to Wrike.

  1. Pilot service, live data: the gateway is a pilot service, but it connects to the live WPP Wrike instance. Any create, update or delete is made directly to production data and can’t be undone by the pilot team. Gateway features, tools and availability may change during the pilot, and support is provided by the Global Wrike Team on a best-effort basis.
  2. Approved use cases only: use the gateway for the business use case submitted in your pilot application.
  3. Your own access: each user connects with their own Wrike account and sees only what their Wrike permissions allow.
  4. No sensitive data: don’t send personal, client-confidential or regulated data to Wrike through AI agents or apps without approval from your data owner.
  5. Review before you change anything: AI agents can make mistakes. Check results against Wrike before acting on them, and review every create, update or delete before confirming it, because changes apply immediately to live Wrike data. Start with read-only use until you’re confident in the results.
  6. Apps and automation: apps or agents built on the gateway are for pilot testing only. Sharing or deploying them beyond your team needs review by the Global Wrike Team and AICOE.
  7. Support scope: the Global Wrike Team supports gateway access, API/MCP usage and pilot issues. Design, development and support of your own app stay with your team.

Before you start

  • Your Wrike user needs API and MCP access enabled. Contact the Global Wrike Team.
  • Use Copilot Studio (https://copilotstudio.microsoft.com).
  • MCP server URL: https://xpi-api.gowrike.space/api/v1/wrikexpi/mcp

Set up the agent

Work through steps 1–17 in order. They are grouped into three stages.

Create the agent · steps 1–6

  1. 1

    Open Copilot Studio.

  2. 2

    Choose the environment: click the environment switcher (bottom left) and select GRM-Global-Wrike DEV (Sandbox). If it isn’t in your list, select insidemedia.net (Upgrade), the default environment.

  3. 3

    Click New agent › Agent (Standard).

  4. 4

    Name your agent (for example, “Wrike MCP Agent”) and click Create.

  5. 5

    Give consent: in the Test panel, click Confirm on the “Consent confirmation” message.

  6. 6

    Set the model: once the agent shows “Your agent has been provisioned”, choose Claude Opus 4.8 under “Select your agent’s model”. It works well for multi-step queries.

Add the Wrike MCP server · steps 7–14

  1. 7

    Go to Tools › Add a tool › Model Context Protocol.

  2. 8

    Enter a Server name and Server description, and in Server URL paste:

    https://xpi-api.gowrike.space/api/v1/wrikexpi/mcp

    Remember the server name — you will use it to find the connector when you share it.

  3. 9

    Under Authentication, select OAuth 2.0. Set Type to Dynamic discovery, then click Create.

  4. 10

    Next to Connection, open the drop-down, click Create new connection, then click Create.

  5. 11

    Choose the environment: in the “Connect to Wrike Xtend” window, select XtendMCP (WPP Media) PROD and click Continue. Complete the Wrike sign-in if asked.

  6. 12

    When the connection shows a green tick, click Add.

  7. 13

    Open the tool you added: click its name in the Tools list.

  8. 14

    Check that the tools are listed (for example, xtend_... and wrike_... tools). If they appear, the connection is working.

Publish and test · steps 15–17

  1. 15

    Click Publish, then Publish again in the pop-up.

  2. 16

    Make sure the connection is active: in the Test panel, ask “Who am I in Wrike?”

    If you see “Let’s get you connected first”:

    1. Click Open connection manager.
    2. Find your connection. If its status is Not Connected, click Connect and sign in. The status should change to Connected with a green tick.
    3. Go back to the Test panel and click Retry.
  3. 17

    Test it: ask “Who am I in Wrike?” and “Show my overdue tasks.”

Share the agent with your team

Make the agent available in Microsoft Teams and Microsoft 365. Then share the connector so your teammates can use it.

  1. 1

    Go to Channels and select Microsoft 365 and Microsoft Teams.

  2. 2

    Publish the agent first: when “Ready to publish?” appears, click Publish and wait until it finishes. You can’t share the agent until it’s published. If you see “You need to publish your agent before you can make it available to others”, click Go to publish.

  3. 3

    Click Edit details.

    • Tick “Use this agent for group and meeting chats” if the team will use it in a group chat.
    • Optionally, update the developer name and description.
    • Save, then publish again.
  4. 4

    Use Availability options to share the agent with your team members.

  5. 5

    Click See agent in Teams, then Add (just for you) or Add to a chat (for a group chat).

Share the connector

The agent uses a custom connector in Power Apps. Share it with the same team members, or the agent won’t work for them.

  1. 1

    Open Power Apps: https://make.powerapps.com

  2. 2

    Check that the Environment (top right) is the same one you built the agent in, for example GRM-Global-Wrike DEV or insidemedia.net (Upgrade).

  3. 3

    In the left menu, click Custom connectors and find your connector by name (the server name from step 8).

  4. 4

    Click ⋯ next to it, then Share.

  5. 5

    Under Add people, enter your team members’ names or emails and save.

  6. 6

    Each person signs in with their own Wrike account the first time they use the agent, through the connection manager.

Don’t use “Share with org”. People you add to the connector can edit it, so add only the team members who need it.

Troubleshooting

“Let’s get you connected first”, or the connection stops working

Click Open connection manager. If the status is Not Connected, click Connect and sign in, then go back to the Test panel and click Retry.

“You need to publish your agent before you can make it available to others”

Click Go to publish and publish the agent first, then continue sharing.

The environment you need isn’t listed

Select insidemedia.net (Upgrade), the default environment, in the environment switcher.

The agent doesn’t work for a teammate

Check that both the agent and the connector are shared with them, and that they have signed in to Wrike through the connection manager.

Built by the WPP Enterprise Technology · Wrike Team

Back to WrikeWay