"Help with creating and importing data into spreadsheets/tables" matching MCP tools:

• list_sheetsA

  MilaA

  List all spreadsheets (sheets, excel, workbooks) with their tab metadata (no cell data). Use this when asked to list, find, or search spreadsheets, workbooks, tables, or tabular data.

  ConnectorNo auth

• list_sheetsA

  MilaA

  List all spreadsheets (sheets, excel, workbooks) with their tab metadata (no cell data). Use this when asked to list, find, or search spreadsheets, workbooks, tables, or tabular data.

  ConnectorNo auth

• vibekit_db_queryA

  VibeKitA

  Run a read-only SQL query against an app's Postgres database and return up to 200 result rows. SELECT only — writes and DDL (INSERT/UPDATE/DELETE/ALTER/DROP/…) are rejected server-side; use vibekit_chat or vibekit_submit_task to have the agent make data or schema changes. Call vibekit_db_schema first to learn the tables. SQL string, max 5000 chars.

  ConnectorNo auth

• adopt_compute_instanceA

  BorealHostB

  Turn an instance you are ALREADY running into a persistent volume. Use this when you launched something, set it up, and then decided you want to keep it. Nothing reboots and no data moves — the machine you have becomes the volume, and you can detach it afterwards to stop paying for compute while keeping the machine. Beats creating a volume and rebuilding. Only instances launched with an ssh_public_key qualify. One launched with your own user_data carries only your key, and a key cannot be added to a machine we cannot already log into — check "managed_ssh" on the instance. Requires: API key with write scope, and an active subscription. Args: instance_id: A running lsw.* instance you own name: Label for the volume (defaults to the instance name) Returns: Volume dict with state "attached", wrapping that same instance. No snapshot exists yet — the first one is taken on detach or snapshot. Errors: CONFLICT: Not running, already a volume, BorealHost Metal, or launched without BorealHost management access

  ConnectorNo auth

• list_mailboxesA

  Mailbox MCPA

  List every IMAP folder in the account, with the special-use role of each where the server reports one. `selectable: false` marks a hierarchy node that organises other folders but cannot itself hold a message: move_email will not file INTO one and delete_email will not read OUT of one, so do not offer either. create_folder DOES accept one as a `parent`, because creating a folder underneath a placeholder is exactly what turns it into a real folder, and a mail client would do the same.

  ConnectorOAuth

• execute_queryA

  BorealHostB

  Run ONE bounded read against a site's database. One statement, beginning with SELECT, SHOW, DESCRIBE or EXPLAIN, with no second statement and no data-modifying clause anywhere in it. The container proves the statement is a read before running it and caps the result: 200 rows by default, 1000 maximum, 2 MB of cell data. `truncated` in the response says whether a cap was reached. ⚠ THIS TOOL CANNOT CHANGE ANYTHING, AND RETRYING WITH DIFFERENT WORDING WILL NOT MAKE IT. Anything that is not a single bounded read is refused with READ_ONLY and nothing runs. To change data or schema, use the tool for the job: optimize_database, database_search_replace, manage_db_user, list_databases, list_tables — and for creating, altering, dropping, importing or exporting tables, the database manager in the control panel, which has no tool here. Requires: API key with write scope (unchanged — the scope is the customer's published permission for this operation, not a claim about what it does). Args: slug: Site identifier database: Database name query: One read statement Returns: {"columns": ["id", "user_email"], "rows": [[1, "a@example.com"], ...], "row_count": 1, "truncated": false, "execution_time_ms": 12.0} Errors: READ_ONLY: Not a single bounded read. The error text carries the explanation and names the operation to use instead.

  ConnectorNo auth

