Appwrite MCP vs Auxen
A side-by-side look at the Appwrite MCP and Auxen MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Appwrite MCP for developer tools work over a hosted endpoint; choose Auxen for conversational ai over a hosted endpoint. 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.
Choose Auxen when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
auxen_list_models, auxen_get_instance_status, auxen_list_instances.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Conversational AI |
| Quality signal | 77/100 · Great | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | 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 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 6 |
| Full listing | View Appwrite MCP | View Auxen |
Tools & capabilities
Appwrite MCP tools
No tool names declared yet. Check the project README from the listing page.
Auxen tools 6
auxen_list_modelsread-onlyauxen_get_instance_statusread-onlyauxen_list_instancesread-onlyauxen_get_balanceread-onlyauxen_provision_modeldestructiveauxen_destroy_instancedestructive
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/"
}
}
}
Auxen
{
"mcpServers": {
"auxen": {
"url": "https://api.auxen.ai/mcp"
}
}
}
Frequently asked questions
Appwrite MCP is categorized under Developer Tools and uses a remote HTTP/SSE transport. Auxen belongs to Conversational AI and uses a remote HTTP/SSE transport. Pick Appwrite MCP for developer tools work and Auxen for conversational ai.
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.
Appwrite MCP is listed as free. Auth: oauth 2.0. Auxen 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 auxen 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 77/100 (Great) with 4 views, 0 installs and 73 GitHub stars. Auxen has 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.