This repository demonstrates how to set up and use MCP (Model Context Protocol) servers within Cursor. MCP allows you to define custom tools that the
Most cloud and infrastructure work still happens through a UI a human drives. MCP 104 Cursor MCP server moves it into the conversation instead. This repository demonstrates how to set up and use MCP (Model Context Protocol) servers within Cursor. MCP allows you to define custom tools that the AI assistant can use to perform actions, such as fetching data from an API or running a.
The server publishes 1 tool. What each one is for:
Servers — 1. docker-server_2: This server runs a Docker container named mcp-weather-server from the mcp-weather-server:latest image. It's used to get weatherSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: DEBUG. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP 104 Cursor's toolset — Servers — is a fair guide to whether it matches your workflow. It is maintained by mitchallen; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Servers | 1. docker-server_2: This server runs a Docker container named mcp-weather-server from the mcp-weather-server:latest image. It's used to get weather information. 2. time-server_2: This server runs a Docker container from |
{
"mcpServers": {
"docker-server_2": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--name",
"mcp-weather-server",
"mcp-weather-server:latest"
],
"env": {
"DEBUG": "mcp:*"
}
},
"time-server_2": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"mcp/time"
],
"env": {
"DEBUG": "mcp:*"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DEBUG | Configuration value read at startup. | Optional |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.