MLflow Prompt Registry MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is MLflow Prompt Registry MCP Server?

MLflow Prompt Registry MCP Server is a server that enables access to prompt templates managed in MLflow, implementing the Model Context Protocol (MCP) for discovering and using these templates.

how to use MLflow Prompt Registry MCP Server?

To use the MCP Server, you need to install MLflow, create prompt templates, build the MCP server, and configure it with Claude Desktop to load and use the prompts.

key features of MLflow Prompt Registry MCP Server?

  • Access to a variety of prompt templates managed in MLflow.
  • Ability to list available prompts and retrieve specific prompts with compiled arguments.
  • Integration with Claude Desktop for streamlined usage of prompts in workflows.

use cases of MLflow Prompt Registry MCP Server?

  1. Loading and using prompt templates for repetitive tasks in Claude Desktop.
  2. Facilitating common workflows by utilizing pre-defined prompts.
  3. Enhancing productivity by automating prompt-based interactions.

FAQ from MLflow Prompt Registry MCP Server?

  • What is the purpose of the MCP Server?

The MCP Server allows users to access and utilize prompt templates from the MLflow Prompt Registry.

  • How do I set up the MCP Server?

Follow the setup instructions to install MLflow, create prompt templates, build the server, and configure it with Claude Desktop.

  • Can I customize the prompts?

Yes! You can create and customize your own prompt templates in MLflow.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
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)

2 days ago