Documentation Enhancement: HTTP Dashboard Authentication Clarity
This patch release improves first-time user experience by clarifying HTTP dashboard authentication requirements in README.md, addressing user confusion when encountering 403 errors (Issues #410, #414).
Changed
- Documentation Enhancement (Issue #410, Issue #414, PR #415): Clarified HTTP dashboard authentication requirements in README.md
- Added authentication setup example to Document Ingestion section with
MCP_ALLOW_ANONYMOUS_ACCESS=truefor local development - Added prominent warning callout explaining authentication requirement by default
- Documented all three authentication options in Configuration section:
- Option 1: API Key authentication (
MCP_API_KEY) - recommended for production - Option 2: Anonymous access (
MCP_ALLOW_ANONYMOUS_ACCESS=true) - local development only - Option 3: OAuth team collaboration (
MCP_OAUTH_ENABLED=true)
- Option 1: API Key authentication (
- Improves first-time user experience by clarifying why dashboard returns 403 errors without authentication
- Added authentication setup example to Document Ingestion section with
Fixed
- CHANGELOG Cleanup: Removed duplicate v10.4.3 release entry from Previous Releases section
Upgrade: pip install --upgrade mcp-memory-service
Full Changelog: https://github.com/doobidoo/mcp-memory-service/blob/main/CHANGELOG.md