Skip to main content
Glama
127,308 tools. Last updated 2026-05-05 13:41

"A platform for managing and deploying backend services and databases" matching MCP tools:

  • List locales supported by the Molt2Meet platform. Returns the URL slug (e.g. 'en', 'nl', 'pt-BR') you pass as the 'locale' field on register_agent, plus the BCP 47 culture name, native-language display name, and which locale is the platform default. No authentication required. Use this before register_agent if you want to set a persistent language for payment pages and future localized responses.
    Connector
  • Retrieve the full GLEIF LEI record for one legal entity using its 20-character LEI code. Returns legal name, registration status, legal address, headquarters address, managing LOU, and renewal dates. Use this tool when: - You have a LEI (from SearchLEI) and need full entity details - You want to verify the registration status and renewal date - You need the exact legal address and jurisdiction of an entity Source: GLEIF API (api.gleif.org). No API key required.
    Connector
  • Returns structured information about what the Recursive platform includes: features, AI model details, supported integrations, and what's included at every tier. Use for systematic feature comparison.
    Connector
  • Get the list of legal document templates available for generation on the platform (e.g. NDA, employment agreement, stock purchase agreement). For corporate services like 83(b) filing or registered agent, use get_available_corporate_services instead.
    Connector
  • Generates a browser authorization URL for connecting a new social account to a project. This endpoint is useful for multi-user integrations where your application lets your own users, clients, or brands connect their social accounts to WoopSocial without giving them access to your WoopSocial account. A common flow is: 1. Create or select a WoopSocial project for your user, client, or brand. 2. Call this endpoint from your backend with that `projectId`, the target `platform`, and a `redirectUrl` in your application. 3. Open the returned `url` in your user's browser. 4. After OAuth completes, WoopSocial redirects the browser back to `redirectUrl` with result query parameters. 5. Use `projectId` and `socialAccountIds` from the redirect, or call `GET /social-accounts?projectId=...`, to store or confirm the connected account in your application. When `redirectUrl` is provided, the browser is redirected back to that URL after the OAuth callback is handled. On success, WoopSocial appends these query parameters to `redirectUrl`: - `status=success` - `projectId`: the project identifier from the request - `platform`: the connected social platform - `socialAccountIds`: comma-separated connected social account identifiers. This may contain one or more IDs depending on the platform OAuth flow. On failure, WoopSocial appends these query parameters to `redirectUrl`: - `status=error` - `projectId`: the project identifier from the request - `platform`: the requested social platform - `error`: an OAuth callback error code If the OAuth callback state is missing or expired, WoopSocial cannot safely determine the original `redirectUrl`, so the callback returns an HTTP error instead of redirecting. The redirect never includes OAuth tokens or credentials.
    Connector
  • List all databases in a given catalog. ⚠️ WORKFLOW: Call this after list_catalogs_tool to explore a specific catalog. 📋 PREREQUISITES: - Call search_documentation_tool first to understand what you're looking for - Call list_catalogs_tool to discover available catalogs 📋 NEXT STEPS after this tool: 1. Use list_tables_tool to find tables in a database 2. Use describe_table_tool to get table schemas before writing queries This tool retrieves all databases within a specified catalog. Parameters ---------- catalog : str The name of the catalog. ctx : Context FastMCP context (injected automatically) Returns ------- DatabaseListOutput A structured object containing database information. - 'catalog': The catalog name. - 'databases': List of database names. - 'count': Number of databases found. Example Usage for LLM: - When user asks for a specific catalog's databases. - Example User Queries and corresponding Tool Calls: - User: "List all databases in the 'wherobots' catalog." - Tool Call: list_databases('wherobots') - User: "What databases are in the foursquare catalog?" - Tool Call: list_databases('foursquare')
    Connector

Matching MCP Servers

  • A
    license
    C
    quality
    C
    maintenance
    Enables access to Usage and Billing APIs for managing accounts, products, meters, plans, and usage reporting. Supports operations like creating products/plans, reporting usage, and retrieving billing information.
    Last updated
    18
    MIT
  • A
    license
    C
    quality
    C
    maintenance
    Enables interaction with Google Cloud services including billing cost analysis, log querying, and metrics monitoring through natural language commands. Provides comprehensive tools for managing GCP resources, analyzing costs, detecting anomalies, and retrieving operational insights.
    Last updated
    40
    1
    Apache 2.0

