miniflux

This Miniflux MCP Server exposes a collection of MCP tools that map to the Miniflux API, enabling you to manage feeds, entries, users, categories, and more through the MCP protocol. The server supports operation via Docker as demonstrated in the setup, and exposes a rich set of tools categorized under Feed Management, Entry Management, Category Management, User Management, System & Utility, API Key Management, and Icons & Media. You can authenticate using either an API key or a username/password combination, depending on your Miniflux configuration. Use the tools to list resources, create or update entities, refresh feeds, and fetch content programmatically, integrating these capabilities into your own clients or automation scripts.

Prerequisites:

• Docker installed on your host (Docker Desktop for Windows/macOS or Docker Engine on Linux).
• Access to a Miniflux instance and ability to generate an API key or set up username/password.

Installation steps:

1. Create a .env file (optional) or prepare environment variables for Miniflux URL and credentials.

2. Run the MCP server via Docker using the configuration in this repository:

   • Build and run (as shown in the README example): docker build -t miniflux-mcp . docker run --env-file .env miniflux-mcp

   • Or use the prebuilt image directly (as configured in mcp_config): docker run -i --rm -e MINIFLUX_URL="https://your-miniflux-instance.com" -e MINIFLUX_API_KEY="your_api_key_here" jwonder/miniflux-mcp:latest

3. Verify connectivity by querying the MCP tools endpoint (the exact commands depend on how you expose the MCP interface in your environment).

4. Adjust environment variables as needed for your deployment (URL, credentials).

Notes:

• If you prefer API key authentication, provide MINIFLUX_API_KEY. If you prefer basic auth, provide MINIFLUX_USERNAME and MINIFLUX_PASSWORD.
• Ensure network access between the MCP container and your Miniflux instance (consider network policies, firewalls, and TLS).

Tips and common issues:

• Ensure MINIFLUX_URL is reachable from the container network; use a fully qualified URL with https when possible.
• If you encounter authentication errors, double-check that you are using either API key or a valid username/password combination as required by your Miniflux setup.
• When using Claude Desktop or other MCP clients, you can pass environment variables via an env block in the config and reference those vars in the container run command.
• The MCP server exposes a large suite of tools (40+). Start with core feed and entry tools (e.g., get_feeds, create_feed, get_entries, update_entry_status) to validate connectivity before expanding to category, user, and system tools.
• Monitor Miniflux API rate limits, and consider enabling retries in your client integration.