One tool registry
The CLI and the MCP server share one registry and implementation, so an agent cannot reach an operation the platform does not expose to you.
Product / Work with agents
Let coding agents work through CLI and MCP against the same governed backend contract your team controls.
The CLI and the MCP server share one registry and implementation, so an agent cannot reach an operation the platform does not expose to you.
Inspect exactly what an agent can see with a read-only tool list before connecting it to anything.
Writes, destructive operations, and external side effects require explicit approval rather than running on the model's word.
An agent session acts inside the workspace permissions granted to it, enforced by the backend rather than by the prompt.
Each entry links to its reference page, generated from the same documentation the CLI and the MCP server return.
getDocsRetrieves comprehensive API documentation for GSB Entity Service.
querySearches and retrieves entities based on complex criteria.
saveCreates new entities or updates existing ones.
The guide covers the working shape of this capability, including request payloads, limits, and failure handling.
Give AI-assisted teams a governed data model, query layer, and transactional save path instead of a hand-built backend.
Keep identity, tenancy, and deep permission policies enforced in the backend, not the interface.
Run business logic inside the tenant runtime without deploying an application server or server farm.
Compose durable, inspectable business processes instead of asking generated glue code to hold state.
Manage documents, PDFs, messages, files, and multilingual content as governed backend capabilities.