CursorIDE

Wiki.js MCP Server

Bring Documentation
to Cursor

Name: Wiki.js MCP Server
Price: 29 USD
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

Learn how to connect Wiki.js to Cursor and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Create PageDelete PageGet PageList PagesSearch PagesUpdate Page

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

What is the Wiki.js MCP Server?

Connect your Wiki.js instance to any AI agent and take full control of your internal knowledge base through natural conversation. This server allows you to interact with your documentation without leaving your chat interface.

What you can do

Page Management — Create new pages with full metadata, update existing content by ID, or delete outdated documentation.
Search & Discovery — Search across your entire wiki for specific keywords or list all available pages to understand your knowledge structure.
Content Retrieval — Fetch the raw content and metadata of any page using its URL path and locale.
Flexible Editing — Support for different editor types and publishing statuses (published/private) directly via the API.

How it works

Subscribe to this server
Enter your Wiki.js API URL and API Key
Start managing your documentation from Claude, Cursor, or any MCP-compatible client

Who is this for?

Developers — quickly update technical docs or search for internal guides while coding.
Knowledge Managers — organize and prune wiki content through simple natural language commands.
Support Teams — find relevant internal documentation to answer customer queries faster.

Built-in capabilities (6)

create_page

Create a new Wiki.js page

delete_page

Delete a Wiki.js page

get_page

Fetch a Wiki.js page by path

list_pages

List all Wiki.js pages

search_pages

Search for content in Wiki.js

update_page

Update an existing Wiki.js page

Why Cursor?

Cursor's Agent mode turns Wiki.js into an in-editor superpower. Ask Cursor to generate code using live data from Wiki.js and it fetches, processes, and writes. all in a single agentic loop. 6 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

—
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
—
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
—
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
—
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

See it in action

Wiki.js in Cursor

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

Wiki.js and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Wiki.js to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready

<40msCold start

60%Token savings

	Raw MCP	Vinkius
Server catalog	Find and host yourself	4,000+ managed
Infrastructure	Self-hosted	Sandboxed V8 isolates
Credential handling	Plaintext in config	Vault + runtime injection
Data loss prevention	None	Configurable DLP policies
Kill switch	None	Global instant shutdown
Financial circuit breakers	None	Per-server limits + alerts
Audit trail	None	Ed25519 signed logs
SIEM log streaming	None	Splunk, Datadog, Webhook
Honeytokens	None	Canary alerts on leak
Custom domains	Not applicable	DNS challenge verified
GDPR compliance	Manual effort	Automated purge + export

Unlock for AI Agents View step-by-step setup guide for Cursor →

Enterprise Security

Why teams choose Vinkius for Wiki.js in Cursor

The Wiki.js 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. All 6 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Unlock for AI Agents View full Wiki.js details →

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

The Vinkius Advantage

How Vinkius secures
Wiki.js for Cursor

Every tool call from Cursor to the Wiki.js MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start

Ed25519Signed audit chain

60%Token savings

FAQ

Frequently asked questions

Can I search for specific keywords across all my wiki pages?

Yes! Use the search_pages tool with your query string. The agent will scan all content and return relevant page matches including titles and paths.

How do I fetch the content of a specific page if I have the URL path?

Use the get_page tool. Simply provide the path (e.g., 'home' or 'engineering/setup') and the agent will retrieve the full content and metadata for that specific page.

Is it possible to modify an existing page's content?

Absolutely. Use the update_page tool by providing the unique page ID and the new content or title you wish to apply. The agent will handle the update via the Wiki.js API.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Explore More MCP Servers

View all →

PayFit

7 tools

Automate HR and payroll operations via PayFit — list collaborators, fetch payslips securely, overview company structure, and export accounting entries via AI.