f5 MCP (f5-mcp-318ae0fa)

MCP运维云端

提供方 f5-rahm

运维云端 stdio · 本地进程 API Key 社区 / 第三方
查看接入方式

一个为F5 BIG-IP设备提供查询服务的MCP服务器,通过mcpo集成,支持查询池、节点、虚拟服务器等LTM组件。

一句话选型结论

按资料字段整理

f5 MCP (f5-mcp-318ae0fa) 属于运维云端类 MCP 服务器,stdio · 本地进程,API Key,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

适用场景

F5BIG-IPPython本地部署MCP服务器网络管理设备监控AI集成

安装与配置

stdio · 本地进程 API Key
客户端在本机拉起子进程,数据不出本机
docker run --rm --network labnet curlimages/curl:latest \

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

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Docker,再按安装命令拉取依赖。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

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

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
f5 MCP (f5-mcp-318ae0fa)当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

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

详细介绍

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

F5 MCP Server with mcpo

A Model Context Protocol (MCP) server for F5 BIG-IP devices, served through mcpo. This setup provides AI
assistants with the ability to query F5 BIG-IP objects like pools, nodes, virtual servers, and other LTM
components.

Overview

This repository contains:
- F5 MCP Server: A FastMCP-based server that provides tools for querying F5 BIG-IP devices
- mcpo Integration: Configuration to serve the MCP server through mcpo for easy integration with AI clients
- Docker Setup: Complete containerized environment for both components

Prerequisites

  • Docker and Docker Compose
  • F5 BIG-IP device with REST API access
  • Network connectivity between the containers and your F5 device

Quick Start

  1. Clone and prepare the environment:bash git clone https://github.com/f5-rahm/f5-mcp cd f5-mcp

  2. Create the external Docker network:bash docker network create labnet

  3. Configure environment variables:

Create f5mcp/.env file with F5 credentials:env F5_HOST=192.168.1.100 F5_USER=admin F5_PASS=your-password

Create .env file in the main directory with mcpo API key:env MCPO_API_KEY=your-mcpo-api-key-here

  1. Start the services:bash docker-compose up -d

> Note: The docker-compose.yml should be configured to use the main .env file for the mcpo service. If needed, add env_file: .env to the mcpo service definition.

Project Structure```

.
├── f5mcp/
│ ├── Dockerfile
│ ├── main.py # MCP server implementation
│ ├── requirements.txt
│ └── .env # F5 credentials (create this)
├── docker-compose.yml # Service definitions
├── mcpo-config.json # mcpo configuration
├── .env # mcpo API key (create this)
└── README.md


## Testing the MCP Server

### 1. Direct HTTP Testing

Test the MCP server directly using curl or any HTTP client:

**Initialize a session:**```bash
curl -X POST http://localhost:8081/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2024-11-05",
      "capabilities": {
        "tools": {}
      },
      "clientInfo": {
        "name": "test-client",
        "version": "1.0.0"
      }
    }
  }'

List available tools:```bash
curl -X POST http://localhost:8081/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/list",
"params": {}
}'


**Test the obj_list tool:**```bash
# List all pools
curl -X POST http://localhost:8081/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 3,
    "method": "tools/call",
    "params": {
      "name": "obj_list",
      "arguments": {
        "obj_type": "pool"
      }
    }
  }'

# Get specific pool details
curl -X POST http://localhost:8081/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 4,
    "method": "tools/call",
    "params": {
      "name": "obj_list",
      "arguments": {
        "obj_type": "pool",
        "obj_name": "your-pool-name"
      }
    }
  }'

2. Container Testing

Check container logs:```bash

F5 MCP Server logs

docker logs f5mcp

MCPO logs

docker logs mcpo


**Test from within the network:**```bash
# Test MCP server from another container
docker run --rm --network labnet curlimages/curl:latest \
  curl -X POST http://f5mcp:8081/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{"tools":{}},"clientInfo":{"name":"test","version":"1.0.0"}}}'

Testing mcpo

1. Health Check```bash

Check if mcpo is running

curl http://localhost:8000/health

If API key authentication is enabled, include it:

curl -H "Authorization: Bearer your-mcpo-api-key-here" http://localhost:8000/health


### 2. List Configured Servers```bash
curl -X GET http://localhost:8000/servers

3. Test MCP Server Through mcpo```bash

Initialize connection through mcpo

curl -X POST http://localhost:8000/f5mcp/initialize \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{
"protocolVersion": "2024-11-05",
"capabilities": {
"tools": {}
},
"clientInfo": {
"name": "test-client",
"version": "1.0.0"
}
}'

List tools through mcpo

curl -X POST http://localhost:8000/f5mcp/tools/list \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{}'

Call obj_list through mcpo

curl -X POST http://localhost:8000/f5mcp/tools/call \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{
"name": "obj_list",
"arguments": {
"obj_type": "pool"
}
}'


> **Note**: If mcpo is configured with API key authentication, add `-H "Authorization: Bearer your-mcpo-api-key-here"` to all curl commands above.

## Available Tools

### `obj_list`

Retrieves F5 BIG-IP LTM objects.

**Parameters:**
- `obj_type` (required): Type of F5 object (e.g., "pool", "node", "virtual", "rule")
- `obj_name` (optional): Specific object name to retrieve details for

**Examples:**```json
// List all pools
{
  "obj_type": "pool"
}

// Get specific pool details
{
  "obj_type": "pool",
  "obj_name": "web-pool"
}

// List all virtual servers
{
  "obj_type": "virtual"
}

Configuration

Environment Variables

F5 MCP Server Configuration (in f5mcp/.env):
- F5_HOST: F5 BIG-IP management IP address
- F5_USER: F5 username with API access
- F5_PASS: F5 user password

mcpo Configuration (in .env):
- MCPO_API_KEY: API key for MCPO authentication (if required)

mcpo Server Configuration

The mcpo configuration in mcpo-config.json defines:```json
{
"mcpServers": {
"f5mcp": {
"type": "streamable-http",
"url": "http://f5mcp:8081/mcp",
"headers": {
"Content-Type": "application/json",
"Accept": "application/json, text/event-stream"
}
}
}
}


## Troubleshooting

### Common Issues

1. **Connection refused to F5 device:**
   - Verify F5_HOST is reachable from containers
   - Check F5 credentials in `.env` file
   - Ensure F5 device has REST API enabled

2. **mcpo can't connect to MCP server:**
   - Verify both containers are on the `labnet` network
   - Check that f5mcp container is running: `docker ps`
   - Review container logs: `docker logs f5mcp`

3. **Network issues:**
   - Ensure the `labnet` network exists: `docker network ls`
   - Create it if missing: `docker network create labnet`

4. **Missing API keys:**
   - Verify `.env` file exists in main directory with MCPO_API_KEY
   - Check that `f5mcp/.env` contains valid F5 credentials

### Debugging Commands```bash
# Check container status
docker-compose ps

# View logs
docker-compose logs f5mcp
docker-compose logs mcpo

# Test network connectivity
docker exec mcpo ping f5mcp

# Interactive container access
docker exec -it f5mcp /bin/bash
docker exec -it mcpo /bin/bash

Development

Adding New Tools

To add new tools to the MCP server, modify f5mcp/main.py:```python
@mcp.tool
def your_new_tool(param1: str, param2: int = 10):
"""Description of your tool"""
# Your implementation here
return result


### Updating Dependencies

Update `f5mcp/requirements.txt` and rebuild:```bash
docker-compose build f5mcp
docker-compose up -d f5mcp

Integration with AI Clients

This MCP server can be integrated with AI assistants that support the Model Context Protocol. The tools will be available to the AI for querying F5 BIG-IP configurations and status.

Example AI assistant usage:
- "List all pools on the F5 device"
- "Show me the configuration of the web-pool"
- "What virtual servers are configured?"

Security Considerations

  • Store F5 credentials securely (consider using Docker secrets in production)
  • Limit network access to the containers
  • Use HTTPS for production deployments
  • Implement proper authentication for mcpo if needed
  • Consider F5 user permissions (read-only recommended for monitoring use cases)

License

Apache License 2.0

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
f5 MCP (f5-mcp-318ae0fa) 怎么安装?

在客户端按下面的安装命令接入:docker run --rm --network labnet curlimages/curl:latest \。装完在客户端配置里引用同一个包或端点。

f5 MCP (f5-mcp-318ae0fa) 怎么在客户端里配置?

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

f5 MCP (f5-mcp-318ae0fa) 收费吗?

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

f5 MCP (f5-mcp-318ae0fa) 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

f5 MCP (f5-mcp-318ae0fa) 能提供哪些能力?

资料显示能力标签包括 Python、网络管理、Docker。具体工具清单以官方文档为准。

f5 MCP (f5-mcp-318ae0fa) 需要什么运行环境?

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

f5 MCP (f5-mcp-318ae0fa) 是本地还是远程?

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

热门专题

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

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