Dvladimirov MCP

MCP开发工具

提供方 dvladimirov

开发工具 stdio · 本地进程 无需鉴权 社区 / 第三方
查看接入方式

一个集成了OpenAI服务、Git仓库分析、本地文件系统操作和Prometheus监控的模型控制平面服务器,适用于AI开发、代码分析和系统监控场景。

一句话选型结论

按资料字段整理

Dvladimirov MCP 属于开发工具类 MCP 服务器,stdio · 本地进程,无需鉴权,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权无需鉴权 部署方式本地部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

适用场景

AI开发平台Python本地部署代码分析工具系统监控Git集成文件管理

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
pip install -r requirements.txt

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Dvladimirov MCP当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方dvladimirov上游标注的维护方 dvladimirov
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

12.7 KB
来自项目仓库与上游目录的原文,未做删改

MCP Server with OpenAI, Git, Filesystem, and Prometheus Integration

This repository contains a Model Control Plane (MCP) server implementation that supports OpenAI services, Git repository analysis, local filesystem operations, and Prometheus integration.

Project Structure```

MCP/
├── mcp/ # Core MCP library modules
├── scripts/ # Utility scripts and test tools
├── prometheus/ # Prometheus configuration
├── docker-compose.yml # Docker configuration
├── mcp_server.py # Main server implementation
├── mcp_run # Main runner script (shortcut)
└── README.md # This file


## Requirements

- Python 3.8+
- FastAPI
- Uvicorn
- OpenAI SDK
- GitPython
- Requests
- Docker and Docker Compose (for Prometheus features)

## Installation

1. Clone this repository
2. Install the dependencies:```bash
pip install -r requirements.txt

Environment Variables

Set the following environment variables:

For Azure OpenAI:```bash
export AZURE_OPENAI_ENDPOINT="your-azure-endpoint"
export AZURE_OPENAI_API_KEY="your-azure-api-key"
export AZURE_OPENAI_API_VERSION="2023-05-15"
export AZURE_DEPLOYMENT_NAME="your-deployment-name"


For Standard OpenAI:```bash
export OPENAI_API_KEY="your-openai-api-key"
# Optional: Specify which models to use
export OPENAI_CHAT_MODEL="gpt-4o-mini"  # Default if not specified
export OPENAI_COMPLETION_MODEL="gpt-3.5-turbo-instruct"  # Default if not specified

For Prometheus:```bash
export PROMETHEUS_URL="http://localhost:9090" # Default if not specified


## Running the Server

Start the MCP server:```bash
python scripts/start_mcp_server.py

Or for more options:```bash
python scripts/start_mcp_server.py --host 0.0.0.0 --port 8000 --debug


The server will be available at http://localhost:8000.

## Unified Testing Tool

We provide a unified testing script that gives you a user-friendly interface to all testing functionality:```bash
./mcp_run

This interactive script provides:
- Filesystem tests
- Git integration tests
- Memory analysis tools
- Prometheus tests & memory stress
- MCP server management
- Environment setup

Individual Tests

You can also run individual tests directly:

Test the OpenAI integration:```bash
python scripts/test_mcp_client.py


Test the Git integration (provide a Git repository URL):```bash
python scripts/test_git_integration.py https://github.com/username/repository

Test the Git diff functionality (analyze requirements compatibility):```bash
python scripts/test_git_diff.py https://github.com/username/repository [commit-sha]


Test the filesystem functionality:```bash
python scripts/test_filesystem.py

Test the langflow integration with MCP:```bash
python scripts/test_langflow_integration.py [OPTIONAL_REPO_URL]


Test the Prometheus integration:```bash
python scripts/test_prometheus.py [prometheus_url]

Advanced Git Analysis

For more advanced Git repository analysis with AI recommendations:```bash
python scripts/langflow_git_analyzer.py https://github.com/username/repository


You can also search for specific patterns in the repository:```bash
python scripts/langflow_git_analyzer.py https://github.com/username/repository --search "def main"

Or analyze the last commit diff with AI insights:```bash
python scripts/langflow_git_analyzer.py https://github.com/username/repository --diff


## Memory Analysis Tools

MCP includes several tools for memory monitoring and analysis:```bash
# Basic memory diagnostics with AI analysis
python scripts/ai_memory_diagnostics.py

# Interactive memory dashboard
python scripts/mcp_memory_dashboard.py

# Memory alerting system
python scripts/mcp_memory_alerting.py

You can also simulate memory pressure for testing:```bash
python scripts/simulate_memory_pressure.py --target 85 --duration 300


## Prometheus Integration

### Setup

1. Start the Prometheus stack using Docker Compose:```bash
docker compose up -d

