AnyDB

Create a View on a type's listing page, so a person opening that type in AnyDB sees it next to All. This is what someone means by "a view showing only X" - the named filter they can see and click at the top of the type page. View names are unique per type; creating a duplicate name is rejected rather than silently merged.

anydb_create_view

Read the authoring guide, then call anydb_list_workflow_triggers and anydb_list_workflow_actions before authoring. Create one supported trigger followed by an ordered chain of registered actions. Prefer one script action when the team license permits it and that is the simplest design. Use action keys and symbolic output bindings; the server generates runtime artifact IDs and connections. For an action_script, follow the guide's Script Actions rules and the action_script catalog guidance: an executable body with no async IIFE, documented anydb/output APIs only, awaited data and mutation calls, an await in every loop body, exact schema field casing, epoch-second dates, and explicit output.set/output.summary results. The server validates script source before persisting it, so use validateOnly to check a draft. After creation, run one representative case and inspect anydb_get_workflow or anydb_get_workflow_execution_history before considering the automation verified.

anydb_create_workflow

Create a new empty AnyDB workspace in an existing team. Use only when the user explicitly requests a new workspace. The authenticated user must have permission to create workspaces in the team. Use the returned adbid in subsequent type, View, share, workflow, and record tools.

anydb_create_workspace

Remove a Document Generation template from a database. This deletes the mapping, not the uploaded template file - the File record stays and can be attached again. Permanent otherwise.

anydb_delete_docgen_template

Delete or unlink an existing AnyDB record. Records can have multiple parents - you can either unlink the record from specific parent(s) by providing their IDs in removefromids, or permanently delete the record by passing '000000000000000000000000' (NULL_OBJECTID). If removefromids is not specified, the record will be permanently deleted by default.

delete_record

Delete a saved report and every snapshot computed for it. Not reversible.

anydb_delete_report

Remove a View from a type's listing page. Permanent, and it takes that View's saved columns and sort with it. The All view cannot be deleted: it holds the default sort and column layout for the whole listing page.

anydb_delete_view

Retrieve semantically plausible reusable AnyDB type candidates before designing a new type. For authoring, search source=workspace first; search source=builtin only when no workspace candidate is compatible. Candidate names, descriptions, categories, and ranking are hints, not proof of compatibility: call anydb_get_type_definition for plausible candidates and compare their complete fields, schema, relationships, formulas, and behavior with the requested role before reuse or import. Use source=all only for general exploration.

anydb_discover_types

Export the last ready snapshot of a report as a file. format csv returns the CSV text; format xlsx returns the workbook as base64 with its filename. Refused until a snapshot is ready - run the report first.

anydb_export_report

Finalize a signed-URL upload once the PUT has succeeded. Pass the adoid that prepare_file_upload returned - the File record it created - not the parent adoid you gave prepare_file_upload, and the same filesize and cellpos. Until this is called the File record exists but has no usable content.

complete_file_upload

Generate a document from one record using a Document Generation template, and attach the result to that record so it can be downloaded, emailed or sent on. This is the tool that actually produces the PDF - the other docgen tools only configure which template applies to which type. REGENERATING REPLACES: running this again with the same template on the same record supersedes the previous output rather than adding a second file, so a record never accumulates a pile of near-identical documents. Replacement is per template, so generating a Quote does not remove an Invoice generated from a different template on the same record. The result is an ordinary File record: pass the returned fileRecordId and cellPosition to download_file to fetch the bytes. If the generated document comes back with blanks where values should be, the template's placeholders do not match the record's fields - a tag naming nothing renders empty rather than failing. See anydb_create_docgen_template for the merge-tag syntax.

anydb_generate_document

Download a file or get download URL from a record cell. Returns JSON with a 'url' field containing a presigned file link. Normal file URLs expire after approximately 60 seconds: fetch immediately and do not cache or reuse them. The MCP client/host should render the URL as a link for humans or fetch its bytes for LLM processing. First use get_record to find file cells and their cellpos values.

download_file

