MCP server for Apache Livy on Amazon EMR with per-request credential refresh
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"emr-livy-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# EMR Livy MCP Server A Model Context Protocol (MCP) server for interacting with Apache Livy on Amazon EMR, with automatic credential refresh. --- ## Overview This MCP server exposes tools for: - Getting temporary EMR session credentials - Managing Livy sessions (create / get / delete) - Submitting and polling PySpark statements - Running end-to-end queries with auto credential refresh --- ## Configuration ### Environment variables | Variable | Required | Description | |----------|----------|-------------| | `EMR_CLUSTER_ID` | Yes | EMR cluster id (e.g. `j-...`) | | `EMR_ROLE_ARN` | Yes | Execution role ARN passed to `get-cluster-session-credentials` | | `LIVY_URL` | Yes | Livy base URL (no trailing slash), e.g. `https://livy.example.com` | | `EMR_REGION` | No | AWS region for the EMR API (default: `us-west-2`) | | `EMR_AK` / `EMR_SK` | No | Optional override; if unset, keys come from the usual AWS env vars / shared credentials / profile / instance role (boto3 default chain) | | `EMR_AWS_ACCESS_KEY_ID` / `EMR_AWS_SECRET_ACCESS_KEY` | No | Same as above with explicit names | | `AWS_ACCESS_KEY_ID` / `AWS_SECRET_ACCESS_KEY` | No | Standard AWS SDK variables (used when `EMR_AK` / `EMR_SK` are not set) | | `EMR_AWS_SESSION_TOKEN` or `AWS_SESSION_TOKEN` | No | Optional session token for temporary keys | ```bash export EMR_CLUSTER_ID="j-xx" export EMR_ROLE_ARN="arn:aws:iam::<account-id>:role/<role_name>" export LIVY_URL="https://livy.example.com" # Optional — overrides default us-west-2: # export EMR_REGION="us-west-2" # Optional — otherwise use AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY (or profile, SSO, etc.): # export EMR_AK="AKIA..." # export EMR_SK="..." ``` ### Run with `uvx` (recommended for users) Same idea as `uvx opensearch-mcp-server-py`: **no clone, no `pip install`, no `--from`**. `uvx` downloads **`emr-livy-mcp`** from PyPI (or your default / `UV_INDEX` mirror) into an isolated tool env and runs the `emr-livy-mcp` console script. **Requirement:** …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.