How to Use the Wiki.js MCP in Google ADK

Q: How can I search Wiki.js documentation using Google ADK?

You run the searchpages tool through your agent. It queries the entire Wiki.js content and returns targeted results, which you can then process in BigQuery.

Q: Can I add new pages to Wiki.js using Google ADK?

Yes, use createpage. Your agent executes this tool by providing the necessary title and initial content block for your new documentation page.

Q: Does Google ADK support updating existing wiki pages?

It does. The updatepage tool modifies current Wiki.js records. You specify the path and send the revised text, ensuring version control is maintained.

Q: What if I need to see a full list of Wiki.js pages using Google ADK?

The listpages tool executes a directory listing for your entire Wiki.js site, giving you the paths and names of all stored documentation.

Build enterprise agents using Google ADK for Wiki documentation.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Wiki.js MCP to Google ADK

Create your Vinkius account to connect Wiki.js to Google ADK 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 Wiki.js with Google ADK

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Search and retrieve specific Wiki content.

The `search_pages` tool lets your agent dig through all the articles in your Wiki.js knowledge base. Instead of reading everything, it finds relevant snippets based on keywords. This is ideal for building agents that answer complex questions by synthesizing information from multiple sources across Wiki.js.

Build and modify documentation pages.

Want to add a whole new section? Use `create_page` to generate a fresh article in your Wiki.js instance. You just pass the title and initial text, and it's live. You can also use `update_page` if you need to revise an existing document before publishing.

Keep track of all your documentation pages.

The `list_pages` tool provides a simple manifest, showing every page path available in Wiki.js. This is critical for auditing or building navigation menus. Need to verify the current state? Running `get_page` pulls down the full, raw content of any specific document.

Setup guide

Set up Wiki.js MCP in Google ADK

Prerequisites

Python 3.10+ installed
google-adk package (pip install google-adk)
Active Vinkius subscription with a valid endpoint token

1

Install Google ADK

Run pip install google-adk to install the Agent Development Kit. MCP support is included via the McpToolset class.
2

Connect via SSE transport

Use McpToolset.from_server() with SseServerParams pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create an LlmAgent

Pass the returned mcp_tools list directly to LlmAgent(tools=mcp_tools). The ADK maps each MCP tool to a native Gemini function call — no manual schema definitions required.
4

Run with any Gemini model

The agent works with any Gemini model (gemini-2.0-flash, gemini-2.5-pro, etc.). Copy the full example on the right to get started with Wiki.js tools in your ADK agent.

agent.py

from google.adk.agents import LlmAgent
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import SseServerParams

# Connect to the MCP via SSE
mcp_tools, exit_stack = await McpToolset.from_server(
    connection_params=SseServerParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    )
)

# Create your agent with auto-discovered tools
agent = LlmAgent(
    name="Wiki.js_agent",
    model="gemini-2.0-flash",
    instruction="You have access to Wiki.js tools via MCP.",
    tools=mcp_tools,
)

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 Wiki.js. 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 Wiki.js 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 Wiki.js MCP in Google ADK

You run the `search_pages` tool through your agent. It queries the entire Wiki.js content and returns targeted results, which you can then process in BigQuery.

Yes, use `create_page`. Your agent executes this tool by providing the necessary title and initial content block for your new documentation page.

It does. The `update_page` tool modifies current Wiki.js records. You specify the path and send the revised text, ensuring version control is maintained.

The `list_pages` tool executes a directory listing for your entire Wiki.js site, giving you the paths and names of all stored documentation.

This server handles Wiki.js page content, including text strings (article bodies) and string paths (page identifiers).

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