Read one installed app (plugin) in full: everything anydb_list_apps shows for it plus its recent activity log (events: health checks, status changes, grant and version updates, refused calls) newest first. Read-only: installing, updating to a newer version and changing grants are the team owner's actions on the Apps page.

anydb_get_app

List what is in YOUR Inbox for a team - the records assigned to the authenticated user, which is the same list the Inbox in the AnyDB app shows. Use it to check that an assignment you made through update_record actually landed, or to see what is waiting on you. A record gets here through meta.assignees on update_record; each entry says whether it was assigned to you directly or through a group you belong to. This reads your own Inbox only: there is no way to read another person's. The list is self-correcting, so a record that was deleted or reassigned away simply is not in it.

anydb_get_inbox

Get a specific AnyDB record by its fully qualified address (teamid, adbid, adoid). A whole record is tens of KB (its dependency graph, permissions and every cell with its props); pass fields, and values: true, to read only the cells you need.

get_record

Report what a user may do with a team, database, or record: read it, update it, delete it, add records underneath it, and share it. Omit userid to ask about the authenticated user. Read the `can` block for the answer; the raw permission matrix is included for detail. Note that being able to update a record and being able to add records under it are independent — see anydb://guides/permissions/v1.

anydb_get_permissions

Fetch a record as it stood at one point in its history, in the same shape get_record returns. This is how you read content that no longer exists on the record - an overwritten cell, or comments removed by a migration. Pass a ts taken from anydb_list_record_versions; a timestamp that matches no version is REJECTED rather than answered, because the underlying replay would otherwise hand back the record as it is today and you would have no way to tell.

anydb_get_record_version

Read one report's complete definition. Returns an error if the id is a record that is not a report.

anydb_get_report

Read the last computed result of a report without re-running it. Without groupIndex: { reportId, manifest, groupsPage, groupDetailsPages } - manifest carries status (pending | running | ready | failed), totalGroups, totalMatchedRecords, isTruncated and grandTotal (metric alias -> number); groupsPage.groups are the grouped rows with their subtotal; groupDetailsPages holds the first detail rows of each group (omit with skipDetails). With groupIndex: one group's detail rows, paged by start and limit. Before the first run the shape is empty but valid (no groups), not an error.

anydb_get_report_result

Return the AnyDB MCP installation, API-key, client configuration, verification, and troubleshooting guide. This tool is available even when AnyDB credentials are not configured.

anydb_get_setup_guide

Get one accessible record or form share facet by shareId and kind. The kind is required because one internal share can contain both facets.

anydb_get_share

Fetch the canonical AnyDB solution-building guide for designing types, cells, relationships, formulas, and workflows. Call this once before any authoring work to understand rules for standalone types, multi-type solutions, relationships, formulas, and workflow creation.

anydb_get_authoring_guide

Get a database template (type) by templatename, including its cell keys, positions, formats, and properties. The terms templatename and typename mean the same thing.

get_template

Get the latest complete definition of a workspace or built-in type by its stable name. Use it to judge reuse from semantic content and behavior, not the candidate name, description, or search score. Use the candidate name returned by anydb_discover_types, never a version-specific template ID. A workspace definition also returns revision, the value anydb_update_type takes as expectedRevision.

anydb_get_type_definition

Poll a queued type migration by the jobId returned from anydb_update_type. Returns processed, total, and remaining record counts from cached job progress without rescanning workspace records. READ success AND errors, not status alone: a migration that could not move some records still ends as status Completed with success false and errors > 0, and message then names the count and the first refused record and why ("N of M record(s) could not be migrated; first: record <adoid>: <reason>"). Those records stay on the previous revision; fix the cause and use anydb_update_type again or the retry route rather than reporting the type as migrated.

anydb_get_type_migration_status

Get one workflow's normalized trigger/action graph and retained execution records, including per-artifact status, outputs, and errors. Each action's stored config is returned, so an action_script entry exposes its current source at config.script; read it before reviewing or revising that script rather than inferring behavior from the workflow name. Use this to diagnose whether a workflow fired and what happened, including script diagnostics at executionHistory[].artifactExecutions[].output.logLines. Use a workflowId returned by anydb_list_workflows or anydb_create_workflow.

