Bring Documentation
to Claude Desktop
Learn how to connect Wiki.js to Claude Desktop 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 SubscribersCompatible with every major AI agent and IDE
Gemini
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 a new Wiki.js page
Delete a Wiki.js page
Fetch a Wiki.js page by path
List all Wiki.js pages
Search for content in Wiki.js
Update an existing Wiki.js page
Why Claude Desktop?
Claude Desktop is the definitive way to connect Wiki.js to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 6 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Wiki.js in Claude Desktop
Wiki.js and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Wiki.js to Claude Desktop 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.
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 |
Why teams choose Vinkius for Wiki.js in Claude Desktop
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 Claude Desktop 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.
* 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
How Vinkius secures
Wiki.js for Claude Desktop
Every tool call from Claude Desktop to the Wiki.js MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
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.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Tactiq
10 toolsManage meeting transcripts via Tactiq u2014 access summaries, action items, speaker analytics, and search across all recordings from your AI agent.
Mailjet
8 toolsSend transactional emails and manage marketing campaigns via the Mailjet REST API.
Fantastical
10 toolsManage calendars via Fantastical — create events using natural language, handle scheduling openings and proposals, and monitor connected accounts directly from any AI agent.
DOAJ
8 toolsSearch and manage open access research journals and articles via the Directory of Open Access Journals (DOAJ).