Remote MCP connector requires separate submission to the MCP Directory

Start by reading .mcp.json and inspect the appwrite-docs remote HTTP entry alongside the appwrite-api server. Choose either the MCP Directory submission form at https://claude.ai/mcp-directory-submission or removal of the remote entry; the issue is done when the chosen path is completed and the plugin can proceed with its approved server configuration.

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:

"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.