Reported issues for nextcloud-organizer-mcp
Pod holds 8 of 8 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.
Back to nextcloud-organizer-mcp.
Most discussed
Add native stdio transport for local clients
Follow-up to #72 (parent: #65). #72 evaluated a native stdio transport and decided it is worth implementing. The evaluation is recorded in docs/deployment.md under "Native stdio transport".
Why
Same-machine clients (Claude Desktop, Claude Code, MCP Inspector) currently need the HTTP server, OAuth, PUBLIC_BASE_URL, an OAuth state directory and, for Claude Desktop, Node.js plus the mcp-remote bridge. With stdio the client starts the server as a child process and none of that is needed.…
Read the thread · 2026-09-30 · closed · 1 comment
Test and document local HTTP use and evaluate stdio transport
Parent: #65
Provide a short setup for clients running on the same machine without a public URL.
Scope:
- Document PUBLIC_BASE_URL=http://127.0.0.1:8000 with a loopback MCP_HOST and the local /mcp endpoint.
- Explain that omitting MCP_OAUTH_PASSWORD is permitted only when both public URL and bind address are local; it does not remove the OAuth protocol.
- Verify an actual local client connection path, including any bridge, browser flow, and redirect-domain configuration needed.
- Explain why a…
Read the thread · 2026-09-30 · closed · 1 comment
Ship a Docker image
Motivation
Today the only documented install is uv tool install plus a hand-written systemd unit (see docs/deployment.md). Most self-hosters run their services in containers, so a container image is the lowest-friction way to try and run the server.
Goal
A user with Docker and a Nextcloud instance can get the server running with one documented command or one compose file, without installing Python or uv.
Notes for whoever picks this up
The scope and shape…
Read the thread · 2026-09-29 · closed · 1 comment
Add deployment diagnostics for public URL and OAuth discovery
Parent: #65
Help operators diagnose setup failures with actionable output.
Proposed interface: nextcloud-organizer-mcp doctor --url https://organizer.example.com (final CLI shape may follow existing conventions).
Scope:
- Check DNS/reachability, TLS, OAuth discovery metadata, and consistency of advertised endpoint/resource URLs with the requested deployment.
- Detect likely localhost URLs in public metadata, routing errors, HTML challenge/login pages, and missing expected authentication…
Read the thread · 2026-09-30 · open · 0 comments
Investigate OAuth-safe subpath deployment and document support boundaries
Parent: #65
Determine whether MCP can run under a prefix such as https://cloud.example.com/organizer alongside Nextcloud.
Known starting point: personal_auth.py currently renders a consent form with action="/consent", which escapes a deployment prefix. Changing only the proxy rewrite is therefore insufficient.
Scope:
- Trace prefix handling through PUBLIC_BASE_URL, MCP routing, OAuth discovery, registration, authorization, token endpoints, consent redirects, and consent form submission. -…
Read the thread · 2026-09-30 · open · 0 comments
Document and support deployments without Tailscale
Motivation
The deployment guide only covers Tailscale Funnel for the public HTTPS URL that Claude needs. Many people cannot or do not want to use Tailscale, and that is likely the biggest barrier to adoption.
Goal
Working, tested setup instructions (and code changes where needed) for the common alternatives, so a user can pick the one that matches their environment. Add them to docs/deployment.md as alternatives to step 4, and link them from the README.
Setups…
Read the thread · 2026-09-29 · open · 0 comments
403 responses (e.g. 'Calendar limit reached') are reported as 'Nextcloud rejected the CalDAV credentials'
Problem
When the Nextcloud server refuses create_task_list / create_calendar with 403 Forbidden — in my case Sabre\DAV\Exception\Forbidden: Calendar limit reached — the MCP tool reports:
AuthenticationFailedError: Nextcloud rejected the CalDAV credentials (check username/app password).
That message sends the user (and any LLM driving the tools) hunting for a credentials problem that doesn't exist. Read operations work fine with the same credentials.
Cause…
Read the thread · 2026-07-15 · closed · 0 comments
list_trash (PR #10) fails against real Nextcloud: PROPFIND Depth 1 on trashbin/objects/ returns HTTP 501
Problem
list_trash from PR #10 (branch feature/trash-bin) always fails against a real Nextcloud instance:
TaskMcpError: Nextcloud returned an unexpected error listing the trash bin (HTTP 501).
Tested live on Nextcloud (alpine-nextcloud, 2026-07-15) with a trash bin that verifiably contained items.
Cause
CalDavService.list_trash() sends PROPFIND with Depth: 1 to calendars/<user>/trashbin/objects/. Nextcloud's DeletedCalendarObjectsCollection does not support…
Read the thread · 2026-07-15 · closed · 0 comments
Most recent
The remaining reports are on the project's issue tracker.