AWS Data Processing vs Databricks
AWS Data Processing is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Databricks is an MCP server published by mcp-dir. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  AWS Data Processing |  Databricks |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:8dc85c2f47b4 Forks (GitHub): 1 806 Pulls (Docker Hub): 31 057 Stars (Docker Hub): 0 Stars (GitHub): 9 779 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | AWS Data Processing | Databricks |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 779 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 31 057 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 806 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-dataprocessing-mcp-server) | Remote server (api.mcp.ai/p_databricks) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 32 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/mcp-dir/databricks-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
AWS Data Processing
Data processing and transformation services.
Databricks
Your Databricks Lakehouse in natural language: run SQL on your SQL warehouses, track long-running qu
How to run each
AWS Data Processing As a local MCP server: Docker image
claude mcp add --transport stdio aws-dataprocessing -- docker run -i --rm mcp/aws-dataprocessing-mcp-serverDatabricks As a remote MCP server
claude mcp add --transport http databricks-mcp https://api.mcp.ai/p_databricksCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Databricks publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Databricks publish no settings it asks for, so we do not compare settings.
What it can do: AWS Data Processing · What it can do: Databricks · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.