For developers
API → MCP
Use the same integrations, permissions and approvals from AI clients and your own applications.
Remote MCP
https://vezista.io/mcpStreamable HTTP, OAuth with PKCE, dynamic client registration and permission-scoped tool discovery.
Connect using OAuth, then choose a workspace and permission profile on the consent screen.
REST API
https://vezista.io/api/v1/toolsCreate a scoped token in your workspace. Tool schemas and permitted actions are returned by this endpoint.
curl https://vezista.io/api/v1/tools \ -H 'Authorization: Bearer YOUR_TOKEN'
One execution policy
A write requires an idempotency key. An action awaiting approval returns an approval URL; it runs only after an authorized person approves the exact request.
Poll the invocation endpoint or use get_invocation over MCP for the result. A queued or pending action is not a successful action.