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.
[ 3722 tools indexed ]
[ all tools ]
30 / 3722
authorization.organizations.roles.permissions.create
[ remote ]Add a single permission to an organization role. If the permission is already assigned to the role, this operation has no effect.
authorization.organizations.roles.permissions.delete
[ remote ]Remove a single permission from an organization role by its slug.
authorization.organizations.roles.permissions.update
[ remote ]Replace all permissions on a role with the provided list.
authorization.organizations.roles.update
[ remote ]Update an existing custom organization role. Only the fields provided in the request body will be updated.
authorization.permissions.create
[ remote ]Create a new permission in your WorkOS environment. The permission can then be assigned to environment roles and organization roles.
authorization.permissions.delete
[ remote ]Delete an existing permission. System permissions cannot be deleted.
authorization.permissions.get
[ remote ]Retrieve a permission by its unique slug.
authorization.permissions.list
[ remote ]Get a list of all permissions in your WorkOS environment.
authorization.permissions.update
[ remote ]Update an existing permission. Only the fields provided in the request body will be updated.
authorization.resources.create
[ remote ]Create a new authorization resource.
authorization.resources.delete
[ remote ]Delete an authorization resource and all its descendants.
authorization.resources.get
[ remote ]Retrieve the details of an authorization resource by its ID.
authorization.resources.list
[ remote ]Get a paginated list of authorization resources.
authorization.resources.organization_memberships.list
[ remote ]Returns all organization memberships that have a specific permission on a resource instance. This is useful for answering "Who can access this resource?".
authorization.resources.update
[ remote ]Update an existing authorization resource.
authorization.roles.create
[ remote ]Create a new environment role.
authorization.roles.get
[ remote ]Get an environment role by its slug.
authorization.roles.list
[ remote ]List all environment roles in priority order.
authorization.roles.permissions.create
[ remote ]Add a single permission to an environment role. If the permission is already assigned to the role, this operation has no effect.
authorization.roles.permissions.update
[ remote ]Replace all permissions on an environment role with the provided list.
authorization.roles.update
[ remote ]Update an existing environment role.
authors-papers
[ remote ]Get papers written by a specific author
authors-search
[ remote ]Search for authors by name or affiliation
autocomplete
[ remote ]Autocomplete values for business filters based on a query. Never use for fields not explicitly listed (e.g., `website_keywords`). Prefer `linkedin_category` over `google_category` when both apply. **Query rules (critical):** - Pass exactly one concept per call: a single word or short phrase (≤100 characters). - Never pack comma-separated or space-joined lists (e.g. "defense, aviation, medical devices") into one query — that fails. - For multiple concepts, call autocomplete once per concept and merge the returned values. **Category specificity check (`linkedin_category` vs `naics_category`):** When the user names a specific business type, the category you filter on must be as specific as the request — for ANY industry, not just common ones. 1. Run autocomplete with field=linkedin_category. This is the default route and normally the ONLY category autocomplete you make. 2. Test the best match: "Would a large share of companies in this category be something OTHER than what the user asked for?" - No → use linkedin_category. Done — do NOT also autocomplete naics_category. - Yes → the label is a parent industry that merely contains the request. Run autocomplete with field=naics_category and use the most specific matching NAICS code(s) instead. 3. Never run both category autocompletes as a routine double-check. The naics_category autocomplete is ONLY for when step 2 answers "Yes" or LinkedIn returned no plausible match. Exactly one of `linkedin_category` / `naics_category` per fetch — never both. **Category Selection Strategy:** When autocomplete returns multiple relevant categories, you MUST: - ✓ MUST include ALL applicable categories to maximize coverage - ✓ ALWAYS prioritize comprehensiveness over precision - ✗ ONLY exclude clearly unrelated categories - ✗ NEVER pad with broader parent categories when the user asked for a specific business type — trigger the NAICS fallback above instead - ✓ For broad queries → include more categories rather than fewer - VIOLATION: Limiting selection unnecessarily will reduce result quality **Session Storage:** - If session_id is provided, results will be stored for future reference - If not provided, a new session_id will be created and returned - Returns session_id in the response for future data retrieval Do NOT call autocomplete for: - `company_country_code`: List[str] — use valid ISO Alpha-2 country codes directly (e.g., "US", "IL") - `company_region_country_code`: List[str] — use valid ISO 3166-2 region codes directly (e.g., "US-NY", "IL-TA") - `prospect_country_code`: List[str] — use valid ISO Alpha-2 country codes directly (e.g., "US", "IL") - `prospect_region_country_code`: List[str] — use valid ISO 3166-2 region codes directly (e.g., "US-NY", "IL-TA") Hints: - Searching for SaaS? Use the keyword 'software'
autonomous_email_deliverability_and_campaign_architect
[ remote ]Autonomous 1-Shot Email & Deliverability Engine: Generates responsive HTML/MJML transactional templates, audits SPF/DKIM/DMARC DNS records for 99%+ inbox placement, and writes 3-step B2B cold outreach sequences in a single call.
award_job
[ remote ]Accept a bid and award the job to a worker agent. Returns the worker's wallet address and agreed price so you can immediately create the bilateral XRPL escrow via create_escrow_vault(). All other bids are automatically rejected. No funds are held by the referee at any point — the escrow is created directly between you and the worker. The award_token was returned by post_job() — store it securely when you post the job.
batch-analysis
[ remote ]Performs a batch analysis of multiple URLs, domains, or subdomains to retrieve selected SEO, backlink, organic, and paid traffic metrics. When analyzing a domain name, you must use mode=subdomains. Using mode=domain can exclude www and other subdomains. Use doc tool first to get the real input schema.
batch_wallet_trust_scores
[ remote ]Score up to 50 XRPL wallets in a single call — the open reputation layer for XRPL agents. All addresses are scored in parallel. Results are returned ranked by score descending with a rank field on each entry. Fee: $0.10 (XRP or RLUSD on XRPL). Use cases: - Rank candidates before awarding a job - Screen a shortlist of bidders for counterparty risk - Build agent directories or leaderboards - Pre-hire due diligence on multiple wallets at once Returns: {count, batch_size, results: [{address, score, rank, signals, ...}]}
billing
[ remote ]Check what this key can still render for free and its credit (no GPU time): the free GPU time left and when it expires or resets (each new key gets 100 JPY of GPU time free with no card (14 days) and 400 JPY more once the user saves a card on a page that charges nothing (once per card); after that, previews are free up to 2 GPU-minutes a day and finals cost 0.1 JPY per GPU-second (prepaid)), the balance in yen, the price per GPU-second, any pending checkout link, and card_offer / autocharge_offer when they apply. Relay tell_user to the user in their language when it is present.
billing
[ remote ]Check credit balance, subscription status, or open billing portal.