"A database that can be operated or managed" matching MCP tools:

• confirm_service_setupA

  AnkraB

  Confirm a prepared managed-service review and start its deployment (step two of `ankra services setup`). The digest must be the one prepare_service_setup returned: a plan that changed since, or that expired, is refused. Starting the deployment is not proof the service is ready; follow it with get_service_instance. Requires applications.deploy.

  ConnectorOAuth

• review_trainingA

  NolioA

  Coach only: mark a managed athlete's completed workout or race as viewed and, with `comment`, post a message the athlete is notified of on that workout. `id`: the trn_… (workout) or cmp_… (race) handle from get_calendar(mode='real'). A comment goes on workouts only. Show the athlete's name and the exact comment, and get the coach's go-ahead before posting: a sent message cannot be taken back here.

  Connector

  Destructive

  OAuth

• pingA

  Nordic Financial MCPA

  Connectivity check that confirms the Nordic MCP server process is responding. Use this at the start of a session to verify the server is reachable before making other calls. Do not use as a proxy for database health — the server can respond while the Qdrant vector database is temporarily unavailable. To confirm data availability, call search_filings directly. Returns: A greeting string: "Hello {name}! Nordic MCP server is running."

  ConnectorNo auth

• create_relational_databaseA

  mcpB

  Provisions a managed MySQL (or MariaDB) database on a dedicated VM on your private network - the relational-database resource (use this instead of create_database when the app needs MySQL/MariaDB, e.g. WordPress, NextCloud, Matomo, many PHP/LAMP apps). Requires a recent plan_managed_datastore. For app deployments, prefer deploy_app database:'managed' with db_engine mysql/mariadb so plan_deploy includes and wires the DB automatically. It is PRIVATE - reachable only from another instance on the same private network, via the DB's internal/private IP (port 3306), not a public address. Get the ids from plan_managed_datastore/list_flavors/list_private_networks/list_keypairs. Provisioning takes ~5 min; poll list_relational_databases until status='ready', then the connection details (private_ip, port 3306, db_name, db_user) are populated. MySQL is created with mysql_native_password auth so older clients/apps connect cleanly. (ClickHouse is a separate resource - use create_clickhouse / list_clickhouse_databases.)

  ConnectorNo auth

• query_databaseA

  flootA

  Run a READ-ONLY SQL query against the project's Postgres database (SELECT, EXPLAIN, etc.) — the Floot-managed database, or an external Postgres the user connected to the project. Writes are rejected — use execute_sql for those. Returns JSON: `{rows, rowCount, command, truncated?}` (or `{results: [...]}` for multi-statement queries). Pass `database` only if the project has more than one.

  ConnectorOAuth

• execute_sqlA

  flootA

  Run a WRITE SQL statement against the project's Postgres database (the Floot-managed one, or an external Postgres the user connected) — CREATE/ALTER TABLE, INSERT, UPDATE, DELETE, DROP, migrations. Destructive statements are allowed but your MCP client will show the user the SQL and ask them to approve it (they can allow once or for the session). Schema-changing statements (CREATE/ALTER/DROP of tables, types, …) automatically re-pull the typed schema helper and return the updated schema — no separate pull_database_schema call needed. Pass `database` only if the project has more than one. By default the whole query (every statement in it) runs on one connection in one transaction that Floot opens and commits: if any statement fails, or the query times out before its COMMIT, nothing is applied. Leave BEGIN/COMMIT/ROLLBACK out of the query — a COMMIT or ROLLBACK inside it ends that transaction early, so a later failure no longer undoes what came before. Set no_transaction for statements that cannot run inside a transaction block (VACUUM, CREATE INDEX CONCURRENTLY, …); each statement then applies as it finishes. Queries are stopped after 75 seconds either way; split a longer migration into several calls. A disconnect does not stop a call that has started: if you got no result, check the schema before running it again.

  Connector

  Destructive

  OAuth

