B0tl1nk vs Appwrite MCP
A side-by-side look at the B0tl1nk and Appwrite MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
B
B0tl1nkDeveloper ToolsSearch and list applications for AI agents. Remote MCP on b0tl1nk.com.37FairAuth: not declaredVerdict: choose B0tl1nk for developer tools work; 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?
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | B B0tl1nk | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 37/100 · Fair | 77/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | — | 73 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View B0tl1nk | View Appwrite MCP |
Tools & capabilities
B0tl1nk tools
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.
B0tl1nk
No confirmed install command for B0tl1nk yet — follow the setup steps linked from its listing page rather than a guessed package name.
Appwrite MCP
{
"mcpServers": {
"appwrite-mcp": {
"url": "https://mcp.appwrite.io/"
}
}
}
Frequently asked questions
B0tl1nk is categorized under Developer Tools and uses an install path we have not confirmed yet. Appwrite MCP belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick B0tl1nk 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. B0tl1nk has no confirmed install command yet — follow its own setup instructions.
B0tl1nk 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 b0tl1nk and appwrite-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, B0tl1nk has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Appwrite MCP has 77/100 (Great) with 4 views, 0 installs and 73 GitHub stars.