Matching MCP Connectors

  • VaultCrux Platform — 60 tools: retrieval, proof, intel, economy, watch, org

  • The Resident Mind gateway. Persistent identity, shared context, workspace-wide AI.

  • Returns the step-by-step setup flow for deploying PayRam as an agent. Covers install, wallet creation, faucet funding, contract deployment, and first payment. Includes chain recommendations (ETH Sepolia for testnet, Base for mainnet), faucet URLs, card-to-crypto prerequisites, and status/recovery commands for interrupted sessions.
    Connector
  • Search recipes by keyword across titles, descriptions, tags, and full source code. Use for any iOS, SwiftUI, or backend topic — e.g. subscription, authentication, camera, animation, chart, onboarding, paywall, infrastructure.
    Connector
  • List all available oracle data feeds: price feeds, off-chain event feeds, and index feeds. Returns catalog with symbol, description, update frequency, and data source. Backend pending (Q3 2026).
    Connector
  • Get full details of a simulation run including timing and results. Returns the complete run record: status, progress, timing (start/end timestamps, duration), compute details (backend, instance type, cost), mesh info, error messages, and result log. Use get_run_status for lightweight polling; use this for final results.
    Connector
  • Get complete hierarchy of catalogs, databases, and tables. ⚠️ WORKFLOW: Use this for a quick overview of all managed catalogs. For external catalogs, use list_catalogs_tool instead. 📋 PREREQUISITES: - Call search_documentation_tool first to understand what data you need 📋 NEXT STEPS after this tool: 1. Use describe_table_tool to get schemas of tables you want to query 2. Use list_catalogs_tool to discover external catalogs not shown here This tool provides a comprehensive view of all available assets in the Wherobots system, including their hierarchical relationships. It can be used to retrieve information about all catalogs, list all databases within those catalogs, and enumerate all tables within each database. *** IMPORTANT LIMITATION: - This tool is being DEPRECATED, but is the only way to get a full hierarchy in one call. - This tool ONLY shows catalogs managed within Wherobots. - External catalogs (e.g., on Databricks, other cloud platforms) are NOT visible in this hierarchy. - If the user mentions specific catalog names that don't appear in the results, they may be external catalogs that need to be accessed differently. - ALWAYS call list_catalogs_tool before or after calling this tool. *** Parameters ---------- ctx : Context FastMCP context (injected automatically) Returns ------- HierarchyListOutput A structured object containing the hierarchy of catalogs, databases, and tables. - 'hierarchy': A dictionary representing the hierarchical structure, where keys are catalog names. Each catalog entry contains a dictionary of its databases. Each database entry includes a list of its tables. Each table entry contains its name. - 'summary': A dictionary providing counts of total catalogs, databases, and tables. Example Usage for LLM: - When user asks for a general overview of data, or specific items across multiple catalogs/databases. - Example User Queries and corresponding Tool Calls: - User: "List all tables in the 'default' database of the 'wherobots' catalog AND in the 'overture_maps_foundation' database of 'wherobots_open_data'." - Tool Call: list_hierarchy() - User: "Show me all databases in 'wherobots' and 'wherobots_open_data' catalogs." - Tool Call: list_hierarchy() - User: "What data is available?" - Tool Call: list_hierarchy()
    Connector
  • <tool_description> Search for products in the Nexbid marketplace. Alias for nexbid_search with content_type='product'. </tool_description> <when_to_use> When an agent needs to discover products (not recipes or services). Convenience alias — delegates to nexbid_search internally. </when_to_use> <combination_hints> list_products → get_product for details → create_media_buy for advertising. For recipes/services use nexbid_search with content_type filter. </combination_hints> <output_format> Product list with name, price, availability, score, and link. </output_format>
    Connector
  • [READ] Aggregated list of paid services swarm.tips agents can spend on. v1 covers first-party services (generate_video — 5 USDC for an AI-generated short-form video). External spend sources (Chutes inference at llm.chutes.ai/v1, x402-paywalled APIs, etc.) are deferred to follow-up integrations. Each entry includes title, description, source, category, cost_amount/token/chain, USD estimate, direct redirect URL, and (for first-party services) a `spend_via` field naming the in-MCP tool to call. Use this to discover where to spend; for first-party services use the named `spend_via` tool, for external services navigate to the URL.
    Connector
  • Is it safe to deploy these changes? Cross-references your changed modules against active constraints, recent incidents, knowledge freshness, and active alerts. Returns a composite verdict (ready/caution/block) with per-module breakdown and actionable recommendations. Use BEFORE deploying to catch constraint violations, recent regressions in the same area, stale knowledge that needs verification, and active alerts that might interact with your changes.
    Connector
  • Get a Stripe billing portal URL for managing payment methods and invoices. Returns a URL (not a redirect) that the human can open in a browser. Requires: API key with read scope. Args: flow: Optional. Set to "payment_method_update" to go directly to the payment method update page. Returns: {"url": "https://billing.stripe.com/p/session/..."}
    Connector
  • List all databases on a site's container. Requires: API key with read scope. Args: slug: Site identifier Returns: {"databases": ["wordpress", "app_db", ...]}
    Connector
  • Record a repayment for an active loan by submitting the on-chain transaction hash. Updates credit score upon confirmation. Backend pending (Q3 2026).
    Connector
  • POST /apps/{appId}/test-suites/{suiteId}/validate — Validate a test suite — Run the suite against a public, non-loopback base URL to capture responses and run assertions. DO NOT use for local-app / localhost validation — the SaaS backend rejects private IPs with 500. For local apps, curl endpoints yourself (Bash) and pass the captured responses into create_test_suite directly. Requires scope: `write`.
    Connector
  • Generate AI-powered platform-optimized content without publishing. Uses AI to create platform-specific text, hashtags, and titles from a prompt or media URL. Respects brand voice profiles if configured. Returns generated content variants for each target platform. Use publish_content to publish the generated content, or publish_ai to generate and publish in one step.
    Connector