magnolia-docs-mcp
Enables AI assistants to search and retrieve information from the official Magnolia CMS documentation through a set of MCP tools.
README
Magnolia CMS Documentation MCP Server (unofficial)
An MCP (Model Context Protocol) server that provides tools to search and retrieve information from the official Magnolia CMS documentation.
Overview
This MCP server allows AI assistants and language models to search the Magnolia CMS documentation directly, making it easier to get accurate and up-to-date information about Magnolia CMS features, configuration, and best practices.
Features
- Documentation Search: Search through the official Magnolia CMS documentation
- Structured Results: Returns formatted search results with titles, URLs, and snippets
- MCP Compatible: Works with any MCP-compatible client or AI assistant
Installation
- Clone or download this repository
- Install dependencies:
npm install
Usage
As a Standalone MCP Server
This server is designed to run as an MCP server using the stdio transport. You can test it directly:
node src/main.js
With MCP-Compatible Clients
To use this server with MCP-compatible clients (like Claude Desktop, Continue, or other AI assistants), you need to configure the client to connect to this server.
Example Configuration for Claude Desktop
Add the following to your MCP configuration file (usually ~/.config/claude-desktop/mcp.json or similar):
{
"mcpServers": {
"magnolia-docs": {
"command": "node",
"args": ["/path/to/your/project/src/main.js"],
"cwd": "/path/to/your/project"
}
}
}
Example Configuration for Other MCP Clients
The server can be configured as a stdio-based MCP server in any compatible client. Refer to your client's documentation for specific configuration instructions.
Available Tools
search_magnolia_docs
Searches the official Magnolia CMS documentation for the given query.
Parameters:
query(string, required): The search term or phrase
Returns:
- An array of search results containing:
title: The title of the documentation pageurl: The URL to the documentation pagesnippet: A brief excerpt from the page
Example Usage:
{
"name": "search_magnolia_docs",
"arguments": {
"query": "content types configuration"
}
}
Project Structure
magnolia-docs-mcp/
├── src/main.js # Main MCP server implementation
├── package.json # Project dependencies and metadata
└── README.md # This file
Dependencies
@modelcontextprotocol/sdk: MCP SDK for building MCP serverscheerio: HTML parsing for extracting search resultsnode-fetch: HTTP client for making requests to the documentation site
Development
Modifying Search Behavior
The search functionality is implemented in the search_magnolia_docs tool handler in main.js. You can modify:
- Search URL construction
- HTML parsing selectors (currently uses
.search-result,.title,.snippet) - Number of results returned (currently limited to 5)
- Result formatting
Adding New Tools
To add new tools:
- Add the tool definition to the
ListToolsRequestSchemahandler - Add the tool implementation to the
CallToolRequestSchemahandler - Update this README with the new tool documentation
Testing
You can test the server by running it directly and sending MCP requests via stdio:
node src/main.js
Then send JSON-RPC requests according to the MCP specification.
Error Handling
The server includes error handling for:
- Network failures when accessing the documentation site
- HTML parsing errors
- Invalid tool requests
Errors are returned as MCP error responses with descriptive messages.
License
MIT
Author
Daniel Naranjo
Contributing
- Fork the repository
- Create a feature branch
- Make your changes
- Test your changes
- Submit a pull request
Troubleshooting
Common Issues
- "Module not found" errors: Make sure you've run
npm installto install dependencies - Connection issues: Verify that the Magnolia CMS documentation site is accessible
- No search results: The HTML selectors might need updating if the documentation site structure changes
Debugging
Enable verbose logging by modifying the error handlers in main.js to include more detailed error information.
Roadmap
- [ ] Add support for different documentation sections
- [ ] Implement caching for better performance
- [ ] Add configuration options for search parameters
- [ ] Support for multiple documentation versions
- [ ] Enhanced result filtering and ranking
Related Resources
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.