Choose work for Zanbase Agent
Learn which workspace jobs Zanbase Agent can help with and how its tools and your permissions limit each request.
Integrations
Cursor
Connect Cursor through Zanbase’s MCP server to read and change workspace information with your permissions.
What you can do
Connect Cursor to request Zanbase workspace actions through Model Context Protocol (MCP). The connection gives an outside tool a way to work with resources your Zanbase account can access.
The MCP server exposes a set of read and write actions. Available actions depend on the tool surface and any configured restriction for the client. Requests run with your permissions and the workspace’s sign-in requirements. An action requiring interactive approval is excluded from this surface, so connecting an outside tool does not expose every action available to Zanbase Agent in chat.
Permissions and privacy
You authorize the app through Zanbase’s OAuth consent screen. Under Workspace, choose the workspace whose id is in the server URL; selecting Allow authorizes the app for that one workspace, within your permissions and that workspace’s sign-in rules, and it reaches no other workspace you belong to. If you choose a different workspace, the server URL refuses the app’s access and you connect again. To use another workspace, add a second server with that workspace’s id and authorize it there. Choose Deny if you do not want to connect it. Zanbase stores the app registration, your consent and authorization-token records so it can identify and revoke the connection.
To review access, open Settings, then Connected apps, and find the Connected apps table. It lists the apps you authorized: App shows each app’s name, Workspace the workspace it is authorized for, and Connected your earliest authorization date. Select Disconnect beside the app and confirm Disconnect to revoke your authorization in that workspace. Zanbase deletes your access tokens, refresh tokens, consent and tool restrictions for that app in that workspace; your authorizations in other workspaces and other people’s authorizations remain intact.
Good to know
Cursor’s MCP documentation covers mcp.json and sign-in for remote servers.
This MCP connection does not let the outside app use your connected Google, Microsoft or GitHub accounts. Those connections have their own permissions. For a separate workflow inside Zanbase, see what Zanbase Agent can do.
Capabilities and permissions
- Reads: Read workspace information through the available MCP tools, within your permissions. Each person authorizes the app for their own Zanbase account.
- Writes: Change workspace information through available MCP actions that do not require interactive approval, within your permissions. Each person authorizes the app for their own Zanbase account.
Setup
- In Cursor, open .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project, and add a server under mcpServers, such as zanbase, with its url set to https://data-rest.zanbase.com/api/mcp/WORKSPACE_ID.
- Replace WORKSPACE_ID with the first part of the path after workspace.zanbase.com/ while you are inside your Zanbase workspace.
- When Cursor asks you to sign in to the server, continue to Zanbase in your browser. Cursor registers itself with Zanbase as an OAuth client.
- Sign in to Zanbase when prompted. On the wants access screen, check the app name, then under Workspace choose the same workspace whose id is in the server URL: Allow authorizes it to read and write in that workspace only, within your permissions and its sign-in rules.
- Select Allow to authorize the app, or Deny to decline.
- In Zanbase, open Settings, then Connected apps. Review the app in the Connected apps table, where App shows its name and Connected your earliest authorization date.