This will start:
- Prometheus server (accessible at http://localhost:9090)
- Node Exporter (for host metrics)
- cAdvisor (for container metrics)

  1. For stress testing, you can start the memory stress container:```bash
    docker compose up -d --build memory-stress

Or use the container test script:```bash
./scripts/container-memory-test.sh start

Docker Configuration and Reset Scripts

This project includes multiple Docker configurations and reset scripts for reliable operation across different environments:

Docker Configurations

  • Standard Configuration (docker-compose.yml): Uses custom Dockerfiles for Prometheus and Langflow to ensure consistent permissions across systems.
  • Bridge Network Configuration (docker-compose.bridge.yml): Alternative configuration that uses bridge networking for environments where host networking is problematic.

Custom Dockerfiles for Solving Permission Issues

The project uses custom Dockerfiles for both Prometheus and Langflow to solve common permission issues:

  • Dockerfile.prometheus: Sets up the Prometheus configuration with proper permissions for the nobody user.
  • Dockerfile.langflow: Copies the components directory into the container without changing file ownership, allowing Langflow to access the components without permission errors.

This approach eliminates the need for volume mounts that can lead to permission conflicts across different machines and user configurations.

Reset Scripts

  • All Services Reset (reset-all.sh): Reset all containers with a single command.```bash
    # Basic reset (rebuilds containers with existing volumes)
    ./reset-all.sh

# Full reset (removes volumes and rebuilds containers)
./reset-all.sh --clean
```

  • Individual Service Reset:```bash
    # Reset only Prometheus
    ./reset-prometheus.sh

# Reset only Langflow
./reset-langflow.sh
```

These scripts ensure that the containers are properly configured with correct permissions and the latest code changes.

Troubleshooting

If you encounter permission issues:
1. Use the reset scripts to rebuild the containers
2. Check the logs with docker compose logs
3. Make sure any components added to Langflow are included in the Dockerfile.langflow

Cross-Machine Deployment

When deploying to a new machine:
1. Clone the repository
2. Make reset scripts executable: chmod +x *.sh
3. Run the reset script: ./reset-all.sh

The custom Dockerfiles automatically handle all permission issues that might occur across different systems.

Using Prometheus Client

The MCPAIComponent class includes Prometheus capabilities:```python
from langflow import MCPAIComponent

Initialize the client

mcp = MCPAIComponent(mcp_server_url="http://localhost:8000")

Instant query (current metric values)

result = mcp.prometheus_query("up")

Range query (metrics over time)

result = mcp.prometheus_query_range(
query="rate(node_cpu_seconds_total{mode='system'}[1m])",
start="2023-03-01T00:00:00Z",
end="2023-03-01T01:00:00Z",
step="15s"
)

Get all labels

labels = mcp.prometheus_get_labels()

Get label values

values = mcp.prometheus_get_label_values("job")

Get targets

targets = mcp.prometheus_get_targets()

Get alerts

alerts = mcp.prometheus_get_alerts()


### Useful PromQL Queries

- CPU Usage: `rate(node_cpu_seconds_total{mode!="idle"}[1m])`
- Memory Usage: `node_memory_MemTotal_bytes - node_memory_MemAvailable_bytes`
- Disk Usage: `node_filesystem_avail_bytes{mountpoint="/"} / node_filesystem_size_bytes{mountpoint="/"}`
- Container CPU Usage: `rate(container_cpu_usage_seconds_total[1m])`
- Container Memory Usage: `container_memory_usage_bytes`

## API Endpoints

### OpenAI Endpoints
- GET `/v1/models` - List all available models
- GET `/v1/models/{model_id}` - Get information about a specific model
- POST `/v1/models/azure-gpt-4/completion` - Generate text completion using Azure OpenAI
- POST `/v1/models/azure-gpt-4/chat` - Generate chat response using Azure OpenAI
- POST `/v1/models/openai-gpt-chat/chat` - Generate chat response using OpenAI chat model
- POST `/v1/models/openai-gpt-completion/completion` - Generate text completion using OpenAI completion model

### Git Integration Endpoints
- POST `/v1/models/git-analyzer/analyze` - Analyze a Git repository
- POST `/v1/models/git-analyzer/search` - Search a Git repository for files matching a pattern
- POST `/v1/models/git-analyzer/diff` - Get the diff of the last commit in a repository

### Filesystem Endpoints
- POST `/v1/models/filesystem/list` - List contents of a directory
- POST `/v1/models/filesystem/read` - Read a file's contents
- POST `/v1/models/filesystem/read-multiple` - Read multiple files at once
- POST `/v1/models/filesystem/write` - Write content to a file
- POST `/v1/models/filesystem/edit` - Edit a file with multiple replacements
- POST `/v1/models/filesystem/mkdir` - Create a directory
- POST `/v1/models/filesystem/move` - Move a file or directory
- POST `/v1/models/filesystem/search` - Search for files matching a pattern
- POST `/v1/models/filesystem/info` - Get information about a file or directory

### Prometheus Endpoints
- POST `/v1/models/prometheus/query` - Execute an instant query
- POST `/v1/models/prometheus/query_range` - Execute a range query
- POST `/v1/models/prometheus/series` - Get series data
- GET `/v1/models/prometheus/labels` - Get all available labels
- POST `/v1/models/prometheus/label_values` - Get values for a specific label
- GET `/v1/models/prometheus/targets` - Get all targets
- GET `/v1/models/prometheus/rules` - Get all rules
- GET `/v1/models/prometheus/alerts` - Get all alerts

## Client Usage

You can use the `MCPAIComponent` in your LangFlow pipelines by providing the MCP server URL:```python
from langflow import MCPAIComponent

mcp = MCPAIComponent(mcp_server_url="http://localhost:8000")

# List available models
models = mcp.list_models()
print(models)

# Generate chat completion with OpenAI model
chat_response = mcp.chat(
    model_id="openai-gpt-chat",
    messages=[
        {"role": "system", "content": "You are a helpful assistant."},
        {"role": "user", "content": "Tell me a joke about programming."}
    ],
    max_tokens=100,
    temperature=0.7
)
print(chat_response)

# Generate text completion with OpenAI model
completion_response = mcp.completion(
    model_id="openai-gpt-completion",
    prompt="Write a function in Python to calculate the factorial of a number:",
    max_tokens=150,
    temperature=0.7
)
print(completion_response)

# Analyze a Git repository
repo_analysis = mcp.analyze_git_repo("https://github.com/username/repository")
print(repo_analysis)

# Search a Git repository
search_results = mcp.search_git_repo("https://github.com/username/repository", "def main")
print(search_results)

# Get the diff of the last commit
diff_info = mcp.get_git_diff("https://github.com/username/repository")
print(diff_info)

# List files in the current directory
dir_contents = mcp.list_directory()
print(dir_contents)

# Read a file
file_content = mcp.read_file("path/to/file.txt")
print(file_content)

# Write to a file
write_result = mcp.write_file("path/to/new_file.txt", "Hello, world!")
print(write_result)

# Search for files
search_result = mcp.search_files("*.py")
print(search_result)

Using the GitCodeAnalyzer Class

For more structured Git analysis, you can use the GitCodeAnalyzer class:```python
from langflow_git_analyzer import GitCodeAnalyzer

Initialize the analyzer

analyzer = GitCodeAnalyzer(mcp_server_url="http://localhost:8000")

Analyze a repository

analyzer.analyze_repository("https://github.com/username/repository")

Get a summary

summary = analyzer.get_repository_summary()
print(summary)

Get AI recommendations

recommendations = analyzer.get_repository_recommendations()
print(recommendations)

Analyze code patterns

pattern_analysis = analyzer.analyze_code_pattern("def process")
print(pattern_analysis)

Get the last commit diff

diff_info = analyzer.get_last_commit_diff()
print(diff_info)

Get a formatted summary of the diff

diff_summary = analyzer.get_formatted_diff_summary()
print(diff_summary)

Get AI analysis of the commit changes

diff_analysis = analyzer.analyze_commit_diff()
print(diff_analysis)
```

Troubleshooting

Prometheus Issues

  1. Verify Prometheus is running: docker ps | grep prometheus
  2. Check you can access the Prometheus UI: http://localhost:9090
  3. Verify the MCP server is running and accessible
  4. Check the MCP server logs for errors
  5. Try simple queries first to verify connectivity (e.g., up query)

OpenAI Issues

  1. Verify your API keys are set correctly
  2. Check for rate limiting or quota issues
  3. Verify you're using supported models for your API key

Git Issues

  1. Ensure the Git repository URL is accessible
  2. Check for authentication issues if using private repositories
  3. Ensure GitPython is installed correctly

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Dvladimirov MCP 怎么安装?

在客户端按下面的安装命令接入:pip install -r requirements.txt。装完在客户端配置里引用同一个包或端点。

Dvladimirov MCP 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Dvladimirov MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Dvladimirov MCP 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Dvladimirov MCP 能提供哪些能力?

资料显示能力标签包括 Python、系统监控、Git集成。具体工具清单以官方文档为准。

Dvladimirov MCP 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

Dvladimirov MCP 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。