Integration

Pterodactyl Application API integration

Pterodactyl is a self-hosted game server panel. With an Application API key, administer the whole panel: create, update, suspend, reinstall and delete servers, change their limits, manage their databases, manage users, nodes and their allocations, and locations, and read nests and eggs (with their variables) to build servers, for example from a billing system. Built for Panel 1.x. Left out: the node configuration route (its answer carries the node's daemon token) and the server startup update (it replaces environment variables, which this API does not return). Authentication is an Application API key (Admin, Application API in the Panel, with read and write rights per resource) sent as a Bearer token, plus the address of your Panel.

Connect Pterodactyl Application API How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Pterodactyl Application API.Built from the 40 Pterodactyl Application API tools below, on the connection you add once.

What you can do with Pterodactyl Application API

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.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

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

Server, 9 operations

create_serverCreate serverPOSTAgents: ask firstCreates and installs a new game server for a user (uses node resources). Read the egg's variables with get_egg first: every variable its rules require must be set in environment.
delete_serverDelete serverDELETEAgents: ask firstPermanently deletes a server and its files from its node.
force_delete_serverForce delete serverDELETEAgents: ask firstPermanently deletes a server even when its node or database host fails to clean up (can leave files behind on the node).
get_serverGet serverGETAgents: ask firstReturns one server by numeric id: owner, node, allocation, nest and egg ids, limits, feature limits, container image and startup command, state. Environment variables are not returned.
get_server_by_external_idGet server by external idGETAgents: ask firstReturns one server by the external id your system set on it, with the same fields as get_server.
list_serversList serversGETAgents: ask firstLists every server on the panel with owner, node, egg, limits, feature limits, container image and state; filter by name, uuid, image or external id.
reinstall_serverReinstall serverPOSTAgents: ask firstQueues a reinstall of the server on its node: the egg's install process runs again on the server's files.
suspend_serverSuspend serverPOSTAgents: ask firstSuspends a server: it is stopped and its users lose access until unsuspend_server.
unsuspend_serverUnsuspend serverPOSTAgents: ask firstLifts a server's suspension so its users can use it again.

Node, 6 operations

create_nodeCreate nodePOSTAgents: ask firstRegisters a new node (a machine that will run Wings) in a location; configure Wings on that machine afterwards from the Panel.
delete_nodeDelete nodeDELETEAgents: ask firstPermanently removes a node from the panel; refused while servers are on it.
get_nodeGet nodeGETAgents: ask firstReturns one node: location, address, scheme, memory and disk totals with what servers already use, overallocation, ports and maintenance state.
list_deployable_nodesList deployable nodesGETAgents: ask firstLists the nodes with enough free memory and disk for a new server of the given size, optionally only in some locations.
list_nodesList nodesGETAgents: ask firstLists the panel's nodes (machines running Wings) with location, address, memory and disk totals, overallocation, ports and maintenance state.
update_nodeUpdate nodePATCHAgents: ask firstUpdates a node's settings; name, location, address, scheme, memory, disk, overallocation and ports are required, so read get_node first and send the values to keep.

User, 6 operations

create_userCreate userPOSTAgents: ask firstCreates a panel user account (the panel emails the new user). Personal data.
delete_userDelete userDELETEAgents: ask firstPermanently deletes a panel user; the panel refuses while the user still owns servers.
get_userGet userGETAgents: ask firstReturns one panel user by numeric id: username, email, names, language, admin and two-factor flags. Personal data.
get_user_by_external_idGet user by external idGETAgents: ask firstReturns one panel user by the external id your system set on it. Personal data.
list_usersList usersGETAgents: ask firstLists the panel's users (username, email, names, admin flag); filter by email, uuid, username or external id. Personal data.
update_userUpdate userPATCHAgents: ask firstUpdates a user's email, username, names and language; those four fields are required, so read get_user first and send the values to keep. Passwords are not set here.

Location, 5 operations

create_locationCreate locationPOSTAgents: ask firstCreates a location (a group of nodes, such as a data center).
delete_locationDelete locationDELETEAgents: ask firstPermanently deletes a location; refused while nodes are in it.
get_locationGet locationGETAgents: ask firstReturns one location by id: short code, description and dates.
list_locationsList locationsGETAgents: ask firstLists the locations (groups of nodes, such as a data center) on the panel.
update_locationUpdate locationPATCHAgents: ask firstUpdates a location's short code and description; short is required, so send the current one to keep it.

Database, 4 operations

create_server_databaseCreate server databasePOSTAgents: ask firstCreates a database for a server on a database host. The generated password is not returned: view it in the Panel.
delete_server_databaseDelete server databaseDELETEAgents: ask firstPermanently deletes a server's database and its data.
get_server_databaseGet server databaseGETAgents: ask firstReturns one database of a server: host id, name, user name, allowed remotes, connection limit. The password is not returned.
list_server_databasesList server databasesGETAgents: ask firstLists a server's databases with host id, name, user name, allowed remotes and connection limit. Passwords are not returned.

Allocation, 3 operations

create_node_allocationsCreate node allocationsPOSTAgents: ask firstAdds allocations to a node: one IP address with one or more ports or port ranges.
delete_node_allocationDelete node allocationDELETEAgents: ask firstPermanently removes an allocation from a node; refused while a server uses it.
list_node_allocationsList node allocationsGETAgents: ask firstLists a node's allocations (IP and port pairs) and whether each is assigned to a server; a free one feeds create_server.

Egg, 2 operations

get_eggGet eggGETAgents: ask firstReturns one egg with its Docker images, default startup command and variables (env_variable, default, rules), which create_server needs.
list_eggsList eggsGETAgents: ask firstLists the eggs (server types) of a nest with Docker images, startup command and variables; egg ids feed create_server.

Nest, 2 operations

get_nestGet nestGETAgents: ask firstReturns one nest (a group of eggs) by id.
list_nestsList nestsGETAgents: ask firstLists the nests (egg groups, such as Minecraft or Source Engine) on the panel.

Database password, 1 operation

reset_server_database_passwordReset server database passwordPOSTAgents: ask firstGives a server's database a new random password (anything using the old one stops connecting). The new password is not returned.

Server build, 1 operation

update_server_buildUpdate server buildPATCHAgents: ask firstChanges a server's primary allocation, memory, swap, disk, IO and CPU limits and feature limits; read get_server first and send every value to keep.

Server detail, 1 operation

update_server_detailsUpdate server detailsPATCHAgents: ask firstChanges a server's name, owner, external id and description. The panel sets all four from the request, so read get_server first and send every value to keep: an external id or description left out is cleared.

Use Pterodactyl Application API from Claude Code, Cursor or Codex

Connect Pterodactyl Application API in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Pterodactyl Application API 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 Pterodactyl Application API

Create your workspace
Sign up free. Nothing to install.
Connect Pterodactyl Application API once
Add your Pterodactyl Application API 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.