Repository navigation
Panel Providers
MAP routes requests according to the selected provider. “Multi-panel” means one MAP installation can connect to multiple panel instances; it does not mean all panels share endpoints or authentication.
| Provider | API mode | Default API prefix | Authentication and behavior |
|---|---|---|---|
| Pterodactyl 1.x | client / application | Namespace is added by MAP | Client keys work with the Client API; Application keys work with Application API. The Admin namespace does not exist in 1.x. |
| Pterodactyl 2.x | client / application / admin | Namespace is added by MAP | The Admin API requires a root administrator's Client API key. Application requests accept an Application key or root-admin Client key. |
| Pelican Panel | client / application | Namespace is added by MAP | Pterodactyl-compatible Client/Application calls. The Admin API is not registered for Pelican by MAP. |
| MCSManager 9.x / 10.x | native | /api | Native API with query-string apikey by default. Dedicated instance list, power, command, and output-log tools are available. Version selection changes daemon selector parameters. |
| Calagopus | native | /api | Provider-specific native API; bearer auth by default. Pterodactyl keys and integrations do not migrate unchanged. |
| Crafty Controller API v2 | native | /api/v2 | Generic REST profile; bearer auth by default but configurable. No Pterodactyl-specific tools are claimed. |
| PufferPanel 2.x | native | /api | OAuth2 client credentials or a supplied bearer token. OAuth token endpoint defaults to /oauth2/token. |
| CubeCoders AMP | native | /API | Session-based authentication using an AMP username/password and optional TOTP token. MAP caches the returned SESSIONID. |
| Generic HTTPS REST | native | Configurable | Supports bearer, custom header, query, Basic, OAuth2 client credentials, or no auth where configured. Custom headers and API prefix are configurable. |
The matrix describes the implementation in the current MAP source. Dedicated tool availability can change between versions; the active MCP tool list and tests are the authority for a specific build.
The official 1.x API has two namespaces: Client at /api/client and Application at /api/application. A user can list their accessible servers with GET /api/client; panel-wide resource management generally needs Application API permissions. The 2.x Admin API is distinct and must not be called on 1.x.
MAP keeps these rules explicit:
- Use API mode client for the current user's servers and operations.
- Use application for panel-wide resources when the configured key has permissions.
- Use admin only on Pterodactyl 2.x with a root administrator's Client API key.
- Set panel_version to 1.x to make MAP reject Admin API calls locally, or auto when the version is unknown.
The documentation links are available in the project's README.
MAP treats Pelican as compatible with the Client and Application namespaces where the installed release implements those endpoints. Do not select admin for Pelican. Confirm the specific endpoint in the official Pelican API documentation if behavior differs from Pterodactyl.
MCSManager has its own API. Use provider mcsmanager and API mode native. The default query auth parameter is apikey, and the adapter adds X-Requested-With for MCSManager API calls.
The dedicated tools cover instance listing, power actions, command submission, and recent output logs:
- MCSManager 10.x uses daemonId.
- MCSManager 9.x uses remote_uuid for the daemon selector.
- State-changing calls are routed to the native open, stop, restart, and kill endpoints.
- Commands and output logs use the matching daemon and instance identifiers.
Set panel_version correctly. The generic native API tool is available for documented endpoints not covered by dedicated tools. Be aware that native commands can affect live game servers.
Official reference: MCSManager Instance API.
Calagopus is not a Pterodactyl API drop-in. Its migration guide states that API keys and active sessions do not migrate and that existing integrations need changes. Configure provider calagopus and use native requests with the provider's own API docs. The common spelling typo cagolqupus is accepted as an alias, but use calagopus in new configuration.
Official references: Calagopus documentation and Pterodactyl migration notes.
Crafty Controller API v2 uses its native API prefix by default. Configure its actual key type and header according to the installed version; MAP's generic provider supports bearer or custom header authentication.
PufferPanel's documented OAuth2 flow uses a form-encoded POST to /oauth2/token with grant_type=client_credentials, client_id, and client_secret. MAP supports automatic token acquisition/caching when both OAuth credentials are configured, and it can instead use a directly supplied bearer key if that's the credential you have.
Official references: Crafty Controller API v2 and PufferPanel OAuth2 authentication.
AMP exposes a native API browser at the panel's /API route. Calls use POST with JSON, and API methods need SESSIONID after the Login action. MAP handles login/session caching and injects SESSIONID for native calls. Configure an account with only the permissions necessary for the intended operations; treat session IDs like passwords.
Official reference: AMP API guide.
Generic REST supports panels for which an API is documented and uses supported authentication mechanisms. It does not auto-discover endpoints, translate data models, or automatically provide dedicated server/power/file tools.
When adding an integration, identify:
- Base URL and API prefix.
- Required auth method/header/query parameter.
- Exact method, path, query, and body shape.
- Error semantics, pagination, and version support.
- Which operations are destructive.
Do not claim a dedicated adapter for a panel until endpoint behavior is covered by tests.