"Diagnosing Issues with My Remote Ubuntu Server Configuration" matching MCP tools:

• analyze_xero_journal_cleanupA

  HelloBooks AI AgentsA

  Scan a Xero "Manual Journals" CSV export for cleanup issues — unbalanced journals, duplicate journals (same date + same totals), and schema problems (invalid dates, malformed amounts, missing account code/name, missing group key). Input is the raw CSV content the user pastes after exporting from Xero via Accounting → Advanced → Manual Journals → Export. Xero-specific idioms handled: signed Amount column (positive = credit, negative = debit), explicit Debit/Credit fallback shape, Reference-or-Narration+Date grouping, account code preferred over name. Max 5,000 rows; max 5 MB. Returns structured flags with severity, a roll-up summary, parse diagnostics, and a shareable URL at agents.hellobooks.ai/r/{slug}. Use this when a user pastes Xero manual-journal data, asks "check my Xero books", or "find issues in my Xero journal". The funnel CTA routes to /migrate/from-xero for users who want to fix at scale.

  ConnectorNo auth

• analyze_xero_journal_cleanupA

  HelloBooks AI Agents MCP ServerA

  Scan a Xero "Manual Journals" CSV export for cleanup issues — unbalanced journals, duplicate journals (same date + same totals), and schema problems (invalid dates, malformed amounts, missing account code/name, missing group key). Input is the raw CSV content the user pastes after exporting from Xero via Accounting → Advanced → Manual Journals → Export. Xero-specific idioms handled: signed Amount column (positive = credit, negative = debit), explicit Debit/Credit fallback shape, Reference-or-Narration+Date grouping, account code preferred over name. Max 5,000 rows; max 5 MB. Returns structured flags with severity, a roll-up summary, parse diagnostics, and a shareable URL at agents.hellobooks.ai/r/{slug}. Use this when a user pastes Xero manual-journal data, asks "check my Xero books", or "find issues in my Xero journal". The funnel CTA routes to /migrate/from-xero for users who want to fix at scale.

  ConnectorNo auth

• save_whatsapp_toolA

  ErzyCallB

  Add or edit non-secret configuration for a WhatsApp HTTP, remote MCP, platform or connected-app tool after confirming the exact change. Pass id to edit and complete configuration; omit url to preserve an existing endpoint. Input schema must describe an object. This customer MCP schema rejects credentials; manage authentication headers in dashboard settings or through the REST API. Creating a tool does not enable it; assign IDs using update_whatsapp_agent updates.externalToolIds. Reuse the same idempotencyKey on retries. Requires whatsapp_agents:write.

  ConnectorOAuth

• list_product_issuesA

  FeedShine: Shopify Google Shopping FeedA

  Google Merchant Center issues for this store, as of the app's last nightly sync: one row per issue code with severity, affected product counts, sample products and the destinations it applies to. Account-level issues are included. Covers the whole account (file feeds and the native channel too). Call this FIRST when the merchant asks why products are disapproved or wants to fix issues. Then inspect specific products with preview_product and fix via set_product_override or update_feed_settings.

  ConnectorAPI key

• list_my_issuesA

  BoardMarkA

  Open issues assigned to you in every project you can access, most recently updated first (D66 "My work"); on Sales & Billing projects also the unpaid installments of deals whose `owner` field is you (D130 (7)). With an agent account's token (D144): the issues assigned to the agent (`agt_…`), not to its owner. "What's on my plate?" — the issues assigned to you (the token's user) in EVERY project you can access, in one call, most recently updated first. Open issues only (not in a done-category status) unless `include_done: true`. Each item is an issue summary (`key`, `title`, `type`, `priority`, `status`, `assignee`, `points`, `sprint`, `version`, `updated_at`, …) plus `project_key` and `project_name`. Paginated with `cursor`/`next_cursor`. Use this instead of calling search_issues with `assignee=me` project by project; use search_issues when the user means one project or needs other filters. Call get_issue before changing any of these issues. Sales & Billing projects (D130): the installments (`type: subtask`, `parent` = the deal) of deals you own (`fields.owner`) are listed too, so an installment that is due or overdue on your deal shows here — read its `flags` (bill_due, due_soon, overdue). You act with exactly the rights of the user who owns this token; a project you cannot see returns not_found.

  ConnectorOAuth

• list_systemic_patternsA

  AnkraA

  List the SYSTEMIC PATTERNS the platform tracks: issues that have recurred AND been remediated repeatedly, grouped by whoever can fix them at source. ALWAYS call this before diagnosing a recurring problem, and whenever the user asks why something keeps happening, keeps coming back, or has happened before. Each entry carries occurrence / distinct-cluster / distinct-day counts, how many times an agent remediated it, and an interpretation field stating what the row means for your answer - read that field before replying. A pattern with status 'escalated' has ALREADY been reported for a permanent fix (to the Ankra platform team as a support ticket, or to a stack profile's owner as a change request): say so and cite escalation_reference instead of re-diagnosing, and never report it again. Scope 'platform' means the defect arrives with every cluster Ankra provisions; 'stack_profile' means one profile version ships it to every deployment of that profile; 'local' is confined to one cluster and is never reported upstream. Read-only.

  ConnectorOAuth

• auditA

  mcpA

  Perform comprehensive audit of a website URL. Fetches the URL content ONCE and provides a combined report with: - Classification: category, subcategory, language, sentiment, demographics - SEO Analysis: score, grade, issues, recommendations - EEAT Analysis: experience, expertise, authoritativeness, trustworthiness scores - AEO Analysis: AI answer engine optimization score, metrics, issues, signals (includes full Citation Readiness analysis in the nested 'citation' key) - Advertiser Matching: best-fit advertising networks with scores - Similar Sites: competitor/related sites from the same category This is more efficient than calling classify_url, analyze_seo, analyze_eeat, analyze_aeo, select_advertiser, and find_similar_sites separately as it only fetches the page once. Args: url: The website URL to audit (e.g., "https://example.com"). Returns: Comprehensive audit report with: - url: The analyzed URL - classification: Category, subcategory, language, sentiment, demographics - seo: Score, grade, issues, recommendations - eeat: EEAT score, grade, category scores, issues, signals - aeo: AEO score, grade, metrics, issues, signals (includes citation results) - advertisers: Matched advertising networks with scores - similar_sites: Related sites from the same category (up to 10) - cached: Whether result was from cache

  ConnectorNo auth

• acc_list_issuesA

  ACC MCPA

  List and filter issues from a single ACC project (limit 50 per call) via the APS Construction Issues API. When to use: The user or upstream agent needs to review open issues, count issues by status/priority, or look up an issue_id before calling acc_update_issue. E.g. 'show me all critical open issues on the Tower project'. When NOT to use: Do not use to fetch RFIs (use acc_list_rfis) or to search documents. APS scopes: data:read account:read. No write scope required. Rate limits: ACC Issues API ~100 req/min per app; results pageable (limit 50 here, max 200 upstream). For large projects, call once and filter client-side instead of looping. Errors: 401 (APS token expired — refresh); 403 (user lacks 'View Issues' permission on project or scope insufficient); 404 (project_id not found — verify 'b.' prefix and hub membership via acc_list_projects); 422 (invalid filter value — check status/priority spelling); 429 (rate limit — back off 60s); 5xx (ACC upstream — retry with jitter). Side effects: None. Read-only and idempotent.

  ConnectorNo auth

• delete_tableA

  mcpA

  Delete a table. The request requires the 'name' field to be set in the format 'projects/{project}/instances/{instance}/tables/{table}'. Example: { "name": "projects/my-project/instances/my-instance/tables/my-table" } The table must exist. You can use `list_tables` to verify. Before executing the deletion, you MUST confirm the action with the user by stating the full table name and asking for "yes/no" confirmation.

  Connector

  Destructive

  No auth

• analyze_qbo_journal_cleanupA

  HelloBooks AI AgentsA

  Scan a QuickBooks Online "Journal Entries" CSV export for cleanup issues — unbalanced journals (debits ≠ credits, with severity by deviation), duplicate journals (same date + same totals, likely posted twice), and schema problems (invalid dates, malformed amounts, missing accounts, missing journal numbers). Input is the raw CSV content the user pastes after exporting from QBO via Reports → Accountant → Journal → Export. Max 5,000 rows; max 5 MB. Returns a structured flag list with severity (high/medium/low), a roll-up summary by category and severity, parse diagnostics (column mapping + unmapped columns), and a shareable URL at agents.hellobooks.ai/r/{slug} (7-day TTL) that renders a branded analysis page suitable for sending to a CA or bookkeeper. Use this when a user pastes QBO journal data, asks "check my books", "find issues in my QBO journal", or "what is wrong with my journal entries". Each flag includes a `fixableInHellobooks` boolean — true means HelloBooks can resolve it automatically in the paid product.

  ConnectorNo auth

• analyze_qbo_journal_cleanupA

  HelloBooks AI Agents MCP ServerA

  Scan a QuickBooks Online "Journal Entries" CSV export for cleanup issues — unbalanced journals (debits ≠ credits, with severity by deviation), duplicate journals (same date + same totals, likely posted twice), and schema problems (invalid dates, malformed amounts, missing accounts, missing journal numbers). Input is the raw CSV content the user pastes after exporting from QBO via Reports → Accountant → Journal → Export. Max 5,000 rows; max 5 MB. Returns a structured flag list with severity (high/medium/low), a roll-up summary by category and severity, parse diagnostics (column mapping + unmapped columns), and a shareable URL at agents.hellobooks.ai/r/{slug} (7-day TTL) that renders a branded analysis page suitable for sending to a CA or bookkeeper. Use this when a user pastes QBO journal data, asks "check my books", "find issues in my QBO journal", or "what is wrong with my journal entries". Each flag includes a `fixableInHellobooks` boolean — true means HelloBooks can resolve it automatically in the paid product.

  ConnectorNo auth

• check_api_statusA

  livetennisapi-mcpA

  Check whether the Live Tennis API is reachable and which plan the configured key is on. Useful for diagnosing why other tools are refusing data.

  ConnectorNo auth

• list_catalogA

  KnownFixA

  Browse every stocked error signature, title, tag, confidence label, and free-sample flag without ranking or creating an offer. Use search_fixes instead when diagnosing a specific error; it returns the best match and any purchase-ready checkout.

  ConnectorNo auth

• tascan_server_infoA

  TaScanB

  Identify exactly which TaScan server and schema this MCP session is talking to. Call this FIRST when diagnosing anything — it makes "dev server masquerading as production" and "is my fix deployed yet" one tool call instead of an inference.

  ConnectorNo auth

• healthA

  Vibes-Coded Agent Security and Commerce ToolsA

  Return MCP server liveness: version, origin, tool count, and catalog size. Use for hosted inspector probes (Glama / Smithery) or before diagnosing tool failures. Do not use for business outcomes — call vc_* tools or pay(slug=...) instead. No auth required. No side effects. Returns JSON {ok, service, version, origin, tools, catalog_resources}.

  ConnectorNo auth

• check_healthA

  NewsMCPA

  Check whether the NewsMCP REST API is reachable and healthy. Does not require an API token. Use when diagnosing connectivity, not for searching news. For allowances and remaining budget use `check_limits` instead. Returns: str: Health status reported by the API.

  ConnectorNo auth

• console_get_crawl_issuesA

  Manifold MCPA

  URLs Bing had trouble crawling on the user's property: HTTP errors, redirects, robots.txt blocks, DNS and timeouts, with the inbound link count of each. Use when: "what is Bing failing to crawl", "which of my pages 404", a Bing-side health check. Not for: Google, which exposes nothing equivalent outside console_inspect_url. A crawl of the whole site with our crawler, use seo_run_technical_crawl. Returns: List, one row per URL and issue. rows[]: url, issue (Code301, Code302, Code4xx, Code5xx, BlockedByRobotsTxt, ContainsMalware, ImportantUrlBlockedByRobotsTxt, DnsErrors, TimeOutErrors), http_status, inlinks, seen_at. Fixed issues stay listed a few days. Cost: 0 credits, Bing only. Cached 6 hours. Example: {"property": "https://example.com"}

  ConnectorAPI key

• delete_mcp_serverA

  AgentPlaybooksA

  Disconnect an MCP or OpenAPI server from this playbook. The remote server is not shut down; only this playbook's connection record is removed. Requires playbooks:write or full permission. Use update_mcp_server to change configuration without disconnecting. Pass playbook_id as the UUID or GUID of the playbook this call should target.

  Connector

  Destructive

  API key

• list_projectsA

  BoardMarkA

  List projects you are a member of. Paginated: pass `next_cursor` from the previous page as `cursor`. Project keys (e.g. `KJ`) are used by every other tool. Pass `stats: true` for an overview of every project in ONE call (use it for "how are my projects doing?" instead of searching each project): each item then carries `stats` — `open_issues` / `done_issues` (done = the project's done-category statuses), `assigned_to_me` (open issues assigned to you), `active_sprints` (scrum only; every running sprint — there can be several — with `id`, `name`, `start`, `end`, `issues`, `done_issues`, `total_points`, `done_points`; empty on kanban/pipeline or when none runs) and `updated_at` (last change to the project, or null). Leave it off when you only need the keys. Before you start working on one of these projects, read its docs: get_project returns `docs.read_first` (read those with get_doc) and `docs.open_handoffs_for_me`, or call get_docs_context for all of it as one text. You act with exactly the rights of the user who owns this token; a project you cannot see returns not_found.

  ConnectorOAuth

• diagnose_shotA

  ShotPulledA

  Evaluate shot metrics to provide ranked hypotheses (C6) and warn on flip-flops (G2) or fatigue (G6). Resolves the SHOT's own bean — age computed at the shot's pulled_at — never the active profile, and echoes it as bean_context, so diagnosing an older or differently-filed shot is always safe. The engine reads metrics and sensory tags — NOT free-text notes — so make sure taste feedback is recorded as sensory_tags on the shot (via log_shot or update_shot) before diagnosing; otherwise an in-range shot that tastes bad will come back "balanced".

  ConnectorNo auth

• list_skillsA

  mcpA

  START HERE for any open-ended request. Lists the task playbooks this server supports — systematic learning from bookmarks, organising into themes, cleaning up, X-list intelligence, exporting data out, finding a half-remembered save, digests, and diagnosing sync. Each names when to use it; call get_skill for the exact tool sequence.

  ConnectorNo auth