Skip to content

feat(productivity): add wrike as project tracker integration (#1)#1

Open
jrfk wants to merge 1 commit intogroove-x:mainfrom
jrfk:main
Open

feat(productivity): add wrike as project tracker integration (#1)#1
jrfk wants to merge 1 commit intogroove-x:mainfrom
jrfk:main

Conversation

@jrfk
Copy link
Member

@jrfk jrfk commented Feb 7, 2026

What

productivity に wrikeを追加

Why

NO_NEWS

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds Wrike as a supported project tracker option for the productivity plugin, updating user-facing docs and the plugin’s default MCP server configuration.

Changes:

  • Mention Wrike in /start and /update command documentation as a supported task source.
  • Update connector documentation to list Wrike as an included project tracker server.
  • Add a Wrike MCP server entry to productivity/.mcp.json.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
productivity/commands/update.md Adds Wrike to project tracker examples in the update workflow docs.
productivity/commands/start.md Adds Wrike to examples of supported task apps during bootstrap.
productivity/README.md Lists Wrike among included MCP connections for project trackers.
productivity/CONNECTORS.md Moves Wrike into the “Included servers” list for project trackers.
productivity/.mcp.json Adds a Wrike MCP server configuration entry.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

"url": "https://mcp.atlassian.com/v1/mcp"
},
"wrike": {
"type": "http",
Copy link

Copilot AI Feb 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wrike MCP entry uses a URL ending in /sse but config sets type to http. In this repo, SSE endpoints are configured with type: "sse" (see cowork-plugin-management/.../customized-mcp.json), so this looks like a misconfiguration that will prevent the Wrike connector from working. Update either the type to sse or change the URL to the correct HTTP /mcp endpoint (whichever matches Wrike's MCP server).

Suggested change
"type": "http",
"type": "sse",

Copilot uses AI. Check for mistakes.
Copy link
Member Author

@jrfk jrfk Feb 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The official website has the following description. What would be the appropriate way to set it up?

Step 2: Configure Your AI Assistant
For Cursor/Claude Desktop Users

Add the following JSON to your configuration file:

{
  "mcpServers": {
    "wrike": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://www.wrike.com/app/mcp/sse",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}
Replace YOUR_API_TOKEN with your actual Wrike API token.

If your Wrike account is located in the EU datacenter, use https://app-eu.wrike.com/app/mcp/sse as your connection url instead of https://www.wrike.com/app/mcp/sse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants