zeppelin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SOCKS5_PROXY | No | SOCKS5 proxy address for tunneled access (optional) | |
| ZEPPELIN_URL | Yes | Base URL of the Zeppelin instance (required) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zeppelin_loginA | Authenticate with Apache Zeppelin using username and password. Must be called before any other tools. Stores session cookie for subsequent requests. |
| list_notebooksA | List notebooks in Zeppelin. Use the query parameter to filter by path (case-insensitive substring match). Without a query, returns all notebooks (can be very large). |
| get_notebookA | Get a notebook's structure: paragraph IDs, status, and first line of text. Use get_paragraph for full content of a specific paragraph. |
| create_notebookB | Create a new notebook at the given path. Path uses '/' as folder separator (e.g. 'folder/notebook_name'). |
| delete_notebookB | Delete a notebook by ID. This action is irreversible. |
| get_paragraphB | Read a single paragraph's text and output from a notebook. |
| update_paragraphB | Update a paragraph's text. Use this to write or modify code in a paragraph. |
| create_paragraphB | Add a new paragraph to a notebook. Optionally specify text and position index. |
| delete_paragraphC | Remove a paragraph from a notebook. |
| run_paragraphA | Execute a single paragraph and return its output. This is a synchronous call that waits for execution to complete. |
| stop_paragraphB | Cancel a running paragraph. |
| run_all_paragraphsC | Execute all paragraphs in a notebook sequentially. |
| stop_all_paragraphsB | Cancel all running paragraphs in a notebook. |
| restart_interpreterA | Restart a Zeppelin interpreter by setting name (e.g. 'spark', 'python', 'sh', 'md'). Optionally scope to a specific notebook. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool has a clearly distinct purpose: notebook lifecycle, paragraph lifecycle, execution control, interpreter restart, and authentication. Descriptions clarify boundaries (e.g., get_notebook vs get_paragraph). No overlap or ambiguity.
All tools follow a consistent verb_noun pattern with underscores (e.g., create_notebook, delete_paragraph, run_all_paragraphs). The only slight deviation is zeppelin_login, but it still fits the pattern of action_resource. Naming is uniform and predictable.
14 tools provide a well-scoped surface for managing Zeppelin notebooks. It covers CRUD for notebooks and paragraphs, execution commands, interpreter restart, and authentication—neither too sparse nor excessive for the domain.
The toolset covers core notebook and paragraph operations, execution, and interpreter management. Minor gaps include no logout, no interpreter listing, and no notebook import/export, but the set is sufficient for typical agent interactions with Zeppelin.