Appwrite MCP vs Uruguay: datos públicos
A side-by-side look at the Appwrite MCP and Uruguay: datos públicos MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
U
Uruguay: datos públicosDeveloper Tools · Local subprocess (stdio)Uruguayan public data from primary sources: BCU rates, CPI, fuel, weather, IDE.uy geocoding, RUT.41FairAuth: no auth requiredVerdict: choose Appwrite MCP for developer tools work over a hosted endpoint; choose Uruguay: datos públicos 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.
UChoose Uruguay: datos públicos when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
MCP_URUGUAY_CACHE.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | U Uruguay: datos públicos | |
|---|---|---|
| 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 | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | MCP_URUGUAY_CACHE |
| 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 Uruguay: datos públicos |
Tools & capabilities
Appwrite MCP tools
No tool names declared yet. Check the project README from the listing page.
Uruguay: datos públicos 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/"
}
}
}
Uruguay: datos públicos
{
"mcpServers": {
"uruguay-datos-p-blicos": {
"command": "uvx",
"args": [
"mcp-uruguay"
],
"env": {
"MCP_URUGUAY_CACHE": "YOUR_MCP_URUGUAY_CACHE_HERE"
}
}
}
}
Frequently asked questions
Appwrite MCP is categorized under Developer Tools and uses a remote HTTP/SSE transport. Uruguay: datos públicos belongs to Developer Tools and uses a local stdio subprocess. Pick Appwrite MCP for developer tools work and Uruguay: datos públicos 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. Uruguay: datos públicos is listed as free. Auth: no auth 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 uruguay-datos-p-blicos 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. Uruguay: datos públicos has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.