• how_munimji_helpsA

  HelloBooks AI AgentsA

  Explain how HelloBooks and Munimji (the in-app AI assistant) help a specific business — given a free-text description of the user's own operations. Returns a curated capability knowledge base: business-operation areas (sales, purchases, banking, tax, reports, inventory, payroll, multi-entity, setup), and for each AI capability WHO does the work — `autonomous` (Munimji does it on its own, e.g. OCR extraction, running reports), `approval` (Munimji prepares the entry and you one-click approve before it posts to the ledger, e.g. AI categorization, find-and-match, creating invoices/bills by chat), `assist` (co-pilot, e.g. guided onboarding, voice), or `manual` (a software feature you run yourself). Each capability links to the backing software features. Use this when a user describes their business and asks "how can HelloBooks help me?", "what can the AI do for my shop/practice/agency?", or "what can Munimji do on its own vs what do I approve?". Pass their description in `businessDescription`; optionally filter by `area` or `autonomy`. The AI never posts to a ledger without approval. For the full software catalog call list_features; for pricing call list_plans.

  ConnectorNo auth

• how_munimji_helpsA

  HelloBooks AI Agents MCP ServerB

  Explain how HelloBooks and Munimji (the in-app AI assistant) help a specific business — given a free-text description of the user's own operations. Returns a curated capability knowledge base: business-operation areas (sales, purchases, banking, tax, reports, inventory, payroll, multi-entity, setup), and for each AI capability WHO does the work — `autonomous` (Munimji does it on its own, e.g. OCR extraction, running reports), `approval` (Munimji prepares the entry and you one-click approve before it posts to the ledger, e.g. AI categorization, find-and-match, creating invoices/bills by chat), `assist` (co-pilot, e.g. guided onboarding, voice), or `manual` (a software feature you run yourself). Each capability links to the backing software features. Use this when a user describes their business and asks "how can HelloBooks help me?", "what can the AI do for my shop/practice/agency?", or "what can Munimji do on its own vs what do I approve?". Pass their description in `businessDescription`; optionally filter by `area` or `autonomy`. The AI never posts to a ledger without approval. For the full software catalog call list_features; for pricing call list_plans.

  ConnectorNo auth

• set_policiesA

  Veto — SQL Safety & Cost OracleA

  Replace the stored custom org policy set for your Pro key (this is also how you update or clear them: send the full new set to update, or an empty array to remove all). Each policy blocks or warns on an operation against matching tables (e.g. no DELETE on payments). Policies are declarative data — validated, never executed — and apply transparently to every later analyze_sql call made with this key. Use get_policies to read the current set.

  ConnectorNo auth

• create_xdala_session_start_handoffA

  XGR MCP GatewayB

  Prepare and store a read-only xgr-session-start@1 handoff for xDaLa Workbench. Use this tool whenever the user wants to start, run, launch, execute, queue, or prepare an XDaLa session. Use this tool for starting an existing deployed XRC-729/XRC-137 workflow, starting from a runtime XRC-729 orchestration, starting from a bundle deploy result, or importing a canonical xgr-session-start@1 request into xDaLa Manage Sessions. When explaining required input to users, use canonical xgr-session-start@1 terminology: sessions[].orchestration, sessions[].ostcId, sessions[].stepId, sessions[].payload, sessions[].maxTotalGas. Do not ask users for entryStepId; entryStepId is not the Workbench Session Start field. For deployed XRC-729 workflows, first inspect the runtime, identify ostcId and the likely entry step, resolve that step's XRC-137 rule, derive required payload fields from the XRC-137 payload schema, treat fields with defaults as optional, and present required and optional/default fields before creating a handoff. Do not call this tool with guessed payload values. If required start payload fields are missing, first present the required fields to the user and ask for values or explicit permission to use demo values. Only use demo/dummy/example/default values when the user explicitly asks or accepts them. This tool returns a Workbench xdalaUrl such as https://xdala.devnet.xgr.network/session-start/ss_... . The agent must show the returned xdalaUrl to the user. Do not replace the xdalaUrl with a generic /operations/op_... link. The MCP does not sign, submit, or execute. xDaLa Workbench performs local signing and calls xgr_validateDataTransfer. Do not describe the XRC-729 contract owner as the owner of a not-yet-started session; owner()/getOwner() and getExecutorList() identify start-authority roles only. Use sessions[].starterAddress only as an intended starter when explicitly set, and use terminal result data such as result.results[].owner/sessionId/pid for the actual session owner/starter after Workbench start.

  ConnectorNo auth

• oecd_dataframe_queryA

  oecd-mcp-serverA

  Run a read-only SQL SELECT against OECD observation tables staged on a DataCanvas by oecd_query_dataset. Call oecd_dataframe_describe first to discover exact table and column names, then use this tool for aggregation, filtering, GROUP BY, JOIN, and window functions. Returns up to `limit` rows (default 100, at most 1,000 per call) and at most 1 MiB of row data; truncated: true marks a result with more rows than came back, and its notice says how to reach the rest. A query still running after 30 seconds is stopped. Unavailable when the server runs with DataCanvas disabled.

  ConnectorNo auth

• database_tools_execute_queryA

  Point Topic — UK Broadband Market ReferenceA

  Query Point Topic's public broadband ontology (ClickHouse) — read-only. Exposes the public reference tables (the visitor view): the entity graph of ISPs, network operators, networks, links, link standards and their relationships. Discover tables with SHOW TABLES FROM ontology; inspect columns with DESCRIBE TABLE <name>. Licensed measurement data (footprints, premises, speeds, tariffs, forecasts, take-up, subscribers) is not queryable here and requires a Point Topic licence — denied queries return contact details. Only SELECT/WITH/SHOW/DESCRIBE/EXPLAIN allowed; returns CSV (large results are truncated at ~50k tokens with a leading notice — add LIMIT to keep results small).

  ConnectorNo auth

• ratchet_get_circuitA

  ratchetA

  Call this when a begin returned "approval_required" or "denied" and the reason mentions a circuit breaker. A breaker opens when an effect type is being performed far more often than its configured hourly ceiling — usually because something is looping. What to do with the answer: - If a breaker is open, STOP creating effects of that type. Retrying will not help and each attempt is recorded. - resets_at tells you when it closes itself. If it is null, a human opened it deliberately and only a human will close it — do not wait, and do not poll. - Report the reason to your operator and stop. Do not attempt to work around it by renaming the effect type, splitting the work across keys, or using a different idempotency key: that defeats a safety control that exists to protect the people your actions reach. - effect_type "*" means every effect type in the workspace is stopped.

  ConnectorNo auth

• read_gmail_attachmentA

  Higgs HubB

  Open one attachment of a Gmail message and return what is in it. Text, CSV, JSON, HTML and code files come back as themselves; images come back as pictures the assistant can look at. PDFs, spreadsheets and Word files can't be read yet — but any attachment can be saved as-is with save_gmail_attachment_to_drive. Attachments up to 10 MB. Get attachmentId from get_gmail_message or get_gmail_thread.

  ConnectorOAuth

• check_hmi_import_csvA

  HMI Import PreflightA

  Check a supplied CSV before importing it into an HMI project. Use tags_csv for a supported FactoryTalk View tag export, digital_alarms_csv for a digital-alarm export, and analog_alarms_csv for an analog-alarm export; each argument is the complete CSV text and may be omitted when that export type is not being checked. The tool validates deterministic import contract rules such as the expected export version marker, record shape, required fields, addresses, alarm severity and analog threshold structure. It returns result (PASS, REVIEW_REQUIRED, or INSUFFICIENT_INPUT), issue_count, a list of issues with code/severity/message and row or record provenance when available, plus a summary by issue code. Use this tool for static import preflight only; it does not connect to any HMI or PLC and does not certify runtime or safety behavior. This is an independent compatibility check, not an official Rockwell Automation service.

  ConnectorNo auth

• check_hmi_import_csvA

  RegEvidenceHub FactoryTalk Import PreflightA

  Check a supplied CSV before importing it into an HMI project. Use tags_csv for a supported FactoryTalk View tag export, digital_alarms_csv for a digital-alarm export, and analog_alarms_csv for an analog-alarm export; each argument is the complete CSV text and may be omitted when that export type is not being checked. The tool validates deterministic import contract rules such as the expected export version marker, record shape, required fields, addresses, alarm severity and analog threshold structure. It returns result (PASS, REVIEW_REQUIRED, or INSUFFICIENT_INPUT), issue_count, a list of issues with code/severity/message and row or record provenance when available, plus a summary by issue code. Use this tool for static import preflight only; it does not connect to any HMI or PLC and does not certify runtime or safety behavior. This is an independent compatibility check, not an official Rockwell Automation service.

  ConnectorNo auth

