How to Use the Wrike MCP in LlamaIndex

Q: Can I query past Wrike information using LlamaIndex?

Yes. By indexing the output from tools like listwriketasks, you can query historical or previous data sets and get answers based on the actual records, avoiding hallucinations.

Ground your AI client in reality: LlamaIndex indexes Wrike data for semantic search.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Wrike MCP to LlamaIndex

Create your Vinkius account to connect Wrike to LlamaIndex and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Wrike with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Indexing Wrike Data into Vector Stores

LlamaIndex doesn't just run the tool; it takes the output and turns it into searchable knowledge. If you run `list_wrike_contacts`, those names, roles, and IDs get indexed. You can then query past sessions or configurations and get answers grounded in that actual API data. This makes your Wrike MCP Server output part of a unified, queryable index.

Building RAG Applications with the MCP Server

Want to combine live project data with internal documents? The `list_wrike_projects` tool provides structured API data that you can feed alongside your knowledge base. You build a Retrieval Augmented Generation (RAG) app where the AI client cross-references both sources. It’s about getting answers based on what Wrike *actually* says, not what it might hallucinate.

Targeted Task and Folder Queries

You can use `list_wrike_folders` to find all relevant project groupings. Then, you run `list_wrike_tasks`, optionally providing a folder ID to scope the results right down to the necessary tasks. This focused approach ensures that when the data is indexed, it's highly specific and immediately useful for semantic search.

Setup guide

Set up Wrike MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Wrike MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Wrike tools.",
)
response = await agent.run("List recent Wrike data")

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Wrike. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Wrike now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Wrike MCP in LlamaIndex

The core mechanism here is indexing. When your AI client calls a tool, the resulting data—like project names or task lists—becomes part of a searchable knowledge base. This grounds subsequent queries in real API results.

Yes. By indexing the output from tools like `list_wrike_tasks`, you can query historical or previous data sets and get answers based on the actual records, avoiding hallucinations.

You use the combination of tools. For example, index all contacts via `list_wrike_contacts`, and then query for a contact's role or associated project ID weeks later.

Yes. By including resources in your setup, you allow the client to process structured lists like those from `list_wrike_spaces` and integrate them into a richer knowledge context.

The server indexes organizational metadata, including task details, project listings, folder structures, and user contact information. The output of these tools forms the basis of your searchable knowledge.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript