Wrike Universal MCP Server

What is Wrike Universal MCP Server about?

The server implements a Wrike Universal MCP (Model Context Protocol) service, exposing Wrike’s functionality via a consistent, language‑agnostic API that can be consumed by any MCP‑compatible client.

How to use Wrike Universal MCP Server?

1. Prerequisites – install Python 3.11+ and the uv package manager.
2. Set up the environment

   uv sync            # install dependencies into .venv
   source .venv/bin/activate   # Linux/macOS
   # .venv\Scripts\Activate   # Windows PowerShell
   

3. Run the MCP inspector

   mcp dev src/universal_mcp_wrike/server.py
   

   Note the address and port displayed.
4. Install the application

   mcp install src/universal_mcp_wrike/server.py
   

5. Enable Wrike on the Agentr platform at https://agentr.dev/apps.

Key features of Wrike Universal MCP Server

• Full compliance with the MCP specification for seamless interoperability.
• Unified API that abstracts Wrike’s native endpoints.
• Ready‑to‑run server entry point (server.py) and tool definitions (app.py).
• Simple local development workflow using uv and the MCP CLI.
• MIT‑licensed, easy to extend or embed in larger automation pipelines.

Use cases of Wrike Universal MCP Server

• Integrating Wrike task management into custom AI agents or automation bots.
• Building cross‑platform connectors that need a consistent interface to Wrike.
• Rapid prototyping of workflow‑automation solutions that leverage Wrike’s data.
• Providing a backend for low‑code platforms that require MCP‑compatible services.

FAQ from the Wrike Universal MCP Server

Q: Do I need a Wrike account? A: Yes. The server forwards calls to Wrike’s API, so a valid account and API token are required (set via environment variables in .env).

Q: Can I run this on Windows? A: Absolutely. Use PowerShell to activate the virtual environment and run the same mcp commands.

Q: Is Docker support available? A: The repository does not include Docker files, but you can containerize the project by building an image that runs the same uv sync and mcp dev commands.

Q: How do I add custom tools? A: Extend src/universal_mcp_wrike/app.py with new MCP tool definitions and update the README in that folder.

Q: Where can I find the list of available tools? A: See src/universal_mcp_wrike/README.md for the complete catalog.

Wrike Universal MCP Server

This repository contains an implementation of an Wrike Universal MCP (Model Context Protocol) server. It provides a standardized interface for interacting with Wrike's tools and services through a unified API.

The server is built using the Universal MCP framework.

This implementation follows the MCP specification, ensuring compatibility with other MCP-compliant services and tools.

Usage

You can start using Wrike directly from agentr.dev. Visit agentr.dev/apps and enable Wrike.

If you have not used universal mcp before follow the setup instructions at agentr.dev/quickstart

Available Tools

The full list of available tools is at ./src/universal_mcp_wrike/README.md

Local Development

📋 Prerequisites

Ensure you have the following before you begin:

• Python 3.11+ (recommended)
• uv (install globally with pip install uv)

🛠️ Setup Instructions

Follow the steps below to set up your development environment:

1. Sync Project Dependencies

   uv sync
   

   This installs all dependencies from pyproject.toml into a local virtual environment (.venv).

2. Activate the Virtual Environment

   For Linux/macOS:

   source .venv/bin/activate
   

   For Windows (PowerShell):

   .venv\Scripts\Activate
   

3. Start the MCP Inspector

   mcp dev src/universal_mcp_wrike/server.py
   

   This will start the MCP inspector. Make note of the address and port shown in the console output.

4. Install the Application

   mcp install src/universal_mcp_wrike/server.py
   

📁 Project Structure

.
├── src/
│   └── universal_mcp_wrike/
│       ├── __init__.py       # Package initializer
│       ├── server.py            # Server entry point
│       ├── app.py            # Application tools
│       └── README.md         # List of application tools
├── tests/                    # Test suite
├── .env                      # Environment variables for local development
├── pyproject.toml            # Project configuration
└── README.md                 # This file

📄 License

This project is licensed under the MIT License.

---

Generated with MCP CLI — Happy coding! 🚀