• update-project-memoA

  MemocoreA

  Update a memo that lives in a SHARED project (visible to, and editable by, every member). Use this to actualize or merge into an existing memo instead of creating a near-duplicate. Only the provided fields change, and each REPLACES the old value wholesale — so to merge, fetch the current memo first (get-memos) and send the combined `content`, not just the new fact. Passing `tags` replaces the memo's tags (this project's tags only). Editing a shared memo can leak data into the project just like creating one, so before calling you MUST scan whatever you are writing (`content` / `title` / `meta`) for personal or sensitive data (private contacts, secrets, credentials, health/financial info). If any is present, proceed only on the user's explicit confirmation. `preview` is PUBLIC (shown in search results and exposable via public share links even outside the project), so it must never contain sensitive data. Set `privacy_reviewed` to true only once that check genuinely passes. For your own private memos use update-private-memo instead. If the memo's project has an `instruction` (search-projects reports `has_instruction: true`, the memo carries its project id), it has writing guidelines from its team: read them with get-project, follow them where they fit the user's request, and pass `instruction_reviewed: true`. A ROW of a table project (it carries `fields`) changes only through `fields`, never `content`: unlike the other fields, `fields` MERGES — send just the columns that change, `null` clears one. The response includes a `share_url` field: the public /m/ link if the memo is already shared, otherwise a hint. If the user wants a link, use that field (or follow the hint via set-memo-sharing); never build one from `id`. The response may carry a `recommendation` with `similar` (near-duplicate memos in this project — if any is truly the same, consolidate: merge into one, delete the extras with delete-memo, staying within this project) and `suggested_tags` (fitting project tags for this memo — add the relevant ones, especially if it has none yet).

  Connector

  Destructive

  OAuth

• flow_get_blueprintA

  Final POS – Custom POS BuilderA

  INSPECTION ONLY — read a blueprint's overlay code by id (from list_blueprints) to understand how it works. To USE a blueprint, apply it: apply_blueprint_widgets for a widget-set (materializes its widgets byte-exact with the command-frame plumbing intact AND provisions the custom tables its code depends on), create_flow_from_blueprint for an FBB. Do NOT re-type code from this tool into write_flow_files — that silently drops the vetted plumbing and leaves its tables unprovisioned. `tables` (when present) lists the custom tables the code binds to by exact name. For a WHOLE-FLOW blueprint this returns the screen manifest WITHOUT file bytes by default — an entire app is far too large to read this way, and you never need to: instantiation copies it server-side. Pass includeFiles: true only to audit the source.

  ConnectorOAuth

• flow_lookup_pos_apiA

  Final POS – Custom POS BuilderA

  Look up the Final POS REST API (https://api.finalpos.com) — endpoint method/path, request fields, response shape, and a worked fetch example. This is the ONLINE-ONLY fallback for admin/management operations command-frame cannot express (creating products/variants/categories, customer management, outlets/stations/tax tables, webhooks). Command-frame is ALWAYS first choice for live POS data — it works offline and the host owns money/totals. A call to this API is network egress from the station: it fails whenever connectivity does, so never put one in the sale path — use it for setup/admin work and degrade gracefully. Pass resource to list a domain, operation for one endpoint, or query for fuzzy search.

  ConnectorOAuth

• import-claude-motion-from-urlA

  SocialyncA

  Import a video made with Claude Motion into the user's Socialync media library so it can be posted. Use this when the user wants to post, schedule or send a Claude Motion video to Socialync. Call it promptly with the download URL Claude Motion provides (it expires within minutes). Returns a mediaId to pass to publish_scheduled or schedule_post_draft (video posts work on every platform, YouTube also needs a title). Importing does not publish anything. Schedule the video within 12 hours of importing: media that no post uses is cleaned up after that.

  ConnectorOAuth

• check_ai_readinessA

  RequstoryA

  Check whether AI agents can read, understand and act on any website (bots allowed, readable pages, product data, checkout, help). Reads up to 3 public pages; results are kept for 24 hours and public at requstory.com/ai-readiness/<domain>/. Faster and narrower than map_website. If status is "queued" or "running", call again with start=false.

  ConnectorNo auth