Before you start
- A verified VentES account with an owner or administrator role in an active organization.
- Access to the apps you want to use.
- A client that supports remote MCP over Streamable HTTP and compatible OAuth registration.
Add the remote MCP server in your client
Open your assistant’s connector or MCP server settings. Choose its remote server option and enter the URL below. The exact screen name depends on the client. A client that supports only local stdio servers needs its own compatible remote connection support.
https://ssdashapi.ventes.group/mcpSign in and choose the business
If you change the selected business, select permissions again. Each connection belongs to one business.
- Start the connection from your assistant. It should open a VentES authorization page in your browser.
- Sign in to VentES and verify the client name and return address. Authorize a connection you started yourself.
- Choose the business in the Business selector.
- Check the capabilities you want to allow. They start unchecked. For a first test, select the relevant read permission.
- Choose Authorize selected access and return to your assistant.
Try a small read request
The assistant can use ventes.business_context to identify its business. Available tools reflect both your permissions and the applications you can access. If no useful tools appear, check your access before requesting broader permissions.
Try this prompt
Check the VentES business context and tell me which business and app capabilities this connection can access. Then summarize the available information for my chosen app without changing records.
Manage or disconnect the client
- Open AI agent connections in VentES.
- Select the business used for this connection.
- Find the client under Authorized clients.
- Choose Revoke access when you want it disconnected. To change the allowed capabilities, revoke and authorize a new connection with the desired selection.
Check compatibility before relying on a client
Muse, Claude, Grokbot and custom agents can have different connector features. The VentES standard SDK flow has been tested; a named product still needs its own connection check. Some hosted clients also require VentES to review their browser origin. If your client cannot complete authorization, use the troubleshooting guide or contact VentES with its name and version.
Maintained by VentES. Tell us if a step needs updating.