Workspace and Type Tools

AnyDB MCP can build one standalone type or a coordinated solution with multiple types, relationships, formulas, Views, shares, reports, and workflows.

Available tools

Tool	What it does
anydb_get_authoring_guide	Returns the canonical rules for designing types, cells, relationships, formulas, and workflows.
anydb_discover_types	Finds plausible reusable types in the current workspace, built-in catalog, or both.
anydb_get_type_definition	Gets the latest complete definition of a workspace or built-in type by stable name.
anydb_create_workspace	Creates a new empty workspace in an existing team.
anydb_create_type	Defines a new type or imports a compatible built-in type.
anydb_update_type	Updates type metadata, fields, layout, title formula, badges, or child policy and migrates existing records.
anydb_get_type_migration_status	Polls the queued record migration started by a type update.

Recommended authoring sequence

1. Call anydb_get_authoring_guide before the first authoring operation.
2. Search workspace types with anydb_discover_types using source: "workspace".
3. Inspect plausible candidates with anydb_get_type_definition and compare fields, relationships, formulas, lookups, and behavior.
4. Search built-in types only when no compatible workspace type exists.
5. Reuse or import compatible types before defining new ones.
6. Create dependent types before types that reference them.
7. Add Views, shares, reports, and workflows only after their target types exist.
8. Validate the result with representative records and workflow executions.

Candidate names and rankings are discovery hints, not proof of compatibility. Inspect the full definition before reusing or importing a type.

Safe authoring

Authoring mutations support a stable clientRequestId. Reuse the same value only when retrying the identical intended operation. Use validateOnly: true where supported to validate without saving.

Type updates require the expected revision. Destructive field changes also require explicit data-loss confirmation. When anydb_update_type returns a migration jobId, poll anydb_get_type_migration_status until all existing records have been processed.

Stable names and formulas

Use stable type names and field keys in authoring inputs. Template IDs identify individual revisions and should not be used as semantic identifiers.

A type's titleFormula names records from their field values. It must be an AnyDB expression that returns a string. For example:

CONCAT('Meeting: ', {{Subject}})

Use {{Field Key}} to reference fields. Grid positions are only valid in formula functions that explicitly accept them.

MCP resources and prompts

The server also publishes supporting resources and prompts:

Resource or prompt	Purpose
anydb://guides/setup/v1	Connection, configuration, verification, and troubleshooting guidance
anydb://guides/permissions/v1	AnyDB permission names and behavior
anydb://guides/solution-building/v1	Solution-design and authoring rules
anydb://schemas/solution-authoring/v1	Machine-readable authoring schemas
design_anydb_type	Plans one standalone type
design_anydb_solution	Plans a coordinated multi-type solution
author_anydb_workflow_script	Authors or reviews a workflow script action