Home

Model Access Panel (MAP)

One MCP gateway for multiple game-server panels. MAP is a self-hosted, open-source bridge between Model Context Protocol clients and hosting-panel APIs.

Wiki navigation

• Getting Started
• Panel Providers and Compatibility
• Configuration Reference
• Tool Reference
• Deployment Guide
• Security Model
• Troubleshooting
• Architecture and Contributing

Project links: Source code · Issues · Discussions · Releases

What MAP does

MAP connects an MCP-compatible AI client or automation runner to configured panel APIs. Depending on the provider adapter and credentials, it can inspect servers, read resource status, operate servers, send console commands, manage files and backups, and call supported native API endpoints.

One MAP installation can connect to several panels. Each panel has a separate ID and credential set so requests can target a specific installation.

Provider support is capability-based

A multi-panel gateway does not mean all panels have identical endpoints. Pterodactyl-compatible installations can use dedicated server tools; other providers use native adapters or generic REST routing where implemented and configured.

• Pterodactyl: legacy 1.x Client and Application API conventions; Admin API only on versions that support it.
• Pelican: compatible API workflows where exposed by the installed version.
• MCSManager: native API integration; available actions depend on adapter and version.
• AMP / CubeCoders: native session-based API integration.
• Other panels: generic REST routing may work with documented HTTPS APIs, but MAP cannot infer vendor-specific authentication, schemas, or operations automatically.

See Panel Providers and Compatibility before depending on a particular operation. If a provider is missing, request it through GitHub Issues with its version, official API docs, desired operations, and sanitized examples. Never include live credentials.

Safety note

MAP is an administrative integration, not just a read-only dashboard. Depending on permissions, callers may stop servers, run console commands, modify or delete files, delete backups, or call destructive endpoints. Use least-privilege credentials, restrict network access, and test against a non-production panel first.

Start here

1. Follow Getting Started.
2. Set up panel IDs and credentials using the Configuration Reference.
3. Check the Tool Reference and the panel vendor's API docs.
4. Read the Security Model before exposing HTTP access beyond loopback.