Integrations and access
Connect Claude and developer tools to Vesso
Use Vesso’s Model Context Protocol (MCP) server to look up customer context and perform permitted actions from your assistant. The endpoint is shared across compatible clients; the sign-in and configuration steps depend on the client.
Reviewed October 2026
Before you connect
- Your live, non-student workspace needs approved Public API access, and the API must be enabled for your deployment. Ask a workspace administrator to check Admin Settings → Integrations → API Access.
- Copy the MCP endpoint shown in that panel. Use the endpoint from your workspace, including its /mcp path.
- Choose the smallest set of scopes needed for the workflow. Start with read access to test the connection, then approve writes only when needed.
Connect Claude with a Vesso sign-in
- In Claude web or Claude Desktop, open Settings → Connectors and add a custom connector.
- Name it Vesso and paste the MCP endpoint from API Access.
- Follow the Vesso sign-in flow. Check the workspace, client name, and requested permissions on the consent screen before approving.
- Enable the connector for a conversation if your client requires it. Ask for a specific account or your open tasks and check the result against Vesso.
Connect Claude Code, Cursor, or VS Code
- In API Access, create a dedicated API key with the required scopes. Copy the secret when it is displayed and store it securely.
- Open the MCP setup panel and select your developer tool. Copy its generated configuration with your actual endpoint.
- For Claude Code, add a remote HTTP server. For Cursor, use the mcpServers configuration. For VS Code, use the servers configuration with HTTP transport.
- Supply the API key as an Authorization: Bearer header using the client’s secret or environment configuration. Reload the MCP server and confirm that the expected tools appear.
- Test a read operation before enabling a workflow that creates or updates records.
claude mcp add --transport http vesso https://YOUR_API_HOST/mcp --header "Authorization: Bearer YOUR_API_KEY"ChatGPT, Gemini, and other clients
Vesso also exposes the same remote MCP endpoint for compatible ChatGPT apps, Gemini apps, Gemini CLI, and other MCP clients. Choose the client’s remote MCP connection flow and review its account eligibility, transport, and authentication support. A model provider alone does not guarantee that every app from that provider supports custom MCP servers.
Client options and availability →If the connection does not work
- If sign-in succeeds but access is denied, check workspace approval, active membership, and the deployment’s API availability.
- If a tool is missing, compare the connection’s scopes with the tool category. Vesso only lists tools the credential may use.
- If a key is expired or revoked, replace it in the client. If OAuth permission has been revoked, reconnect and approve a new grant.
- Use a native or server-backed client. Browser-direct clients that require cross-origin OAuth requests are not supported by the current endpoint.