Facilitates model control by integrating OpenAI services, Git repository analysis, filesystem operations, and Prometheus monitoring.
Facilitates model control by integrating OpenAI services, Git repository analysis, filesystem operations, and Prometheus monitoring. That is what the model control plane mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
This repository contains a Model Control Plane (MCP) server implementation that supports OpenAI services, Git repository analysis, local filesystem operations, and Prometheus integration.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
The server publishes 2 tools. What each one is for:
Setup — This will start: - Prometheus server (accessible at http://localhost:9090) - Node Exporter (for host metrics) - cAdvisor (for container metrics)Troubleshooting — If you encounter permission issues: 1. Use the reset scripts to rebuild the containers 2. Check the logs with docker compose logs <service_name> 3Configuration is passed through the environment: AZURE_OPENAI_ENDPOINT, AZURE_OPENAI_API_KEY, AZURE_OPENAI_API_VERSION, AZURE_DEPLOYMENT_NAME, OPENAI_API_KEY, OPENAI_CHAT_MODEL, OPENAI_COMPLETION_MODEL, PROMETHEUS_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Model Control Plane's toolset — Setup, Troubleshooting — is a fair guide to whether it matches your workflow. It is maintained by dvladimirov; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Setup | This will start: - Prometheus server (accessible at http://localhost:9090) - Node Exporter (for host metrics) - cAdvisor (for container metrics) |
| Troubleshooting | If you encounter permission issues: 1. Use the reset scripts to rebuild the containers 2. Check the logs with docker compose logs <service_name> 3. Make sure any components added to Langflow are included in the Dockerfil |
| Variable | Description | Required |
|---|---|---|
| AZURE_OPENAI_ENDPOINT | Configuration value read at startup. | Optional |
| AZURE_OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| AZURE_OPENAI_API_VERSION | Configuration value read at startup. | Optional |
| AZURE_DEPLOYMENT_NAME | Configuration value read at startup. | Optional |
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| OPENAI_CHAT_MODEL | Configuration value read at startup. | Optional |
| OPENAI_COMPLETION_MODEL | Configuration value read at startup. | Optional |
| PROMETHEUS_URL | Endpoint or connection string the server talks to. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.