An assistant through MCP
What an assistant can read or change as an area owner or a global administrator.
DBMap 0.20.0 · Updated · The editor uses Russian UI labels, shown as written.
Connection and permissions
Open API and MCP in the account menu to create a key, or connect OAuth in ChatGPT/Codex. New grants default to off. Existing keys and connections are never expanded automatically: create a new key or reconnect OAuth and select the required checkboxes. account_get returns your own identity and connection grants. Refresh the tools in your client for this release.
Descriptions, links and sheets
analysis_get reads tasks, views and sheets. analysis_batch update_task edits description and externalLinks: tracker, mergeRequest and swagger. Link keys are independent patches; null removes one. add_task_note prepends a journal entry. sheets_commit saves the full sheet: coordinates, groups, pinning, filters, navigation, fields, FK/JOIN and notes. Read the current version first and preserve other fields. Re-read on conflict; reuse mutationId only for the identical request.
schema_get/schema_import handle metadata, descriptions_update edits common or contextual explanations, and table_example_get/set handles fictional examples only. Screenshot access requires separate screenshots:read/write grants. source_get/update requires the current owner and source:manage; source databases remain metadata-read-only.
Owner sharing
A registered owner can grant access:manage together with write access. area_members_list lists existing members or resolves one exact full email. area_member_set grants read/edit access or removes the owner grant, guarded by expected state. Editors and global administrators without ownership cannot change owner sharing. Administrative assignments remain independent.
Global administrator
Only a global administrator can approve admin:read/admin:write; select all accessible areas. admin_users_list returns names, emails, avatars and flags. admin_user_update promotes/demotes or blocks/unblocks accounts. The last active administrator is protected. admin_user_areas_list/set manages separate administrative area assignments. admin_errors_list/get reads sanitized 4xx/5xx diagnostics. Current roles and bans are checked on every request; an old key never retains removed administrator privileges.
Help and boundaries
help_search searches the actual public guide; help_read retrieves a selected page in bounded Russian or English chunks. The editor help uses the same source text as its UI dialog. Area metadata and documents never include source credentials, screenshots or example records.
Sign-in, secret key issuance, OAuth consent and recovery of a lost private channel proof remain human browser actions. An assistant cannot expand its own connection or obtain another channel proof. Browser tabs, file downloads and local drafts belong to the device; saved content is available as documents or view_render. Private discussions require the assistant’s own verified channel. Public site chat is separate; posting requires community:write and an explicit publication request, and moderation requires a global administrator with admin:write.
Next: DBMap documentation
Related materials: MCP, REST and AI integrations · Collaboration and roles