Log inSubmit server

DealFilter vs Awslabs MCP

A side-by-side look at the DealFilter and Awslabs MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

D
DealFilterCloud PlatformsAI deal pipeline for IT freelancers in DACH: analyze, list and manage project inquiries.37FairAuth: not declaredAwslabs MCP logoAwslabs MCPCloud Platforms · Local subprocess (stdio)AWS MCP servers for seamless integration with AWS services and resources.48FairAuth: api key required

Verdict: choose DealFilter for cloud platforms work; choose Awslabs MCP for cloud platforms as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

D
Choose DealFilter when

  • You need dedicated capabilities in the Cloud Platforms domain.
Explore DealFilter

Awslabs MCP logoChoose Awslabs MCP when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
Explore Awslabs MCP

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
D
DealFilter		Awslabs MCP logoAwslabs MCP
CategoryCloud PlatformsCloud Platforms
Quality signal37/100 · Fair48/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—9,821
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView DealFilter View Awslabs MCP

Tools & capabilities

DealFilter tools

No tool names declared yet. Check the project README from the listing page.

Awslabs 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.

DealFilter

No confirmed install command for DealFilter yet — follow the setup steps linked from its listing page rather than a guessed package name.

Awslabs MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "awslabs-mcp": {
      "command": "uvx",
      "args": [
        "awslabs.aws-api-mcp-server@latest"
      ]
    }
  }
}

Frequently asked questions

DealFilter is categorized under Cloud Platforms and uses an install path we have not confirmed yet. Awslabs MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick DealFilter for cloud platforms work and Awslabs MCP for cloud platforms.

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. DealFilter has no confirmed install command yet — follow its own setup instructions.

DealFilter has no declared pricing — check the project's own site. Awslabs MCP is listed as free. 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 dealfilter and awslabs-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, DealFilter has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Awslabs MCP has 48/100 (Fair) with 2 views, 0 installs and 9,821 GitHub stars.

Popular comparisons with DealFilter

Popular comparisons with Awslabs MCP