anydb_get_workflow

Get the retained execution records for one workflow, including per-artifact status, outputs, and errors. Returns an empty array when the workflow has not run. Use a workflowId returned by anydb_list_workflows or anydb_create_workflow.

anydb_get_workflow_execution_history

Get all ADBs (databases) for a specific team. An ADB is like a spreadsheet file or a database table containing records. Use this to discover available adbid values within a team.

list_databases_for_team

List the Document Generation templates set up in a database - the .docx/.xlsx templates a person can generate a filled document from, shown under Document Generation in the AnyDB app. Each entry gives its id, its name, the workspace type it applies to (templateName), and the File record holding the template (fileAdoId). Call this before creating one to avoid a duplicate, and to find the id that update and delete take. Note the product also calls this feature "formatted export" internally, so that is the wording you will see in server logs and URLs.

anydb_list_docgen_templates

List the apps (plugins) installed for a team, as the Apps page shows them: pluginId, name, the pinned manifestVersion, status (active | needs_configuration | needs_attention | update_available | incompatible | unreachable | paused | disabled) with its reason, updateAvailableVersion when a newer version is registered (the team's owner updates it from the Apps page - this tool cannot), granted scopes, allowed types, last health, and each connection with the workspaces it is bound to. Pass adbid to keep only the apps bound to that workspace. Read this before concluding an app is broken: not installed, not bound here, unhealthy and behind a version are four different problems.

anydb_list_apps

List the saved versions of a record - every point at which it was changed, with the timestamp and who changed it. Use it to answer "what happened to this record", and as the first step in recovering content that was overwritten or lost: the timestamps it returns are the only values anydb_get_record_version accepts. NOTE THIS NEEDS DELETE PERMISSION ON THE RECORD, not just read - the server treats history as a stronger privilege than the current content, so a caller who can read a record may still be refused here.

anydb_list_record_versions

List ADOs (records) in a database. Use parentid with a normal record ID to list its children. You can also filter directly by template and use pagination for large result sets. Pass fields (e.g. ["adoid","name"]) to get only those keys per record: a full record header is a few KB and a hundred of them exceed the response cap.

list_records

List the saved reports in a database, with their ids and names. Call this before creating one so an equivalent report is reused rather than duplicated.

anydb_list_reports

List accessible shares in a database as semantic record/form facets, including target, privacy, recipient counts/groups, and publicUrl where applicable. Call before creating a share to avoid duplicate public links.

anydb_list_shares

List team groups available to the authenticated user for private sharing. Use the returned stable group names in anydb_create_share; do not guess names or pass internal group IDs.

anydb_list_team_groups

List the teams this connection can access, as teamid, name, and plan. A team is like an organization or workspace with its own databases and users. Use this first to discover available teamid values for other operations. Access control and policy detail are omitted; ask for them only if you genuinely need them, as they are large.

list_teams

List the templates (types) available in a database. Use this to discover templatename values and cell schemas before creating or updating records.

list_templates

List the Views on a type's listing page - the strip reading All, and whatever named filters sit beside it, that a person sees when they open the type in AnyDB. That strip is what a View is in AnyDB: the thing a user creates, names, and clicks. Use this when the user asks what views or saved filters they already have on a type, or to check that a View you created actually landed.

anydb_list_views

List registered workflow actions with descriptions, exact input/output schemas, trigger compatibility, and whether each action is accepted by anydb_create_workflow. The action_script entry carries the authoritative script runtime surface for the running server: allowed globals, anydb APIs, output APIs, record helpers, trigger-input binding, debugging, and authoring rules. Read it before writing or revising any script source, and prefer it over remembered API names.

anydb_list_workflow_actions

List server-supported workflow triggers with descriptions, output schemas, and whether each trigger is accepted by anydb_create_workflow. Each inputSchema is the exact object shape accepted at workflow.trigger.config; use those property names directly. Call before choosing a workflow trigger.

anydb_list_workflow_triggers