Access via MCP
The Model Context Protocol is the second way to the same services. You create as many endpoints in the portal as you need, one per application, team or assistant, and decide for each of them which APIs it offers.
When to use MCP and when the API
MCP is the route for people: anyone using an AI assistant enters one address and key there once and can call the services in conversation from then on. No software development and no development budget is needed, only a tool that speaks MCP.
The API is the route for software: a call from inside your application, with no assistant in between, with an OpenAPI description per service. Anyone automating a process takes that route; anyone doing a task by hand takes MCP.
Both routes lead to the same services, the same credit balance and the same invoice. You do not have to choose: one account carries both side by side, and whatever works well over MCP can later be moved to the API without changing the contract.
Connected in three steps
- Create a customer key in the portal and keep the matching secret safe.
- Under "MCP endpoints", create an endpoint and assign it the APIs it should offer.
- Enter the endpoint's address in your MCP-capable tool and store key and secret there, optionally with a cost centre after a vertical bar.
Address
Each endpoint has its own identifier. It is shown in the portal and never changes, not even if you rename the endpoint.
https://api.apizone.eu/mcp/{Endpunkt-Kennung}
A few extra credits
A call via MCP costs the price of the service plus a small amount for the endpoint itself. Both appear separately in your billing view, and you see both before the call.
The same cost centres
The cost centre is appended to the key and is reported separately, just as with the API.
The same data sovereignty
Processing within the EU, one data processing agreement, whichever route you choose.