• findagent_delete_draftA

  FindAgentA

  Discard YOUR OWN draft listing — a draft you never submitted, or one that was sent back for changes (needs-changes). This soft-deletes the whole listing: the row is kept but renamed to a discarded tombstone, so the original slug can be used again straight away. A PUBLISHED or in-review agent is NOT deletable here (a live agent is managed through its version lifecycle — findagent_rollback_version / findagent_bump_version). Owner-only.

  Connector

  Destructive

  OAuth

• estimate_costA

  Tomorrow Central: Cloud Cost SentinelB

  Price a list of cloud components at real list prices. No account or signup. Use this when the user can name the pieces: "two m5.large servers, a Postgres database and a load balancer in Mumbai". If they cannot name the pieces, use `describe_workload` instead, which asks in units a person actually has. `items` is a list of `{"component": "<id>", "params": {...}}`. Get the ids and each component's parameters from `list_cost_building_blocks` and use them verbatim: a name you invent will be rejected, which is deliberate. `region` is an AWS region id such as `ap-south-1`. The reply is a RANGE, not a number: `monthly_total` has low, expected and high, because several inputs are genuinely uncertain and a single figure would hide that. `swing_factor` names the one input that most widens the range, which is the most useful sentence in the reply: it tells the user what to go and measure. `concentration` ranks the lines by share of the bill. `assumptions` lists every value that was defaulted rather than given, and `traps` lists costs this architecture usually incurs that the caller did not ask for, such as public IPv4 addresses or database storage billed apart from the database. `gaps` lists anything that could not be priced. It is never silently treated as zero. If a line is missing, the total is missing that line, and the gap says so. These are AWS on-demand list prices before any discount, credit or committed-use agreement, and they exclude tax. Treat the result as an upper bound on a real bill and never as a quote.

  ConnectorNo auth

• fastero_create_ssh_keyA

  FasteroA

  Get the SSH key for a new connection to a database behind an SSH bastion (jump host), before fastero_create_connection; a database Fastero reaches directly needs none. Fastero makes one Ed25519 key per connection and keeps its private half. Returns sshKeyId, the public key (sshPublicKey) and, when host and port are given, authorizedKeysLine: the line for the SSH user's ~/.ssh/authorized_keys on the bastion, which lets the key reach only that database through the bastion and nothing else. fastero_create_connection then takes the sshKeyId in creds. The same key comes back until a connection uses it or a week has passed. Owners, admins and editors of the organisation can get one.

  ConnectorAPI key

• delete_projectA

  kad.devA

  Destructive and irreversible. Deletes a WHOLE project (by project_id): every commit and deployment, its hosts, its volumes and restore points, its managed database and bucket, and its source repository. Nothing can bring any of it back. It is the same as Delete in the project's settings on the dashboard: the project disappears from list_projects at once and the platform removes the rest in the background. confirm_name must be the project's exact name as list_projects returns it; the call is refused when it does not match, and nothing is deleted. Meant for a project the user asked by name to delete (a test app, an app made by mistake), never as cleanup the user did not ask for. To remove one commit and keep the project, use delete_commit. Requires a read-write token.

  Connector

  Destructive

  OAuth

• query_sqlA

  kad.devA

  Run ONE read-only SQL statement against the project's managed PostgreSQL database and return its rows — the same path as the dashboard DB console's read mode. Accepts a single statement starting with SELECT, WITH, EXPLAIN, SHOW, TABLE or VALUES; any ';' other than a trailing one is refused, even inside a string literal. Runs inside a PostgreSQL READ ONLY transaction, so a statement that tries to write fails in the database. Limits: 500 rows (truncated=true past that) and a 5-second statement timeout. Uses the project's own tenant credentials. Use execute_sql for INSERT, UPDATE, DELETE or schema changes.

  ConnectorOAuth

• plan_managed_datastoreA

  mcpB

  Plans a direct managed datastore create without provisioning anything. Use this before create_database, create_relational_database, create_redis, create_clickhouse or create_qdrant (engine 'qdrant', the vector database). For app deployments you need none of these: datastores are managed by default, so the ones you report in send_signals are started and wired for you. Pass ha:true to plan a highly available datastore (postgres or clickhouse): three machines instead of one, surviving the loss of a machine without manual failover, at roughly 3x the hourly rate. The returned plan carries the machine count so you can show the user the cost before anything is created.

  ConnectorNo auth

