MCP · Agents

MCP tools

The 38 tools of the Manybases MCP server, served identically by the remote connector and the local server. Each family has its own page with the full description, parameters and behaviour of every tool.

Plane says which host a tool reaches: management is api.manybases.com (the account's control plane), data is the project's own host (proj-<id>.manybases.com). Human says whether the tool needs a signed-in human in addition to the account key: always, conditionally, or never (—). What "human" means, and how a conditional gesture confirms, is in The human boundary.

Tool	Family	Plane	Human	Does
`create_project`	projects	management	—	Creates a project with its database, storage and users
`list_projects`	projects	management	—	Lists the projects the key can see
`get_project`	projects	management	—	The project card, with the address of its data plane
`get_usage`	projects	management	—	Usage and quotas
`set_app_url`	projects	management	always	Sets or clears the app URL, renames
`delete_project`	projects	management	always	Deletes a project and everything in it
`run_sql`	data	data	conditionally	Runs one SQLite statement
`apply_migration`	data	data	conditionally	Runs one DDL statement
`list_tables`	data	data	—	Lists tables, or describes one
`create_table`	data	data	—	Creates a table and declares its access preset
`set_table_preset`	data	data	conditionally	Changes who may see and write a table's rows
`query_rows`	data	data	—	Reads rows, one by id or a filtered list
`insert_row`	data	data	—	Inserts a row
`update_row`	data	data	—	Updates a row by id
`delete_row`	data	data	—	Deletes a row by id
`list_users`	users	data	—	Lists the app's end users
`delete_user`	users	data	always	Deletes an end user and their data
`reset_password`	users	data	always	Issues a password-reset link
`upload_file`	files	data	—	Uploads a file (base64, 25 MB)
`list_files`	files	data	—	Lists the files of a project
`delete_file`	files	data	—	Deletes a file
`list_keys`	keys	management	—	Lists a project's keys, never their values
`create_key`	keys	management	conditionally	Creates a `pk` or `sk` key (`sk` needs a human)
`rotate_key`	keys	management	conditionally	Rotates a key with a 24 h grace (`sk` needs a human)
`revoke_key`	keys	management	—	Revokes a key immediately
`get_logs`	logs	data	—	Reads the project's request log
`list_functions`	functions	management	—	Lists the edge functions
`deploy_function`	functions	management	—	Deploys or replaces an edge function
`list_function_secrets`	functions	management	—	The names of the secrets present on a function
`list_secrets`	functions	management	—	The names of the project's secrets and of the account's shared ones, with their dates
`rotate_function_secret`	functions	management	—	Rotates a function's own key
`delete_function`	functions	management	—	Destroys a function
`deploy_site`	site	management	—	Deploys a small hand-written site (30 files, 100 KB)
`list_site_deployments`	site	management	—	The history of a site, refusals included
`link_repo`	github	management	—	Links a GitHub repository to a project
`get_github_link`	github	management	—	Reads which repository is linked
`get_deploy_workflow`	github	management	—	The GitHub Actions workflow that deploys the site
`claim_site_subdomain`	site	management	—	Claims the site's readable address — permanent

Twenty-nine tools run on the key alone, four always need a human, five need one conditionally. The gestures that no tool exposes at all — and stay in the dashboard — are: setting a secret's value, managing the account's shared secrets, exporting a project, and connecting a GitHub account.

Every tool takes project_id (the proj_… id) except create_project and list_projects. Every refusal is rendered the same way — see Errors for agents.