Overview
What is F5 MCP Server?
F5 MCP Server is a Model Context Protocol server that interacts with F5 devices via the iControl REST API. It provides tools for managing F5 objects such as virtual servers (VIPs), pools, iRules, and profiles. This server is implemented with the FastMCP framework and is intended for developers or operators who need to integrate F5 device management into AI assistants or automation workflows.
How to use F5 MCP Server?
Set up environment variables (IP address, authorization strings) in a .env file, then run the server using stdio transport. An example configuration for the Claude Desktop app is included in the repository. For containerized deployment, a Dockerfile is provided.
Key features of F5 MCP Server
- Tool-based API for creating, updating, listing, and deleting F5 objects.
- REST API integration using Python's
requestslibrary. - Environment configuration via
.envfile for sensitive data. - Extensible modular design for adding new tools.
stdiotransport support for client integrations.- Dockerfile available for containerized deployment.
Use cases of F5 MCP Server
- Automating creation and management of F5 virtual servers.
- Updating or deleting pool configurations via natural language prompts.
- Listing existing F5 objects like iRules or profiles.
- Integrating F5 device management with AI chat assistants like Claude Desktop.
- Running F5 management tasks from a containerized environment.
FAQ from F5 MCP Server
What does F5 MCP Server do?
It provides MCP-compatible tools to perform CRUD operations on F5 devices using the iControl REST API, enabling AI assistants to manage F5 objects.
What runtime or dependencies are required?
Python with the requests library and environment variable configuration (stored in a .env file) are required. The server can also be run via the provided Dockerfile.
How is authentication handled?
Authentication credentials and IP addresses are loaded from a .env file as environment variables, keeping sensitive information out of the code.
What transport does the server use?
The server uses stdio transport, making it compatible with clients that support this MCP transport method.
Can this server be run in a container?
Yes, a Dockerfile is included in the repository for building and running the server as a Docker container.