appwrite-api error after install
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- Ein halber Tag
- Anfängerfreundlichkeit
- 50/100
- Issue-Typ
- Bug
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- python
- Bereich
- developer-experience
Rechercherichtung
The log shows mcp-server-appwrite exiting with unrecognized arguments: --users, and its usage line lists only --transport, --host, --port and --console-url. The payload does not show where --users is passed, so start by searching this repository's plugin and MCP server configuration for that flag and for the appwrite-api entry. Remove the flag or align it with what the server accepts, then confirm the server starts without the error. Done when the appwrite-api connection reaches a connected state in the log.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
👟 Reproduction steps
- Install the appwrite plugin through the cursor marketplace
- Go to the cursor desktop app on Mac OS
- See the plugin log for appwrite-api
- See error
👍 Expected behavior
Let me authenticate with my appwrite account
👎 Actual Behavior
Gives this error log:
2026-10-07 18:17:59.360 [info] [Shared MCP process] connecting stdio for "appwrite-api" (plugin-appwrite-plugin-appwrite-api)
2026-10-07 18:17:59.360 [info] [Shared MCP process] [V2 FSM] connection:connect_start: conn=idle,auth=unknown -> conn=connecting,auth=unknown
2026-10-07 18:17:59.360 [info] [Shared MCP process] MCP stdio spawn policy decision: sandboxed=false, sandboxReason=controls_disabled, networkControlsEnabled=false, mcpNetworkMode=unset, mcpNetworkAllowlistCount=0, mcpNetworkDenylistCount=0, localAgentNetworkAllowlistCount=0, sandboxPolicyHash=dbad6ab7a53b8aaa3269e0c907d30e5e1483298ffc76de0456eeb31b7d11df5e
2026-10-07 18:17:59.375 [info] [MCPService] [MCPService] createClient: identifier="plugin-appwrite-plugin-appwrite-api", serverName="appwrite-api"
2026-10-07 18:17:59.375 [info] [MCPService] [MCPService] createClient completed for server: plugin-appwrite-plugin-appwrite-api, statusType=initializing, success=true
2026-10-07 18:18:00.156 [error] [Shared MCP process] Downloading openai (2.1MiB)
undefined
2026-10-07 18:18:00.188 [error] [Shared MCP process] Downloading mcp-server-appwrite (31.2MiB)
undefined
2026-10-07 18:18:00.310 [error] [Shared MCP process] Downloaded openai
undefined
2026-10-07 18:18:01.308 [error] [Shared MCP process] Downloaded mcp-server-appwrite
undefined
2026-10-07 18:18:01.421 [error] [Shared MCP process] Installed 64 packages in 112ms
undefined
2026-10-07 18:18:03.960 [error] [Shared MCP process] usage: mcp-server-appwrite [-h] [--transport TRANSPORT] [--host HOST]
[--port PORT] [--console-url CONSOLE_URL]
mcp-server-appwrite: error: unrecognized arguments: --users
undefined
2026-10-07 18:18:04.049 [warning] [Shared MCP process] Connection failed: MCP error -32000: Connection closed
2026-10-07 18:18:04.049 [warning] [Shared MCP process] [V2 FSM] connection:connect_failure: conn=connecting,auth=unknown -> conn=failed,auth=unknown
🎲 Appwrite version
Appwrite Cloud
💻 Operating system
MacOS
🧱 Your Environment
No response
👀 Have you spent some time to check if this issue has been raised before?
- I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
- I have read the Code of Conduct
- Vorherrschende Sprache
- Keine Sprachdaten
- Sterne
- 19
- Forks
- 4
- Ø Merge
- 8 Std. 32 Min.
- Gemergte PRs (30 T.)
- 2
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus appwrite/cursor-plugin
-
Schwierigkeit 3/5 Ein halber Tag Anfängerfreundlichkeit 50/100
appwrite/cursor-plugin#10 ·
Alle Issues in appwrite/cursor-plugin
Ähnliche Issues
-
[doc-healer] DDUw improvement: retry integrity-filtered issue reads with direct single-item lookupsOffenautomation documentation
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
diegosouzapw/OmniRoute#18387 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
davidjerleke/embla-carousel#1414 ·
Maintainer antworten meist innerhalb von 4 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 77/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 77/100
Maintainer antworten meist innerhalb von 1 Tag