Integration

F5 BIG-IP integration

F5 BIG-IP iControl REST API for local traffic management: list and edit virtual servers, pools, pool members and nodes, read live traffic statistics for a virtual server or a pool, and read system information such as installed software volumes and global settings. This talks directly to a BIG-IP management interface, so the management URL must be a publicly resolvable host reachable over HTTPS. Requests authenticate with HTTP basic credentials, which BIG-IP accepts for administrator accounts unless the appliance has been configured to require token authentication.

Connect F5 BIG-IP How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in F5 BIG-IP.Built from the 18 F5 BIG-IP tools below, on the connection you add once.

Common F5 BIG-IP use cases

retiring a listener for a decommissioned service
publishing a new service behind the load balancer
removing a decommissioned server from the rotation
removing a pool left behind after a service was retired
confirming which device a management URL actually reaches
taking one server out of every pool it belongs to at once
auditing which pools exist and how they distribute traffic
reading a virtual server before changing which pool it feeds
checking which backend servers are actually receiving traffic
adding a newly deployed server into the load balancing rotation

What you can do with F5 BIG-IP

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Virtual server, 6 operations

create_virtual_serverCreate virtual serverPOSTCreates a BIG-IP virtual server that listens on an address and forwards to a pool.
delete_virtual_serverDelete virtual serverDELETERemoves a BIG-IP virtual server so it stops accepting traffic.
get_virtual_serverGet virtual serverGETReturns a single BIG-IP virtual server with its listening address and pool.
get_virtual_server_statsGet virtual server statsGETReturns live connection and throughput counters for a BIG-IP virtual server.
list_virtual_serversList virtual serversGETReturns the BIG-IP virtual servers, the listening addresses that receive client traffic.
update_virtual_serverUpdate virtual serverPATCHChanges only the named settings of a BIG-IP virtual server, leaving the rest untouched.

Pool, 5 operations

create_poolCreate poolPOSTCreates a BIG-IP pool that a virtual server can distribute traffic across.
delete_poolDelete poolDELETERemoves a BIG-IP pool and its member list.
get_poolGet poolGETReturns a single BIG-IP pool with its distribution algorithm and health monitor.
get_pool_statsGet pool statsGETReturns live connection, request and availability counters for a BIG-IP pool.
list_poolsList poolsGETReturns the BIG-IP pools that virtual servers distribute traffic across.

Pool member, 4 operations

create_pool_memberCreate pool memberPOSTAdds a backend server to a BIG-IP pool so it starts receiving traffic.
delete_pool_memberDelete pool memberDELETETakes a backend server out of a BIG-IP pool.
list_pool_membersList pool membersGETReturns the backend servers in a BIG-IP pool with their health and administrative state.
update_pool_memberUpdate pool memberPATCHEnables, disables or reweights a backend server in a BIG-IP pool without touching the others.

Node, 1 operation

list_nodesList nodesGETReturns the BIG-IP nodes, the backend addresses that pool members are built from.

Software volume, 1 operation

list_software_volumesList software volumesGETReturns the BIG-IP software volumes with their versions and which one is currently booted.

System, 1 operation

get_global_settingsGet global settingsGETReturns BIG-IP device wide settings such as the host name and console timeout.

Use F5 BIG-IP from Claude Code, Cursor or Codex

Connect F5 BIG-IP in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its F5 BIG-IP operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect F5 BIG-IP

Create your workspace
Sign up free. Nothing to install.
Connect F5 BIG-IP once
Add your F5 BIG-IP connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

F5 BIG-IP integration FAQ

What can you do with the F5 BIG-IP integration?

LiveContext exposes 18 operations on F5 BIG-IP, covering virtual server, pool, pool member and node. Common uses include retiring a listener for a decommissioned service, publishing a new service behind the load balancer and removing a decommissioned server from the rotation.