The MCP tool directory.
Each row is one tool from one provider. Tools sharing a name across providers (e.g. search) are listed separately because they aren't interchangeable.
[ 3610 tools indexed ]
[ all tools ]
30 / 3610
read_transmissions
[ remote ]Browse and read AI-authored book reviews. Lists all transmissions if no slug provided, or returns the full review text for a specific book.
read_verification_email
[ remote ]Read the latest email verification code / OTP from the user's Gmail inbox. Use this after smart_login encounters a verification code screen. The user must have previously authorized Gmail access via authorize_email_access. Searches recent emails for verification codes from common senders (Clerk, Auth0, etc).
read_wiki_contents
[ remote ]View documentation about a GitHub repository
read_wiki_contents
[ remote ]View documentation about a GitHub repository
read_wiki_structure
[ remote ]Get a list of documentation topics for a GitHub repository
read_wiki_structure
[ remote ]Get a list of documentation topics for a GitHub repository
realtime_apps_create
[ remote ]Provision a Realtime app and its first key. `region` is immutable once set and must be one of `realtime_regions_list`. The response is the only place the key's secret ever appears, and no operation can read it back: recovering from a lost secret means creating another key. An app is what the publish and channel-inspection operations address.
realtime_apps_delete
[ remote ]Permanently delete a Realtime app. Every connected client is disconnected, all keys and configuration are removed, and clients holding one of its keys start failing immediately. Deleted apps cannot be restored.
realtime_apps_get
[ remote ]Read one Realtime app's configuration and the connection details a client needs (`app_id`, `region`). Key material is never included, so a client that also needs a key uses `realtime_apps_keys_list`.
realtime_apps_keys_create
[ remote ]Add a key to an app and read its secret. Takes no body. This response is the only place the secret appears, so a caller that does not capture it has to create another key. The app's existing keys keep working, which is what makes this the first step of a rotation: add, roll out, then revoke the old key.
realtime_apps_keys_list
[ remote ]List an app's keys, oldest first, without their secrets: a secret is readable only in the response that created it. Revoked keys are excluded unless `include_revoked` is true. An app can hold several live keys at once, which is what makes rotation zero-downtime.
realtime_apps_keys_revoke
[ remote ]Revoke a key. It stops working immediately and every client still holding it fails, so revoke only after the replacement is rolled out. The record survives with `revoked_at` set rather than disappearing. Revoking a key twice is a conflict, and an app's last remaining key cannot be revoked at all.
realtime_apps_list
[ remote ]List the workspace's Realtime apps as a cursor page, filterable by a case-insensitive `name` substring. Each entry carries the connection details a client needs (`app_id`, `region`) but no key material.
realtime_apps_update
[ remote ]Rename a Realtime app or change its configuration flags. Omitted fields keep their current value. Region cannot be changed after creation, so moving an app to another region means creating a new one and repointing clients.
realtime_regions_list
[ remote ]List the regions a Realtime app can be created in. Read this before creating an app: `region` is immutable, and the identifiers here are the only accepted values.
rebalance_resources_to_product
[ remote ]Shift outbound/day budget from the worst active campaign to a target product campaign.
rebase_branch
[ remote ]Rebases a development branch on production. This will effectively run any newer migrations from production onto this branch to help handle migration drift.
recipients_add_cc
[ remote ]Add a CC (non-signing) recipient to a document. Requires an existing contact ID. Cannot add to Expired or Declined documents. Adding a contact that is already a CC recipient is silently ignored. This tool only adds CC recipients; signers must be set via `documents_create` or `documents_update`.
recipients_delete
[ remote ]Remove a recipient from a document. Signers can only be removed in Draft status. CC recipients can be removed in any status except Expired/Declined.
recipients_edit
[ remote ]Update one recipient's details (email, name, phone, company, address, redirect) in place. Signers can be edited in Draft, Waiting Approval, Approved, Rejected, Sent, or Viewed status. A signer's email cannot be changed after they have signed. CC recipients can be edited in any status except Expired or Declined. Get recipient_id from document details first. Cannot use emails of existing contacts — use `recipients_reassign` for that.
recipients_reassign
[ remote ]Replace a signer with another contact. Transfers all assigned fields to the new signer. The original signer is removed. Cannot reassign already-signed recipients. To just fix a signer's email/name, use `recipients_edit`.
recommend_deployment
[ remote ]$0.25 USDC: recommend what to buy or run from bounded StackBench fit, performance, confidence, evidence, caveats, and economics only when supported.
recommend_stack
[ remote ]Get a full tech stack recommendation with custom priorities and constraints. Unlike the demo version, this uses the complete scoring engine with weight adjustments. Requires Pro account.
recommend_stack_demo
[ remote ]Get a complete tech stack recommendation for your project type. Returns the highest-scored technology for each category (frontend, backend, meta-framework, database, ORM, auth, hosting, payments) based on deterministic scoring algorithms. FREE demo with 1 request per day limit. For unlimited access with custom priorities and constraints, upgrade to Pro at stacksfinder.com.
recommend_template
[ remote ]Get template recommendations based on your project requirements. Provide criteria like purpose, color preferences, animation level, required features, and complexity. Returns ranked template suggestions with explanations.
records.changeStatus
[ remote ]Update the status of a record. Works on Offers, Candidates (candidate status), Job Openings, and similar status-bearing modules. The body's `data` array contains the new status value.
records.changeStatus
[ remote ]Update the status of a record. Works on Offers, Candidates (candidate status), Job Openings, and similar status-bearing modules. The body's `data` array contains the new status value.
records.changeStatus
[ remote ]Update the status of a record. Works on Offers, Candidates (candidate status), Job Openings, and similar status-bearing modules. The body's `data` array contains the new status value.
records.changeStatus
[ remote ]Update the status of a record. Works on Offers, Candidates (candidate status), Job Openings, and similar status-bearing modules. The body's `data` array contains the new status value.
records.clone
[ remote ]To clone a record in a module.