ECP MCP server for MSPs: connect per client
Every AI app connection is bound to one client organisation. That keeps one client's data apart from another's. Connect once per client.
When a client can connect
A client organisation can connect AI apps when it has its own active subscription, or when you manage it and your own partner contract is active (started and not lapsed). ECP checks this on every connection and every call, so a lapsed contract stops the connections of the clients you manage.
The client's administrator switches it on
Eligibility is not enough. An owner or admin of the client organisation must switch on Allow AI app connections for this organisation under Settings, Connected AI apps. You can do it yourself only where you hold that role.
Connect per client
- Check that the client is eligible (see above).
- Ask the client's owner or admin to switch on AI app connections, or do it yourself if you hold that role there.
- Make sure the person who connects has the right to connect AI apps.
- In your AI app, add the server URL and approve for that client's organisation. Name the connection after the client, for example ECP Acme, so you can tell them apart.
- Repeat for the next client.
The steps for each AI app are in ECP MCP server: connect Claude, ChatGPT, Copilot or Cursor.
A connection acts with the rights of the person who made it, in that one client organisation. It cannot see your other clients.