appwrite / appwrite/claude-plugin
Remote MCP connector requires separate submission to the MCP Directory
- Lingua principale
- Nessun dato sulla lingua
- Stelle
- 11
- Fork
- 1
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
Hi team — thanks for submitting the Appwrite plugin to the Claude Code plugin directory. The plugin structure is in great shape (`plugin.json`, 11 SDK skills, commands, `user_config` for endpoint/project/API key). One policy item is blocking promotion to the official directory:
## Remote MCP connector requires separate review
`.mcp.json` includes a remote HTTP MCP server:
```json
"appwrite-docs": {
"type": "http",
"url": "https://mcp-for-docs.appwrite.io"
}
```
Remote MCP connectors go through an independent review pipeline before they can ship as part of an official plugin — this is so end users have the same consent experience for remote endpoints regardless of which plugin they arrive from.
### Two options to unblock
**Option A (recommended): submit the docs MCP separately to the MCP Directory.** That review covers the remote endpoint on its own, and once it passes the plugin can ship with both servers intact. The form is at:
> https://claude.ai/mcp-directory-submission
**Option B: ship the plugin without the remote server.** Keep the `appwrite-api` stdio server (and all the skills/commands), drop the `appwrite-docs` entry from `.mcp.json`. The plugin ships immediately; users who want the docs MCP can still add it manually with `claude mcp add` once it's independently reviewed.
The stdio `appwrite-api` server and the skills/commands are completely fine — no changes needed to those.
Let us know which path works best for your team and we'll pick this back up. Happy to clarify anything.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia leggendo .mcp.json e ispeziona la voce HTTP remota di appwrite-docs insieme al server appwrite-api. Scegli tra il MCP Directory submission form all’indirizzo https://claude.ai/mcp-directory-submission o la rimozione della voce remota; l’issue è completata quando il percorso scelto è stato portato a termine e il plugin può procedere con la configurazione del server approvata.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Ambito
- tooling
- Tipo di issue
- Funzionalità
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Tranquilla
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 38/100