Your business. Your preferred interface.
Connect your AI agent to VentES.
Use a compatible desktop assistant or custom agent to work with the VentES applications your business has access to. Sign in, choose a business and authorize the capabilities it can use.
Add a remote MCP connection
In a client supporting Streamable HTTP and OAuth authorization, add this server URL:
https://ssdashapi.ventes.group/mcp- Start the connection from your AI client.
- Sign in to VentES and choose the business.
- Select the permitted capabilities and authorize the client.
- Return to the client to discover the available tools.
A verified owner or administrator can authorize connections. App subscriptions and assigned access still apply. Client names are supplied by their developers, so approve only a connection you started.
Keep control of the work
Read permissions let the client request information for the selected business. Write permissions let it prepare proposed changes. A proposal returns an approval link where you review the exact action in VentES before it executes.
Your client can check progress and retrieve the result using ventes.action_status. It can also inspect the selected business with ventes.business_context. The agent does not receive permission to bypass approval.
Revoke a connection in VentES whenever you need to. Current business membership and application access are rechecked for delegated requests. Each connection is bound to one business.
For custom agents
The gateway publishes OAuth protected-resource and authorization-server metadata. Register a public client, use the authorization-code flow with S256 PKCE, and request the MCP URL as the resource. Keep the returned tokens in your client’s secure credential storage.
- Resource
- https://ssdashapi.ventes.group/mcp
- Protected resource metadata
- https://ssdashapi.ventes.group/.well-known/oauth-protected-resource/mcp
- Authorization server metadata
- https://ssdashapi.ventes.group/.well-known/oauth-authorization-server
Public clients use no shared client secret. Access tokens expire after 15 minutes. Refresh tokens rotate on use and the connection expires after 30 days unless you authorize it again. Use an HTTPS callback or a loopback callback for native clients.
Compatibility and app coverage
Clients must support remote MCP and a compatible OAuth registration or pre-registration flow. Adding an arbitrary HTTP URL as an MCP server is not enough. Browser-hosted clients can require additional origin configuration. A particular client or model is supported only after its connection flow has been tested.
The gateway exposes selected capabilities for connected applications, rather than every screen or action in the suite. Social publishing still depends on the social network’s permissions and account connections. Existing manually configured MCP connections remain available through the AI Dashboard.
For connection help, contact VentES with your client name and the error message.