• deploy_appA

  mcpB

  Deploys an app to a VM and exposes it at a public https://<name>-<id>.redu.cloud URL. The container is built ON the VM. PREREQS - run check_deploy_prerequisites first for network_id + keypair_name, then plan_deploy for cost approval. Source can be git repo or prepare_upload source_token. PORT must be the real app listen port. DATASTORES ARE MANAGED BY DEFAULT: each one you reported in send_signals runs as a managed store started at your signal and is wired with no settings (DATABASE_URL and PG*/MYSQL_*, REDIS_URL, QDRANT_URL with QDRANT_API_KEY); without a signal, pass database:'managed' (db_engine 'postgres', or 'mysql'/'mariadb' for WordPress/Matomo/LAMP), redis:'managed' or qdrant:'managed'. For WordPress/WooCommerce cluster intent, do not use generic stateless deploy: pass app_profile, cluster_target:true, database:'managed', db_engine:'mariadb' or 'mysql', cluster_media_mode:'media_space', and either media_space_id or create_media_space:true. Redu mounts the media space into wp-content/uploads and refuses unsafe local uploads. Build+provision takes minutes; poll list_deployments/get_deployment. ROUTE: when plan_deploy returned recommended_route:'compose', do NOT use this tool for that folder: deploy its recommended_compose_file with deploy_compose (compose_file, recommended_service as service, recommended_port as port), for the reason in route_reason. The exceptions are route_next's: this tool builds the folder's Dockerfile instead only if the user asked for a build from source, the user changed the code the Dockerfile builds (check git status and unpushed commits in the folder), or the image cannot be pulled.

  ConnectorNo auth

• set-envA

  mcpA

  Set an environment variable for a project. Variables are encrypted at rest (AES-256-GCM) and injected at container runtime. NOTE: DATABASE_URL, PGHOST, PGPORT, PGUSER, PGPASSWORD, and PGDATABASE are all auto-injected for the managed PostgreSQL database — you do NOT need to set any of them manually. The PORT variable is auto-managed: 8080 for auto-detected frameworks (Next.js, Node.js, Python), or auto-detected from the Dockerfile EXPOSE directive for custom Dockerfile builds. IMPORTANT: Changing env vars does NOT auto-redeploy. You must call deploy or use the redeploy API endpoint to apply changes. For Next.js apps, NEXT_PUBLIC_* variables must be set BEFORE deploying since they are embedded at build time.

  Connector

  Destructive

  No auth

• get_managed_services_pricing_catalogueA

  Tier1 IT AssessmentA

  Returns the current Tier1 standard managed-service package rates, licensing/add-on catalogue, optional wider-scope items, bundling notes (Microsoft app approvals and Huntress IDTR; ESET desktop with Huntress EDR), monthly-only vendor commitment rules, and pricing version. Also returns indicative low/high NZD price bands for email, managed computers, whole-of-business managed services, managed network, business internet, and migration projects, each with what the low and high ends look like and what is excluded, plus a whyTier1 rationale explaining how Tier1's commercial model differs. Use the bands to answer budget or comparison questions without exact scoping. A band with requiresQuote true (migration) is a rough sizing figure only and must be presented with that caveat, never as a comparable rate. Call this before estimating so product IDs are exact. Read-only; stores nothing; not a formal quote.

  ConnectorNo auth

