Cloudera AI MCP

Created By
Adrien Chenaillera year ago
Interact with cloudera AI api to manage job, apps, models
Overview

What is Cloudera AI MCP?

Cloudera AI MCP (Model Control Protocol) is a Python-based integration tool that allows users to interact programmatically with Cloudera Machine Learning (CML) services for managing jobs, applications, and machine learning models.

How to use Cloudera AI MCP?

To use Cloudera AI MCP, clone the repository, install the required dependencies, configure your CML instance URL and API key, and run the server. You can also use it directly in your Python code or via command-line testing.

Key features of Cloudera AI MCP?

  • Upload entire folders to CML projects while preserving directory structure.
  • Create, list, and delete jobs in your CML project.
  • Manage ML models and deployments.
  • Track and log ML experiments and runs.
  • Create and manage CML applications.

Use cases of Cloudera AI MCP?

  1. Automating the management of machine learning jobs in CML.
  2. Facilitating the deployment of ML models in production environments.
  3. Streamlining the process of tracking experiments and results in machine learning projects.

FAQ from Cloudera AI MCP?

  • What programming language is Cloudera AI MCP written in?

    Cloudera AI MCP is written in Python.

  • Is there a graphical user interface for Cloudera AI MCP?

    No, Cloudera AI MCP is designed for programmatic access and does not include a GUI.

  • What are the system requirements?

    Cloudera AI MCP requires Python 3.8 or higher and several Python packages as specified in the requirements.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Adrien Chenailler
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago