You decide which services we may enable for analytics, personalization, and external content.
We use cookies and similar technologies on our website to personalize content, embed external media, and better understand how individual areas are used.
Necessary cookies
These entries support essential functions such as security, stability, and form processing.
Optional sections
Your data may be processed with your consent or on the basis of legitimate interests. In the cookie settings, you can reject or explicitly allow each optional category.
Some services process personal data in third countries. By consenting, you also agree to this transfer. You can find more information in our Privacy Policy.
You can reopen and change your selection at any time. · 1.0.2
Pick the right path for your gameservers, VPS, dedicated servers, and TeamSpeak servers: MCP Connect for AI clients like Cursor and Claude, or the REST API for your own scripts, bots, and integrations.
Access
One account, three ways in: MCP is an open standard that lets AI clients discover and call tools. The REST API is the classic interface with fixed endpoints for your own code. Pick what fits your workflow.
For Cursor, Claude, ChatGPT, Gemini, and other MCP clients. Controls gameservers, VPS, dedicated servers, and TeamSpeak.
/api/mcp with OAuth ConnectFor CI/CD, custom dashboards, and classic integrations. Controls gameservers, VPS, dedicated servers, and TeamSpeak.
/api/v1/openapi.jsonzapx_ prefixNatural language right in the customer panel — no external client needed.
FAQ
In short: MCP vs. REST API vs. ZapX AI Agent.
AI client vs. your own integration.
MCP Connect is ideal when you work in Cursor, Claude, or Gemini: you sign in with OAuth Connect, your AI client uses the /api/mcp endpoint right in the chat, and you set permissions per connection. The REST API suits scripts, CI/CD, dashboards, and classic integrations: you authenticate with a Bearer API key, work with the OpenAPI 3.1 description, and set permissions on the key itself.
Interactive Scalar reference with OpenAPI.
You'll find every endpoint in the interactive Scalar reference, and an overview of the REST API on the API page. Interactive API referenceREST API overview
ZAP does not host LLMs.
AI hosting usually means GPU or model infrastructure. ZAP connects your existing services via MCP or a REST API.
Yes, MCP and API access are part of ZapX Pass Plus.
You use MCP Connect and the REST API with ZapX Pass Plus. For the ZapX AI Agent in the customer panel, you need a ZapX Pass with AI access.
No, it complements it.
The ZapX AI Agent runs directly in the customer panel, without an external client. MCP Connect links your services to your own AI client such as Cursor, Claude, ChatGPT, or Gemini.
You decide the permissions yourself.
MCP Connect links your AI client via OAuth, with fine-grained permissions per connection. For the REST API, you create an API key under Settings → API access and set the permissions it needs.
Still have questions? Our support team is happy to help.
Contact SupportConnect your AI client, confirm OAuth, and get started. For your own integrations, use the REST API.
MCP and API access are part of ZapX Pass Plus