Tools Reference

Tools: Projects & References

Each MCP connection is bound to one project, determined by the API key you connect with. Project lifecycle — creating a project (where the backend framework is chosen), archiving, reactivating, and setting the git remote — lives in the portal, not the MCP surface. Create an API key for a project on the API Keys page and connect with it; every project-scoped tool then applies to that project automatically, so you never pass project_id.

The tools below fetch reference metadata for the bound project and rebuild its preview. project_id is optional on all of them — omit it to use the connection's project.

zeeb_get_project_reference

Return the full backend reference bundle for the bound project: metadata, preview/runtime/OpenAPI URLs, deployment readiness, and the workspace-file descriptor in one call. This is the preferred resume/sync tool — call it after connecting and after backend changes.

zeeb_get_project_reference(project_id: str = "") → str

Returns: JSON with the project reference, warnings, and next steps.

zeeb_get_preview_url

Get the live preview URL for the project. The preview is always-on and auto-restarts.

zeeb_get_preview_url(project_id: str = "") → str

Returns: The HTTPS preview URL, e.g. https://<project-uuid>.preview.zeeb.cloud

zeeb_get_public_api_url

Get the runtime HTTPS API base URL for the project. Use this when building frontend integrations.

zeeb_get_public_api_url(project_id: str = "") → str

zeeb_get_openapi_url

Get the OpenAPI schema URL for the project. Returns the live endpoint that serves the current OpenAPI JSON.

zeeb_get_openapi_url(project_id: str = "") → str

zeeb_get_api_client

Get a ready-to-use frontend API client module for the project — authentication, automatic token refresh, and CRUD helpers matched to the project's backend contract, with the runtime API base URL baked in.

zeeb_get_api_client(project_id: str = "", language: str = "typescript") → str

Arguments:

Name	Type	Description
`project_id`	string	UUID of the project (omit to use the bound project)
`language`	string	`typescript` (default) or `javascript`

Returns: JSON with file.path, file.content (the complete module source), the runtime API base URL, warnings, and next steps. Write file.content to file.path in the frontend workspace.

zeeb_get_workspace_reference

Return the workspace resume file content for the project. Write workspace_file.content to file_path so a later session can resume without re-fetching URLs.

zeeb_get_workspace_reference(project_id: str = "", file_path: str = "zeeb/backend_reference.json") → str

zeeb_redeploy_preview

Rebuild the preview now. Forces an immediate rebuild: the preview service re-clones the current HEAD of the project's git remote and recreates the runtime container. Every project-scoped tool call already commits and pushes automatically and the preview auto-polls the remote — this just skips the wait. Also use it to recover a preview whose runtime crashed or whose last build failed.

zeeb_redeploy_preview(project_id: str = "") → str

Returns: The resulting preview status. Check lifecycle_state is running before testing.

Notes

project_id is optional everywhere — the connection is bound to one project by its API key.
Projects are isolated per tenant — a key can only touch its own project.
To work on a different project, connect with an API key created for that project.