MCP.so
Sign In
Servers

F5 MCP Server

@czirakim

A MCP server for talking to a F5 device

Overview

What is F5 MCP Server?

F5 MCP Server is an MCP (Model Context Protocol) server that interacts with F5 devices through the iControl REST API. It provides a set of tools for managing F5 objects such as virtual servers (VIPs), pools, iRules, and profiles, and is designed for developers and network administrators automating F5 infrastructure.

How to use F5 MCP Server?

Install the server via Smithery (npx -y @smithery/cli install @czirakim/F5.MCP.server --client claude) or run it as a Docker container. Configure sensitive information (IP address, authorization string) through environment variables loaded from a .env file. The server uses the stdio transport and was tested with the Claude Desktop app hosted in Windows WSL.

Key features of F5 MCP Server

  • Tool-based API with list, create, update, and delete operations.
  • REST API integration using Python’s requests library.
  • Environment configuration via .env file for security.
  • Modular design allowing easy addition of new tools.
  • stdio transport for compatibility with various clients.
  • Docker support for containerized deployment.

Use cases of F5 MCP Server

  • Automate creation and management of F5 virtual servers and pools.
  • Integrate an AI assistant with F5 infrastructure for configuration tasks.
  • Simplify bulk updates to iRules or profiles across multiple devices.
  • Enable natural-language-driven CRUD operations on F5 objects.

FAQ from F5 MCP Server

What does F5 MCP Server do?

It acts as a bridge between MCP-compatible clients (like Claude Desktop) and F5 devices, allowing users to create, read, update, and delete F5 objects via the iControl REST API.

What are the runtime dependencies?

The server requires Python, the requests library, and environment variables holding the F5 device IP and authorization token. A Dockerfile is provided for containerized use.

How does the server communicate with clients?

It uses the stdio transport, meaning it reads from standard input and writes to standard output, making it compatible with any MCP client that supports this transport.

Which F5 objects can be managed?

The server supports managing virtual servers (VIPs), pools, iRules, and profiles through dedicated CRUD tools.

Has it been tested with specific clients?

Yes, it was tested with the Claude Desktop app, with the MCP server hosted in Windows WSL.

More from Other