Records, Search, and Access Tools

Use these tools to identify the current connection, find teams and workspaces, inspect schemas, manage records, search content, check access, and collaborate through assignments and comments.

Connection and setup

Tool	What it does
anydb_get_setup_guide	Returns the MCP setup, verification, and troubleshooting guide even when no AnyDB credentials are configured.
anydb_whoami	Reports the active AnyDB identity, authentication method, OAuth scopes, client, and server without revealing credentials.

Use anydb_whoami before acting on data when the connected account is uncertain or results appear to belong to another account.

Teams, workspaces, Inbox, and permissions

Tool	What it does
list_teams	Lists accessible teams with their IDs, names, and plans.
list_databases_for_team	Lists the AnyDB workspaces available in a team.
anydb_get_inbox	Lists records assigned to the authenticated user, directly or through a group, for one team.
anydb_get_permissions	Summarizes what a user may do with a team, workspace, or record and returns the detailed permission matrix.
anydb_check_permissions	Checks specific permission and access-level pairs for a user and target.

Call list_teams first to discover teamid, then list_databases_for_team to discover adbid. An Inbox belongs to a team and only returns the authenticated user's assignments.

Templates and records

Tool	What it does
list_templates	Lists the templates, also called types, available in a workspace.
get_template	Gets a template schema by stable templatename, including cell keys, positions, formats, and properties.
list_records	Lists records with pagination and optional parent, type, structured filter, and View filtering.
get_record	Gets one complete record using its team, workspace, and record IDs.
create_record	Creates a record, optionally using a type and one or more parents.
bulk_create_records	Creates up to 100 records with an ordered result for every input.
update_record	Updates record metadata, assignments, parents, and partial cell content.
bulk_update_records	Updates up to 100 records with an ordered result for every input.
delete_record	Permanently deletes a record or detaches it from specified parents.
copy_record	Copies a record and can omit, link, or duplicate file attachments.
move_record	Reassigns a record to one parent and removes all other parent connections.

Record relationships

AnyDB records can have more than one parent:

• create_record.attach accepts one parent ID or an array of parent IDs.
• update_record.meta.attach replaces the complete parent list. Include every parent that must remain connected.
• move_record is a single-parent reassignment and detaches every current parent.
• delete_record.removefromids detaches specified parents without deleting the record.

Bulk operations

Bulk create and update calls use bounded concurrency and partial-failure behavior. A failed input does not roll back successful inputs. Add clientref values when you need to correlate each input with its result.

Structured record filters

list_records supports metadata, badge, and template-field filters. For example:

{
  "teamid": "team-id",
  "adbid": "workspace-id",
  "templatename": "Task",
  "filter": [
    { "type": "cell", "field": "{{Status}}", "op": "eq", "value": "Done" }
  ]
}

Search

Tool	What it does
search_records	Searches record text by keyword in one workspace, with optional parent filtering and pagination.
search_team_records	Searches every accessible workspace in a team and groups results by workspace.
anydb_semantic_search	Searches authorized records in one workspace by content meaning and returns ranked records with matching chunks.

Semantic-search scores are relative hybrid ranking values, not probabilities. Check the returned mode and warnings before relying on a degraded lexical-only or dense-only result.

Comments

Tool	What it does
anydb_add_comment	Posts a record-level or cell-level comment as the authenticated user and supports user mentions.
anydb_resolve_comment	Resolves or reopens an existing record-level or cell-level comment.

For a cell comment, use the same cellPosition when resolving it. Record-level lookup does not find comments attached to individual cells.