miniflux-mcp-server
by rokoucha
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port. | 3000 |
| ISSUER | Yes | Public MCP origin. Must use HTTPS in production. | |
| NODE_ENV | No | Set to production for production deployment. | |
| MINIFLUX_URL | Yes | Miniflux HTTP(S) origin, without /v1. | |
| DATABASE_PATH | No | SQLite database path for replay prevention. In containers, typically /data/oauth.sqlite. | ./oauth.sqlite |
| MAX_RESPONSE_BYTES | No | Maximum upstream response size in bytes. Default is 4 MiB. | 4194304 |
| OAUTH_CLIENTS_JSON | No | Optional pre-registered OAuth clients as JSON. The same callback restrictions apply. | [] |
| UPSTREAM_TIMEOUT_MS | No | Upstream HTTP timeout in milliseconds. | 15000 |
| JWE_KEYS_ACCESS_TOKEN | Yes | Encryption key for access tokens, in k1:<base64url> format. | |
| JWE_KEYS_REFRESH_TOKEN | Yes | Encryption key for refresh tokens and dynamic client registration, in k1:<base64url> format. | |
| JWE_KEYS_AUTHORIZE_REQUEST | Yes | Encryption key for authorization requests, in k1:<base64url> format. | |
| JWE_KEYS_AUTHORIZATION_CODE | Yes | Encryption key for authorization codes, in k1:<base64url> format. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues