A side-by-side look at the ListingsAPI MCP and Appwrite MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ListingsAPI MCP for developer tools work over a hosted endpoint; choose Appwrite MCP for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
L
Choose ListingsAPI MCP when
You need dedicated capabilities in the Developer Tools domain.
No tool names declared yet. Check the project README from the listing page.
Appwrite MCP 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.
ListingsAPI MCP is categorized under Developer Tools and uses a remote HTTP/SSE transport. Appwrite MCP belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick ListingsAPI MCP for developer tools work and Appwrite MCP 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.
ListingsAPI MCP has no declared pricing — check the project's own site. Appwrite MCP is listed as free. Auth: oauth 2.0. 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 listingsapi-mcp and appwrite-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ListingsAPI MCP has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Appwrite MCP has 76/100 (Great) with 3 views, 0 installs and 72 GitHub stars.