Open Source MCP Servers for AWS for Cursor: Setup & Config

What you can do with Open Source MCP Servers for AWS in Cursor

Choose task-specific AWS context and workflow integrations from a broad open-source server collection.

• Add AWS data and analytics context to an AI application.
• Explore cloud development automation through MCP-compatible clients.

Before you start: Open Source MCP Servers for AWS in Cursor

• An MCP-compatible client
• uvx for the documentation-server example

This is the AWS Documentation MCP Server configuration encoded in the README's installation link, not a command for the entire suite. The linked example uses ERROR logging and the aws documentation partition. Configure other servers separately; individual tool identifiers are not stated in the supplied excerpt.

Open Source MCP Servers for AWS Cursor configuration

1. Choose Cursor configuration scope

   For Open Source MCP Servers for AWS, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

2. Add Open Source MCP Servers for AWS to Cursor

   Use the mcp entry below in mcpServers. Keep Open Source MCP Servers for AWS's documented stdio connection fields and your other Cursor entries.

3. Check Open Source MCP Servers for AWS in Cursor

   Open Source MCP Servers for AWS: Enable in Cursor’s MCP settings; inspect tools.

{
  "mcpServers": {
    "mcp": {
      "command": "uvx",
      "args": [
        "awslabs.aws-documentation-mcp-server@latest"
      ],
      "env": {
        "FASTMCP_LOG_LEVEL": "<desired logging level>",
        "AWS_DOCUMENTATION_PARTITION": "<AWS documentation partition>"
      }
    }
  }
}

Troubleshooting Open Source MCP Servers for AWS in Cursor

• Cursor must find uvx awslabs.aws-documentation-mcp-server@latest (from uv, for Python tools) for Open Source MCP Servers for AWS. Enable the project/user entry in MCP settings and inspect its tools.
• Review AWS_DOCUMENTATION_PARTITION, FASTMCP_LOG_LEVEL for Open Source MCP Servers for AWS before sharing project .cursor/mcp.json; project scope travels with the repository.
• Open Source MCP Servers for AWS uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: The repository describes local servers as stdio-only and removed SSE from current major versions.
• Known limitation: Production agent builders are directed toward the newer Agent Toolkit for AWS.
• Known limitation: A single universal tool catalog and launch command are not provided in the supplied excerpt.
• General Cursor troubleshooting lives in the /clients/cursor guide.

Frequently asked questions