| name | xwiki-mcp-connector |
| description | MCP connector for XWiki – enables AI-powered wiki management, space organization, and collaborative documentation through Claude |
| license | LGPL |
| tags | ["dev","wiki","mcp","xwiki","documentation"] |
| difficulty | intermediate |
| time_to_master | 4-8 weeks |
| version | 1.0.0 |
Xwiki MCP Connector
Overview
This skill enables Claude to interact with Xwiki through the Model Context Protocol (MCP). It provides a bridge between Claude's AI capabilities and Xwiki's REST API, allowing natural language control of Xwiki operations, intelligent automation, and AI-powered assistance for Xwiki workflows.
When to Use This Skill
- Page and space creation via natural language
- XWiki scripting and macro development
- Application creation with App Within Minutes
- User and group management
- Extension installation and configuration
Architecture
┌─────────────┐ ┌─────────────────┐ ┌──────────────────┐
│ Claude │────▶│ MCP Server │────▶│ Xwiki │
│ (Client) │◀────│ (TypeScript) │◀────│ (REST API )│
└─────────────┘ └─────────────────┘ └──────────────────┘
Core Concepts
MCP Server Setup
The connector implements an MCP server that exposes Xwiki operations as tools Claude can invoke. The server translates natural language intentions into REST API calls.
Key Endpoints/Interfaces
/rest/wikis/:wiki/spaces, /rest/wikis/:wiki/pages, /rest/wikis/:wiki/search, /rest/wikis/:wiki/classes
Implementation
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";
const server = new McpServer({
name: "xwiki-mcp-connector",
version: "1.0.0",
});
server.tool(
"list_resources",
"List and query Xwiki resources with optional filters",
{
query: z.string().optional().describe("Search query or filter"),
limit: z.number().optional().describe("Max results to return"),
},
async ({ query, limit }) => {
const response = await fetch(`${BASE_URL}/rest/wikis/:wiki/spaces`, {
headers: { "Authorization": `Bearer ${API_KEY}` },
});
const data = await response.json();
return {
: [{ : , : .(data, , ) }],
};
}
);
server.(
,
,
{
: z.().(),
: z.({}).().().(),
},
({ name, config }) => {
response = (, {
: ,
: {
: ,
: ,
},
: .({ name, ...config }),
});
data = response.();
{
: [{ : , : }],
};
}
);
server.(
,
,
{
: z.().(),
: z.().().(),
},
({ , timeframe }) => {
response = (, {
: { : },
});
data = response.();
{
: [{ : , : .(data, , ) }],
};
}
);
transport = ();
server.(transport);
Claude Desktop Configuration
{
"mcpServers": {
"xwiki-mcp-connector": {
"command": "node",
"args": ["path/to/xwiki-mcp-connector/index.js"],
"env": {
"XWIKI_API_KEY": "your-api-key",
"XWIKI_BASE_URL": "https://your-instance-url"
}
}
}
}
Best Practices
- Authentication: Store API keys securely using environment variables; never hardcode credentials
- Rate Limiting: Implement request throttling to respect Xwiki API rate limits
- Error Handling: Provide clear, actionable error messages for common failure scenarios
- Pagination: Handle paginated responses for large datasets efficiently
- Caching: Cache frequently accessed read-only data to reduce API calls
- Security: Validate all inputs before passing to the Xwiki API; sanitize outputs
- Logging: Log all API interactions for debugging and audit purposes
Example Prompts
"Create a structured space for the engineering handbook with templates for RFCs, ADRs, and runbooks"
Security Considerations
- All API credentials must be stored as environment variables
- Implement input validation and sanitization for all tool parameters
- Use HTTPS for all API communications
- Follow the principle of least privilege for API token permissions
- Audit log all write operations for compliance tracking
Resources
Changelog
| Version | Date | Changes |
|---|
| 1.0.0 | 2026-04-01 | Initial MCP connector skill |
Part of SkillGalaxy - 10,000+ comprehensive skills for AI-assisted development.
