The Apache Spark MCP, built by community, provides interact with Apache Spark clusters via the Spark REST API and Livy — submit Spark jobs and queries, query application status and executor metrics, retrieve stage and task-level performance data, access driver logs, manage Spark History Server data, run SparkSQL queries via Livy sessions, monitor shuffle and GC metrics, and retrieve DAG visualization data. It is community-built and best for data.
by community
About
Interact with Apache Spark clusters via the Spark REST API and Livy — submit Spark jobs and queries, query application status and executor metrics, retrieve stage and task-level performance data, access driver logs, manage Spark History Server data, run SparkSQL queries via Livy sessions, monitor shuffle and GC metrics, and retrieve DAG visualization data.
Trust verdict
How grades are computed →Grade A (94/100, reliable) from 1 measured signal, based on repository evidence. Only one signal stands behind it, so treat the grade as provisional.
What was measured
- Repository maintenance100/100 · weight 20
The repository has been pushed to or released within the last six months. — last push 2026-07-16, last release 2026-06-23 (v1.0.0).
- Source verification100/100 · weight 25
The repository URL was confirmed to resolve against the live GitHub API and is not archived.
- Provenance65/100 · weight 10
Community-built. That is not a mark against it — most of the ecosystem is community-built — but there is no vendor accountable for keeping it working.
- Listing ↔ repository match100/100 · weight 5
The listing name lines up with the linked repository kubeflow/mcp-apache-spark-history-server.
What could not be measured
These contributed nothing to the score — not a penalty, not a zero. They are why the confidence reads the way it does.
- Live MCP handshakeunknown
No remote endpoint to handshake — this server installs and runs locally over stdio, so there is nothing to probe from the outside.
- Measured uptimeunknown
No probe history recorded for this server yet.
- Tool-schema stabilityunknown
Drift is a difference between two successive checks, and this server has none recorded.
Installation
uvx --from mcp-apache-spark-history-server spark-mcpmcp-apache-spark-history-server confirmed live on PyPI — checked August 17, 2026.
Categories
Works With
Frequently Asked Questions
What is Apache Spark MCP?
Who built Apache Spark MCP?
Is Apache Spark MCP free?
How do I install Apache Spark MCP?
What does Apache Spark MCP integrate with?
Repo Health
Local/stdio install — runs on your machine, so there is no remote endpoint to verify live. Trust signal below is from the source repo.
- Last commit
- 2mo ago
- Last release
- v1.0.0 · 2mo ago
- Install
- pip
Quick Info
- Install Type
- pip
- Author
- community
- Categories
- 2
- Integrations
- 2
Related Servers
DeepSeek MCP
Integrate DeepSeek API for cost-effective reasoning and code generation — access DeepSeek-V3 and DeepSeek-R1 models for complex problem solving, mathematical reasoning, and code synthesis.
Qwen (Alibaba Cloud) MCP
Access Alibaba Cloud Qwen LLM family via API — long-context processing with Qwen-Long, multimodal with Qwen-VL, and code generation with Qwen-Coder for multilingual AI workflows.
Moonshot AI (Kimi) MCP
Connect to Moonshot AI Kimi API for long-context document analysis up to 200K tokens, Chinese-English bilingual processing, web search-augmented generation, and multimodal understanding.
MCP Jenkins
a Python MCP server for Jenkins (lanbaoshen/mcp-jenkins, published to PyPI as mcp-jenkins) and the alternative to the official Jenkins MCP plugin: where the plugin has to be installed into the controller from the update centre, this one runs beside Jenkins and talks to it over the ordinary REST API, so you can point it at a Jenkins you do not administer. Install it with uvx mcp-jenkins, pip install mcp-jenkins, or the ghcr.io/lanbaoshen/mcp-jenkins container. Credentials go in as --jenkins-url, --jenkins-username and --jenkins-password (an API token works in place of the password), and on the HTTP transport the same three can be supplied per-connection as the x-jenkins-url, x-jenkins-username and x-jenkins-password headers, which is what lets one running instance serve several Jenkins controllers. Three transports are available via --transport: stdio (the default), sse, and streamable-http, which listens on 0.0.0.0:9887 unless --host and --port say otherwise. The tool set is wider than most Jenkins integrations. Jobs and pipelines: get_item, get_item_config, get_item_parameters, get_all_items, query_items for pattern search, and build_item to trigger. Builds: get_build, get_build_console_output, get_build_parameters, get_build_test_report, get_build_scripts, get_running_builds and stop_build, plus get_all_build_artifacts, get_build_artifact and get_build_artifact_url for pulling artifacts out of a finished run. Queue: get_all_queue_items, get_queue_item, cancel_queue_item. Agents: get_all_nodes, get_node, get_node_config. The plugin tools are the part with no equivalent elsewhere — get_all_plugins, get_plugin, get_plugins_with_updates, get_plugins_with_backup, get_plugin_dependency_graph (Graphviz output), and get_plugins_with_problems, which reports missing dependencies and version mismatches and turns a plugin upgrade audit into one question. Two flags matter for safety. run_groovy_script executes arbitrary Groovy on the controller, which is full remote code execution against your CI; --read-only disables it along with every other mutating tool and is the right default for an agent that only needs to read build state. --jenkins-timeout defaults to 5 seconds, which is often too short for a large get_all_items on a busy controller.
TeamCity MCP
Connect to JetBrains TeamCity CI/CD via REST API — trigger build configurations, monitor build queues, inspect test results, manage agents, and query build artifacts for developer workflow automation.
Sponsored
Better Stack
Free PlanGet alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.
Start monitoring free →