2,500+ MCP servers ready to use
Vinkius

Wrike MCP Server for VS Code Copilot 6 tools — connect in under 2 minutes

Built by Vinkius GDPR 6 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Wrike and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "wrike": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Wrike
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Wrike MCP Server

Connect your Wrike account to any AI agent and manage your enterprise workflows through natural conversation.

GitHub Copilot Agent mode brings Wrike data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 6 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

  • Task Monitoring — List and browse tasks across your entire account or filter by specific folder/project IDs
  • Deep Task Analysis — Retrieve comprehensive metadata for specific tasks, including descriptions, assignees, and custom fields
  • Project Navigation — Browse top-level project containers and monitor their current status and organization
  • Folder Hierarchy — Explore your organizational structure to understand how tasks are grouped and categorized
  • Team Discovery — List all users and contacts within your Wrike workspace to find IDs for task assignment
  • Space Access — List all available work areas (spaces) to navigate your team's different departments or functions
  • Workflow Automation — Quickly find unique task and folder IDs required for building automated project management flows

The Wrike MCP Server exposes 6 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Wrike to VS Code Copilot via MCP

Follow these steps to integrate the Wrike MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Wrike

Ask Copilot: "Using Wrike, help me...". 6 tools available

Why Use VS Code Copilot with the Wrike MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Wrike through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Wrike + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Wrike MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Wrike MCP Tools for VS Code Copilot (6)

These 6 tools become available when you connect Wrike to VS Code Copilot via MCP:

01

get_task_details

Retrieves comprehensive details for a specific Wrike task

02

list_wrike_contacts

Lists all users and contacts within the Wrike workspace

03

list_wrike_folders

Lists all folders and projects in the Wrike account

04

list_wrike_projects

Lists all active projects in the account

05

list_wrike_spaces

Lists all Wrike spaces available to the authenticated user

06

list_wrike_tasks

You can optionally provide a folder_id to scope the results. Lists tasks in the Wrike account, optionally filtered by folder

Example Prompts for Wrike in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Wrike immediately.

01

"List all my Wrike projects."

02

"Show me tasks in the 'Product Launch 2026' folder."

03

"Get full details for task ID 'IEA...'."

Troubleshooting Wrike MCP Server with VS Code Copilot

Common issues when connecting Wrike to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Wrike + VS Code Copilot FAQ

Common questions about integrating Wrike MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Connect Wrike to VS Code Copilot

Get your token, paste the configuration, and start using 6 tools in under 2 minutes. No API key management needed.