Skip to content

Tools Reference

Jump to bottom
RealmsNetwork edited this page Oct 20, 2026 · 1 revision

Tool Reference

The tools exposed by MAP depend on the release, provider adapters, and configuration. The tool schemas returned by the running MCP server are authoritative.

Discovery and connectivity

  • list_panels: configured panel IDs, provider metadata, and authentication readiness without returning secret values.
  • panel_status: check connectivity to a supported API namespace or provider.
  • list_servers: list servers using the selected API/provider where implemented.

Generic API calls

  • panel_api_request: send a relative request using a configured API namespace or native provider route where supported.

Generic requests are privileged. POST, PUT, PATCH, and DELETE can mutate system state, and GET endpoints can expose sensitive operational data. Use only documented endpoints and configured HTTPS hosts.

Pterodactyl-compatible server operations

Where dedicated tools are registered for a selected panel, tool families may include:

  • Resource state and live usage.
  • Start, stop, restart, or kill.
  • Console command submission.
  • List, read, write, rename, or delete files.
  • Create directories.
  • Create, list, or delete backups.
  • Bounded binary upload/download.

The selected token must have the required permissions. Successful listing does not imply permission to write, delete, restart, or manage backups.

Native provider tools

MCSManager and AMP operations use their native APIs rather than Pterodactyl endpoints. Invoke only tools shown by the running MAP instance and check the target provider version.

Destructive operations

Take a backup before deleting files/backups or changing important configuration. Verify the panel ID and server ID before every write. Test new behavior on a disposable instance.

Typical errors

  • 401/403: missing, invalid, expired, or insufficient credentials.
  • 404: wrong API namespace, path, panel version, or server ID.
  • 3xx: redirects may be rejected to avoid credential forwarding.
  • Timeout/TLS/DNS failure: check connectivity from the MAP host.
  • Unsupported provider: use a supported adapter or generic native API route if configured.

Never include keys, cookies, Authorization headers, session identifiers, or signed transfer URLs when reporting errors.

Clone this wiki locally