MCP server implementation for Qexo CMS
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"qexo-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Qexo MCP Server An MCP (Machine Communication Protocol) server implementation for interacting with Qexo CMS, allowing seamless integration with Qexo's content management capabilities. ## Overview Qexo MCP Server provides a bridge between MCP clients and the Qexo CMS API, enabling programmatic management of content through a standardized interface. This server implementation simplifies the process of working with Qexo CMS by providing a set of well-defined tools for common operations. ## Features - **Content Management**: Create, read, update, and delete blog posts and files - **Post Management**: Save and manage draft posts - **Search Capability**: Search through existing posts - **Metadata Handling**: Manage categories and tags for posts - **Full Integration**: Complete integration with the Qexo API - **Commit Messages**: Support for custom commit messages when saving changes ## Installation ### Using pip ```bash pip install qexo-mcp ``` ### From Source 1. Clone the repository: ```bash git clone https://github.com/yuzhi-jiang/mcp-servers.git cd mcp-servers/qexo-mcp ``` 2. Install the package: ```bash pip install -e . ``` ## Configuration Qexo MCP Server requires API credentials to connect to your Qexo instance. You can provide these through environment variables: 1. Create a `.env` file in your project directory: ``` api_url=https://your-qexo-instance.com api_token=your-api-token ``` 2. Alternatively, set the environment variables directly: ```bash # Linux/macOS export api_url=https://your-qexo-instance.com export api_token=your-api-token # Windows set api_url=https://your-qexo-instance.com set api_token=your-api-token ``` ## Running the Server ```bash qexo-mcp ``` This will start the MCP server, which will listen for incoming requests. ## Available Tools ### Post Management - `get_posts(s: str = None) -> List[dict]` - Get all posts, optionally filtered by search string - Parameters: - `s`: Optional search string - `save_or_update_…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.