4,000+ servers built on vurb.ts
Vinkius
Wiki.js

Wiki.js MCP Server with 6 Tools for Claude, Cursor, and AI Agents

MCP Inspector GDPR Free for Subscribers

Manage your Wiki.js instance—create, search, and update documentation pages directly from your AI agent. Vinkius routes your AI agents directly to Wiki.js through a governed connection. 6 tools ready to use with Claude, ChatGPT, Cursor, or any AI agent — no hosting, no setup, connect in 30 seconds.

Built for AI Agents by Vinkius

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
AI AgentVinkius
High Security·Kill Switch·Plug and Play
Wiki.js
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

What is the Wiki.js MCP Server?

The Wiki.js MCP Server routes AI agents like Claude, ChatGPT, and Cursor directly to Wiki.js via 6 tools. Manage your Wiki.js instance—create, search, and update documentation pages directly from your AI agent. Powered by Vinkius — your credentials stay on your side of the connection, every request is auditable. Connect in under 2 minutes.

Built-in capabilities (6)

create_pagedelete_pageget_pagelist_pagessearch_pagesupdate_page

Tools for your AI Agents to operate Wiki.js

Ask your AI agent "Search for 'deployment guide' in our Wiki.js." and get the answer without opening a single dashboard. With 6 tools connected to real Wiki.js data, your agents reason over live information, cross-reference it with other MCP servers, and deliver insights you would spend hours assembling manually.

Works with Claude, ChatGPT, Cursor, and any MCP-compatible client. Powered by Vinkius — your credentials never touch the AI model, every request is auditable. Connect in under two minutes.

Why teams choose Vinkius

One subscription gives you the infrastructure to connect your AI agents to thousands of MCP servers — and deploy your own to the Vinkius Edge. Your credentials stay yours. Your data flows directly between your agent and the API. DLP blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade routing and governance, zero maintenance.

Build your own MCP Server with our secure development framework →

The Wiki.js App Connector works with every AI agent you already use

…and any MCP-compatible client

CursorClaudeOpenAIVS CodeCopilotGoogleLovableMistralAWSCursorClaudeOpenAIVS CodeCopilotGoogleLovableMistralAWS

Use all 6 Wiki.js tools with your AI agents right now

Vinkius routes your AI agents to Wiki.js through a governed proxy. Beyond a simple connection, you get full visibility into every action your agents perform, with enterprise-grade security and up to 60% savings on AI costs.

Explore Tools Hub
create

Create page on Wiki.js

Create a new Wiki.js page

delete

Delete page on Wiki.js

Delete a Wiki.js page

get

Get page on Wiki.js

Fetch a Wiki.js page by path

list

List pages on Wiki.js

List all Wiki.js pages

search

Search pages on Wiki.js

Search for content in Wiki.js

update

Update page on Wiki.js

Update an existing Wiki.js page

What the Wiki.js MCP Server unlocks

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

1. Subscribe to this server
2. Enter your Wiki.js API URL and API Key
3. 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.

Frequently asked questions about the Wiki.js MCP Server

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.

Vinkius AI Gateway

We built the connector to Wiki.js. Now put your agents to work. Fully governed.

Vinkius is the AI Gateway with managed hosting. Stop building connectors. Every connection runs inside eight layers of security.

How it works
Infrastructure

Hosted, sandboxed, and live on AWS. You don't provision anything. You don't maintain anything. You connect.

Visibility

Every tool call, every token, every response. Logged and auditable. Data flows direct from Wiki.js to your agent. Nothing is stored on our side. Ever.

Control

Eight governance layers on every request. Sensitive data redacted before it reaches the model. Kill switch if anything goes sideways. Always on.