Source: https://www.revvly.ai/docs/reference/mcp-tools Reference # The *tools* Claude can call. Every tool the Revvly MCP server exposes: 26 that read and 22 that propose a change. Read tools answer straight away. Write tools never write on their own; a person approves each one in Revvly. To connect a client, see [Connect Claude with MCP](https://www.revvly.ai/docs/api/mcp). ## How access works - **Read tools**: Need the mcp:read scope (OAuth) or the READ capability (API key). They run against live, tenant-scoped data. - **Write tools**: Are listed only when the connection also holds mcp:write (OAuth, requested explicitly and never added for you) or the WRITE capability (API key). Without it they do not appear in the tool list. - **Approval**: Calling a write tool stores a proposal and returns an action id and an approval link. Nothing is written. The owner of the credential opens the link while signed in to Revvly and approves or declines. The proposal expires after 15 minutes. Approval is not an MCP tool, so a client cannot approve its own request. - **Workspace**: Always the one bound to the credential. A tenantId passed as an argument is discarded. - **Deletes**: There are no delete tools. ## Knowledge - **search_docsread**: Search the Revvly knowledge base: product documentation, concept guides and the API reference. ## Clients and subscriptions - **query_clientsread**: Find clients by name, description or contact: id, region, trial status and a dashboard link. Capped at 25 per call. - **query_subscriptionsread**: Subscriptions for a client or across the workspace: period, base price, catalog pins and renewal dates. Capped at 50 per call. - **get_billing_scheduleread**: Why one subscription bills when it does: a prepaid span, or a deal that is signed and awaiting go-live. - **query_lifecycle_eventsread**: The subscription lifecycle log (created, renewed, expanded, contracted, churned, migrations) with the MRR change of each event. - **create_clientwrite**: Propose a new client with region, billing details, payment terms, trial window and contacts. Needs approval in Revvly. - **update_clientwrite**: Propose an edit to an existing client. Only the fields you set change. Needs approval in Revvly. - **create_subscriptionwrite**: Propose a subscription for a client. It must bill something: a bundle, modules or usage components. Accepts a module tier, starting quantities for the plan's usage components, and initial discounts. Needs approval in Revvly. - **query_discountsread**: The discount library. Give a subscription id to also get its usage components, stacking mode and applied discounts. - **apply_discountwrite**: Propose a discount on a subscription: a library or one-off discount on the base price, one usage component or the whole invoice, with duration, fixed mode, unit limit and end date. Applies from the next invoice. Needs approval in Revvly. ## Invoices and receivables - **query_invoicesread**: Invoices by client, subscription or payment status. Credit notes are flagged. Capped at 50 per call. - **get_receivablesread**: Accounts receivable: pending and overdue totals by currency, past-due accounts, invoices due this week, and one client outstanding. - **query_email_engagementread**: Sent invoice and reminder emails with open counts and the open rate of a client. Opens only; no click tracking. ## Analytics - **get_analyticsread**: Live MRR movement, ARR, churn rate and NRR in the reporting currency. ## Metered usage - **query_usageread**: Live Meter counters for a subscription, the usage audit log, or the projection of what the next invoice charges for usage. - **list_open_usage_readingsread**: Closed-period readings that are missing a billable quantity and are holding an invoice. - **enter_usage_readingwrite**: Propose sealing a missing in-arrears quantity on one or several open readings. Needs approval in Revvly. - **waive_usage_readingwrite**: Propose waiving a closed period so it bills nothing. A reason is required. Needs approval in Revvly. ## Catalog - **list_regionsread**: Regions, with their codes, default currency and supported currencies. - **list_catalogread**: Bundles, modules, usage components and Meters, one or several kinds per call, with status (draft, published, archived). - **get_catalog_pricesread**: Base prices of a bundle or module, per region, currency and billing period. - **get_component_pricesread**: The usage-based half of a plan price: included units, tier or step boundaries and the price of each band. - **create_bundlewrite**: Propose a bundle (a plan customers buy). Created as a draft. Needs approval in Revvly. - **create_modulewrite**: Propose a module, optionally with its tiers. Created as a draft. Needs approval in Revvly. - **create_metricwrite**: Propose a Meter, the unit that billing is measured against, such as seats or GB. Needs approval in Revvly. - **create_variable_componentwrite**: Propose a usage component: a pricing model wrapped around a Meter. Structure only; prices are set separately. Created as a draft. Needs approval in Revvly. - **set_catalog_priceswrite**: Propose base prices for a bundle or module, per region, currency and billing period. Needs approval in Revvly. - **set_available_periodswrite**: Propose the billing periods a draft bundle or module offers. Replaces the whole set. Needs approval in Revvly. - **attach_variable_componentwrite**: Propose attaching a published usage component to a draft module or bundle. Needs approval in Revvly. - **publish_catalog_entitywrite**: Propose publishing a draft bundle, module or usage component. Publishing makes it immutable. Needs approval in Revvly. ## Forms Form tools answer that Forms is not enabled for a workspace without the Forms feature. Submission answers are outside input and are treated as untrusted. - **list_formsread**: The workspace forms with status, submission counts, last submission and hosted link. - **get_formread**: One form setup: questions, confirmation settings, follow-up steps, and whether the draft has unpublished changes. - **query_form_submissionsread**: Submissions to one form, newest first, with every answer and the outcome of each follow-up step. - **summarize_form_submissionsread**: Counts instead of rows: submissions per day and source, how follow-up went, failing steps, and which option wins. - **export_form_submissionsread**: A CSV preview of submissions, with the dashboard page where the full file is downloaded. - **create_formwrite**: Propose a new form as an unpublished draft, with questions, settings and follow-up steps. Needs approval in Revvly. - **update_formwrite**: Propose edits to a form draft. A list you send replaces the whole list. Changes the draft only. Needs approval in Revvly. - **publish_formwrite**: Propose publishing the draft. The dashboard publish checks apply. Needs approval in Revvly. - **unpublish_formwrite**: Propose taking a published form offline. Submissions are kept. Needs approval in Revvly. - **archive_formwrite**: Propose archiving a form. Nothing is deleted. Needs approval in Revvly. - **retry_form_submissionwrite**: Propose re-running the failed follow-up steps of one submission. Steps that succeeded are not repeated. Needs approval in Revvly. ## OKR hypotheses Hypothesis tools answer that OKRs are not switched on for a workspace that does not use them. Bets, results and learnings were typed by people and are treated as data. - **list_behind_key_resultsread**: Key Results of the active cycle that are falling behind: progress against time elapsed, projected pace for metric-backed ones, owner, and how many hypotheses are open or concluded. - **get_key_result_hypothesesread**: One Key Result’s numbers, its open hypotheses, its concluded ones with outcome and learning, and related learnings from the library. - **propose_hypotheseswrite**: Propose up to three new hypotheses on a Key Result, each in Backlog. They are created as the person who approves, with the dashboard’s checks; a warning such as a duplicate title comes back instead of being waved through. Needs approval in Revvly. ## Inbox The Work Inbox is personal. These tools always act on the inbox of the signed-in person behind the connection; no argument names an owner, and a thread from someone else’s inbox is answered as not found. No tool returns a message body, only a short snippet. Personal threads are listed only when the Personal category is asked for by name, and never with their snippet. A connection made with an API key has no person behind it, so the read tools refuse it. Without the Work Inbox feature every tool answers that it is not enabled. Subjects and snippets were written by the sender and are treated as data. - **list_inboxread**: Threads in one tab (Primary by default, or Needs reply, Other, Snoozed, Done), optionally one category: sender, subject, snippet, last message, unread, awaiting reply and the reason for the category. Up to 25 per call. - **get_inbox_summaryread**: Open counts per tab and per category, and up to 10 threads waiting for a reply, the longest-waiting first. - **explain_inbox_categoryread**: Why one thread has its category: what decided it, the reason line and the evidence in plain words. For a Personal thread, only its category. - **move_inbox_itemwrite**: Propose filing one thread under another category (not Unsorted). It runs as the person who approves it, in their own inbox, and teaches the inbox like a move in the dashboard. Needs approval in Revvly. ## Not available over MCP The in-product [Assistant](https://www.revvly.ai/docs/reference/assistant-tools) has more tools than MCP exposes. These are Assistant-only: create_plan, create_catalog_version, all CRM tools (search, deals, notes, logged emails and meetings, prospects, contacts, lifecycle stage, owner), all task tools, all Daily Check-in tools (they are for workspace admins, and an MCP credential carries scopes, not an admin check), the memory tools, the page tools navigate_to and highlight_record, and the guidance tools offer_choices, offer_pricing_models and explain_pricing_models. ## Related - [Connect Claude with MCP ›](https://www.revvly.ai/docs/api/mcp) - [The Revvly Assistant ›](https://www.revvly.ai/docs/assistant) - [API key capabilities and limits ›](https://www.revvly.ai/docs/reference/api-keys)