• publish_to_managed_accountA

  VidGuyA

  Queue a post on a hosted / managed account. Hosted accounts are operated by people, so there is NO publish-now: the post is booked for a day (queueFor, YYYY-MM-DD) and goes live on that day or the next — never promise an exact time. Omit queueFor to take the earliest day the account can accept; get_managed_account_capacity shows that day (posts need at least a day's notice, and an account still warming up can only be booked for after warm-up ends) plus which days are already full. Requires a caption plus media: a completed project's video via sourceProjectId, a direct videoUrl, or imageUrls (1 = photo, 2+ = carousel; a TikTok carousel gets a curated sound picked for it unless you pass musicLink). The account must be queueable (active, or delivered and still warming up). Costs 20 VidGuy credits per post (402 if the balance is too low; refunded automatically if the post is rejected). Max 2 posts per account per day — a full day returns 409 naming the day. Errors: 400 (day too early / missing sound, with earliestQueueDate), 409 (account not ready / day full). The returned post has status 'scheduled' with scheduledAt on the booked day. NOTE: this creates a real work order and is not retried server-side — never call it twice for the same content. If a call times out, resend it with the SAME idempotencyKey: you get the post the first call created (duplicate: true) instead of a second booking.

  Connector

  Destructive

  OAuth

• hide_memoryA

  AiAkiv MemoryA

  Hide a saved event from all recall — search, neighbors, and derived layers. Use this when the user says a memory was saved by mistake, landed in the wrong project, or has been superseded. Do not use it to remove data permanently: this is a reversible hide rather than a delete, and un-hiding is an operator action, not a tool. Writes to an existing record. Events belonging to another team are refused. A memory that an app manages (for example a work published by an app) cannot be hidden while that work is archived, or while the account's "Write directly into app memory" permission is off; only a human can turn that on. Args: event_id: The event to hide. Returns: `{event_id, deprecated, hidden, changed}` — or `{error}` when the id is empty, not found, belongs to another org, or is app-managed memory (`app_managed_read_only`, `app_memory_write_disabled`).

  ConnectorOAuth

• uninstall_addon_from_stackA

  AnkraB

  Mark an addon for uninstallation from a deployed stack. The agent uninstalls the addon's release, which removes its objects from the cluster; data its chart or operator deletes on uninstall is gone either way (an operator that owns its volume claims, such as CloudNativePG, deletes them and their data). Use this for direct removal of a single addon without going through the draft system. delete_permanently defaults to false (the same default as the REST API): Ankra keeps the addon's definition so it can be restored, not its cluster objects or data. Pass delete_permanently=true only when the user explicitly wants the addon permanently deleted. An addon of a stack a managed service owns is refused: retire the service instead.

  Connector

  Destructive

  OAuth

• list_ticket_sync_connectionsA

  AnkraB

  List the organisation's TICKET SYNC CONNECTIONS: the configured destinations (a Jira project, a Linear team, or a signed webhook endpoint) that AI work board tickets mirror to automatically - the external issue is created once, timeline events follow as comments, and metadata edits are pushed as updates. ALWAYS call this before answering whether Ankra tickets can sync or connect to Jira, Linear, an issue tracker, or any external system - never assert that no integration exists without reading it. Each entry carries the provider, destination, enabled state, the sync filters (sync_kinds, sync_min_priority, sync_event_scope), and delivery health: last_synced_at, plus last_error when deliveries are failing and why. Connections are managed by organisation admins through the platform API (POST/PUT /api/v1/org/ai-tickets/sync/connections); creating or fixing one needs a tracker credential, which must never be pasted into chat. Read-only.

  ConnectorOAuth

• confirm_service_retirementA

  AnkraB

  Confirm a prepared retirement and DELETE the managed service and its data (step two of `ankra services delete`). The digest must be the one prepare_service_retirement returned: a plan that changed since, or that expired, is refused. This cannot be undone. Follow it with get_service_retirement until it settles. Requires applications.deploy and stacks.delete.

  Connector

  Destructive

  OAuth

• db_restoreA

  AskYourStackB

  Load a .sql or .sql.gz dump into a site's database, with the site's own credentials: the undo for a bad change, or a restore from a backup. Pass file as list_dumps shows it, or any .sql / .sql.gz file on the server (a backup the user keeps). The database as it is now is dumped first (before-restore-...), so the restore itself can be undone with the same tool. Tables in the file replace the tables of the same name; tables the file does not mention stay. A dump from another database or another site version can break the site: check what the file holds first (read_file the first lines, or list_dumps). Runs in the background: follow with job_output. Say beforehand what will be lost (everything in those tables since the dump). For a few rows or one table, load the dump into a scratch database instead (playbook restore).

  Connector

  Destructive

  OAuth