# Wiki.js MCP for AI Agents AI Agent Connect

> Wiki.js MCP lets you manage your internal documentation directly from your AI agent. You can create new pages, search for existing guides, and update content without switching tabs. It turns your wiki into an interactive knowledge base where you can just ask for information or tell your agent to draft a new technical doc.

## Overview
- **Category:** productivity
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_UPX0fKnYH2Uxub9bz7ZciNLeJrgUF0N9yxnb0eVn/ai-agent-connect
- **Tags:** documentation, wiki, content-creation, knowledge-base, api-access

## Description

Managing a company wiki usually means jumping between tabs, hunting for the right URL, and wrestling with a manual editor. This Connector changes that by putting your entire knowledge base inside your chat interface. Instead of digging through folders, you can just ask your agent to find a specific deployment guide or summarize a policy. If you need to update something, you tell the agent what needs changing and it handles the edit. It's a much faster way to keep documentation current without the friction of a traditional UI. If you're looking for a way to make your internal docs more accessible, you'll find this is one of the most practical ways to do it on the Vinkius marketplace. Your agent handles the heavy lifting of navigating the API so you can just talk to your data.

## Tools

### update_page
Modify the content or publishing status of an existing wiki page.

### create_page
Create a new page in your Wiki.js instance with custom metadata and content.

### delete_page
Permanently remove a specific page from your wiki to keep your documentation organized.

### get_page
Fetch the content and metadata of a page using its unique URL path.

### list_pages
Retrieve a full list of all pages currently hosted in your Wiki.js instance.

### search_pages
Query your wiki for specific keywords to find relevant documentation quickly.

## Prompt Examples

**Prompt:** 
```
Find the internal guide for setting up the staging environment.
```

**Response:** 
```
I found a page titled **Staging Environment Setup** at the path `infra/staging`. It includes the following steps:

*   Run the setup script
*   Configure the API keys
*   Verify the connection

Would you like me to pull the full content?
```

**Prompt:** 
```
Create a new page for our Summer Internship program at the path hr/internships.
```

**Response:** 
```
I've created the **Summer Internship** page for you at `hr/internships`. I set it to published status. You can now tell me what content you'd like to add to it.
```

**Prompt:** 
```
Show me all the pages we have in the Security section.
```

**Response:** 
```
I've pulled the list of pages. You have 4 pages in the security folder:

| Page Title | Path |
| :--- | :--- |
| Password Policy | security/pass |
| VPN Access | security/vpn |
| Data Encryption | security/enc |
| Incident Response | security/ir |

Which one should I look into?
```

## Capabilities

### Create new documentation pages
Generate a new wiki page with specific metadata and content instantly.

### Search the entire wiki
Find specific information across all your pages using natural language.

### Update existing content
Modify the text or status of a page without opening the editor.

### List all available pages
Get a bird's-eye view of your entire wiki structure.

### Fetch specific page content
Pull the raw text and metadata of a page based on its URL path.

### Delete outdated pages
Remove old documentation to keep your knowledge base clean.

## Use Cases

### Finding a deployment guide
An engineer asks for the production deploy steps and the agent uses search_pages to find the right path and summarizes it.

### Updating an API change
A developer tells the agent to update the v2 auth page, and it uses update_page to change the outdated credentials.

### Onboarding a new hire
A manager asks the agent to list all onboarding pages so the new employee can see the full training path.

### Creating a new project doc
A lead asks the agent to create a new page at projects/alpha for the new initiative, and it uses create_page to set it up.

## Benefits

- Stop hunting for URLs by using search_pages to find any guide in seconds.
- Update technical docs faster by telling your agent to use update_page on specific content.
- Keep your knowledge base clean by using delete_page to prune old information.
- Draft new content quickly with create_page to save time on manual formatting.
- Get a full overview of your wiki structure instantly with list_pages.
- Access raw page data via get_page to feed your agent specific context for complex tasks.

## How It Works

The bottom line is that your documentation becomes a conversational tool rather than a static library.

1. Connect your Wiki.js instance by providing your API URL and Key.
2. Grant your AI client permission to interact with your wiki pages.
3. Start asking your agent to find, create, or edit documentation.

## Frequently Asked Questions

**How does the Wiki.js MCP help my team find info?**
It lets your team ask your AI agent questions about your internal docs. Instead of searching a website, they get direct answers pulled from Wiki.js.

**Can I use the Wiki.js MCP to create new pages?**
Yes, you can tell your agent to create a new page at a specific path with a title. It handles the creation and metadata for you.

**Does the Wiki.js MCP support searching my whole wiki?**
It does. Your agent can search across all your Wiki.js content to find specific keywords or topics instantly.

**Can I update my documentation without using the Wiki.js web UI?**
Yes, you can use your agent to modify existing pages. Just tell it what needs to change and it will call the update tool.

**Is my Wiki.js data secure with this Connector?**
Your data stays in your Wiki.js instance. This Connector just provides a way for your agent to talk to your API using the keys you provide.

**What happens if I delete a page using the Wiki.js MCP?**
The page is removed from your Wiki.js instance. It's best to use the list tool to confirm the path before you do this.

**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.