Appwrite MCP vs Developer API
A side-by-side look at the Appwrite MCP and Developer API MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
D
Developer APIDeveloper ToolsManage your Servera hosting over MCP: VPS/VDS, DNS, firewall, backups, SSL, billing, tickets.37FairAuth: not declaredVerdict: choose Appwrite MCP for developer tools work over a hosted endpoint; choose Developer API for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Appwrite MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
DChoose Developer API when
- You need dedicated capabilities in the Developer Tools domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | D Developer API | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 76/100 · Great | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 73 | — |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Appwrite MCP | View Developer API |
Tools & capabilities
Appwrite MCP tools
No tool names declared yet. Check the project README from the listing page.
Developer API tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Appwrite MCP
{
"mcpServers": {
"appwrite-mcp": {
"url": "https://mcp.appwrite.io/"
}
}
}
Developer API
No confirmed install command for Developer API yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Appwrite MCP is categorized under Developer Tools and uses a remote HTTP/SSE transport. Developer API belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Appwrite MCP for developer tools work and Developer API for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Developer API has no confirmed install command yet — follow its own setup instructions.
Appwrite MCP is listed as free. Auth: oauth 2.0. Developer API has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add appwrite-mcp and developer-api-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Appwrite MCP has a quality signal of 76/100 (Great) with 3 views, 0 installs and 73 GitHub stars. Developer API has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.