Appwrite MCP vs Rigshare
A side-by-side look at the Appwrite MCP and Rigshare MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
R
RigshareDeveloper Tools · Local subprocess (stdio)Rent GPUs, robots, drones, and construction gear on RIGShare; also onboards equipment owners.41FairAuth: api key requiredVerdict: choose Appwrite MCP for developer tools work over a hosted endpoint; choose Rigshare for developer tools as a local process. 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.
RChoose Rigshare when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
RIGSHARE_API_KEY, RIGSHARE_BASE, RIGSHARE_API_BASE, RIGSHARE_AGENT_API_BASE, RIGSHARE_V1_API_BASE.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | R Rigshare | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 76/100 · Great | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | API key required |
| Pricing | Free | Not declared |
| Required env vars | None listed | RIGSHARE_API_KEYRIGSHARE_BASERIGSHARE_API_BASERIGSHARE_AGENT_API_BASERIGSHARE_V1_API_BASE |
| Verified owner | Verified | Community listing |
| GitHub stars | 72 | 0 |
| 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 Rigshare |
Tools & capabilities
Appwrite MCP tools
No tool names declared yet. Check the project README from the listing page.
Rigshare 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/"
}
}
}
Rigshare
{
"mcpServers": {
"rigshare-3": {
"command": "npx",
"args": [
"-y",
"rigshare-mcp"
],
"env": {
"RIGSHARE_API_KEY": "YOUR_RIGSHARE_API_KEY_HERE",
"RIGSHARE_BASE": "YOUR_RIGSHARE_BASE_HERE",
"RIGSHARE_API_BASE": "YOUR_RIGSHARE_API_BASE_HERE",
"RIGSHARE_AGENT_API_BASE": "YOUR_RIGSHARE_AGENT_API_BASE_HERE",
"RIGSHARE_V1_API_BASE": "YOUR_RIGSHARE_V1_API_BASE_HERE"
}
}
}
}
Frequently asked questions
Appwrite MCP is categorized under Developer Tools and uses a remote HTTP/SSE transport. Rigshare belongs to Developer Tools and uses a local stdio subprocess. Pick Appwrite MCP for developer tools work and Rigshare 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.
Appwrite MCP is listed as free. Auth: oauth 2.0. Rigshare has no declared pricing — check the project's own site. Auth: api key required. 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 rigshare-3 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 72 GitHub stars. Rigshare has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.