Skip to main content
Glama
341,535 tools. Last updated 2026-07-30 11:30

"Querying a PostgreSQL database using natural language input" matching MCP tools:

  • Search the iHerb product database using a natural-language query, benefit keyword, ingredient name, or brand name. Uses the PostgreSQL GIN full-text search index first (fast, relevance-ranked), then falls back to a broader ILIKE scan if FTS yields no results.
    Connector
  • List the tables and their columns on a DataCanvas staged by openmeteo_get_historical, openmeteo_get_ensemble, openmeteo_get_flood, or openmeteo_get_climate. Call this first to discover table names before querying with openmeteo_dataframe_query.
    Connector
  • Provisions a managed PostgreSQL database on a dedicated VM on your private network. Requires a recent plan_managed_datastore. For app deployments, prefer deploy_app database:'managed' so plan_deploy includes and wires the DB automatically. It is PRIVATE — reachable only from another instance on the same private network, via the DB's internal/private IP (not a public address). Get the ids from plan_managed_datastore/list_flavors/list_private_networks/list_keypairs. Provisioning takes ~5 min; poll list_databases until status='ready', then the connection details (private_ip, port 5432, db_name, db_user) are populated.
    Connector
  • Search for data assets using identifier matching, keyword search, semantic similarity, or hybrid fusion. Use 'identifier' mode (default) when you know the asset name or a pattern (supports * wildcards). Use 'keyword' when searching by domain terms or metadata keywords. Use 'semantic' for natural language queries about what the data represents. Use 'hybrid' to combine all approaches for the best recall. Returns a ranked list of matching assets with identifiers, types, and relevance scores.
    Connector
  • Live corpus statistics, contributor list, tool surface, and orientation links (agent-entry handshake, limitations, claims registry). Use this to orient before querying.
    Connector
  • List all shipping lines in the ShippingRates database with per-country record counts. Use this to discover which carriers and countries have data before querying specific tools. Returns each carrier's name, slug, SCAC code, and a breakdown of available D&D tariff and local charge records per country. FREE — no payment required. Returns: Array of { line, slug, scac, countries: [{ code, name, dd_records, lc_records }] } Related tools: Use shippingrates_stats for aggregate totals, shippingrates_search for keyword-based discovery.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • FEMA disasters, NOAA weather alerts, USGS earthquakes. 4 tools.

  • Access comprehensive company data including financial records, ownership structures, and contact information. Search for businesses using domains, registration numbers, or LinkedIn profiles to streamline due diligence and lead generation. Retrieve historical financial performance and complex corporate group structures to support informed business analysis.

  • Search commercial real estate listings. Returns paginated hits with facet counts. For AI-driven search, call interpret_search first to convert a natural-language query into structured filters, then pass those filters — and its bounds, when present — here.
    Connector
  • Delete a project and all its deployments from sota.io. This action is PERMANENT and irreversible. It removes the project, all deployments, the managed PostgreSQL database, environment variables, and webhooks. The project slug will become available again after deletion.
    Connector
  • Translate a natural-language property-search sentence into a structured filter payload compatible with search_listings. Use this as a transparent intermediate step: pass the user's raw query here, then forward the returned filters — and the returned bounds, when present (they carry the "near <place>" intent) — to search_listings.
    Connector
  • Search live UK workspace listings on FrankSpace. Filter by location text (city, postcode, submarket), size band, and maximum monthly price (pence). For richer natural-language queries prefer `ai_search`.
    Connector
  • Search through a user's LinkedIn bookmarks using either keyword (text) search or semantic (meaning-based) search. Supports all list_bookmarks filters, full-text search via the q field, and semantic search via the vector_search_term field for natural language or topic-based queries. IMPORTANT: At least one of 'q', 'vector_search_term', or 'author' must be provided. If the user asks to find posts by a specific author (e.g., 'Show posts by John Doe', 'Find posts from Suresh sambantham'), use the 'author' parameter instead of putting the author name in the 'q' field. Use 'q' for searching post content, not for filtering by author.
    Connector
  • Create a new project on sota.io. Each project automatically provisions: (1) a managed PostgreSQL 17 database accessible via the DATABASE_URL environment variable (auto-injected, no configuration needed), (2) PgBouncer connection pooling (pool size 20, max 100 clients), (3) automatic daily database backups with 7-day retention, (4) a live URL at https://{slug}.sota.io with automatic HTTPS via Let's Encrypt. The project slug is auto-generated from the name (lowercase, hyphens, max 63 chars) and is immutable after creation. Supported frameworks: Next.js, Node.js (Express/Fastify/Koa), Python (Flask/FastAPI/Django), or any language via custom Dockerfile. You can also add up to 5 custom domains per project with automatic HTTPS (via API: POST /v1/projects/:id/domains with {domain: "yourdomain.com"}). DNS: A record to 23.88.45.28 for apex domains, CNAME to {slug}.sota.io for subdomains. Optionally associate the project with a public git repository at create-time by passing `git_url` (and optional `git_branch`). The association is informational — it shows up in the dashboard and the `sota deploy --git` CLI flag can default to it — but does NOT enable auto-deploy-on-push yet.
    Connector
  • Returns metadata for a specific SIDRA table. Features: - General info (name, survey, subject, periodicity) - Available territorial levels - Variable list with units - Classifications and categories - Available periods Use this tool to understand table structure BEFORE querying data with ibge_sidra. Examples: - Population table metadata: tabela="6579" - Census 2022 metadata: tabela="9514" - PNAD unemployment: tabela="4714" Use this after finding a table code (ibge_sidra_tabelas) and before querying with ibge_sidra. Behavior: read-only and idempotent — a live GET against the public IBGE SIDRA API. Returns Markdown.
    Connector
  • Search public prediction markets for markets relevant to a natural-language topic or question. Use when you need candidate markets, market URLs, outcomes, statuses, and relevance scores. Do not use for a final probability forecast, market-history lookup, trading, or private/internal data. Scores are relevance scores, not probabilities.
    Connector
  • Use this when a user asks how many database connections to configure in their connection pool, or is troubleshooting PostgreSQL connection exhaustion. Takes CPU cores, app instances, and max_connections. Returns recommended pool size per instance with utilization ratio.
    Connector
  • Map any list of hex values into a target archive using CIEDE2000 nearest-neighbour matching. Each input hex is matched to the closest named colour in the chosen archive, with a delta-e relevance band (exact / close / approximate / loose) and full provenance. Use to translate a client's paint colours into Shakespeare language, map a brand palette into historical Japanese pigments, or find the nearest Oxfordshire equivalents to a French scheme.
    Connector
  • Find the best prediction market for a natural-language question or trading intent. Returns the best cross-venue match, current probability, liquidity, and any arbitrage opportunity between venues.
    Connector
  • Edit ONE scene with a natural-language note (the same director chat the editor UI uses): move/restyle/add/remove layers and overlays, retime, etc. Synchronous — returns the applied mutations + updated scene. Use list_scenes to find scene ids; for notes spanning the whole video use project_director_note instead.
    Connector
  • Natural-language contractor search. Pass a free-form Russian brief (e.g. "хочу каркасный дом 180 кв.м в Подмосковье до 15 млн") and get top-N matching contractors plus an explanation of how the brief was parsed. Returns JSON with: parsed filters, matches list, explanation.
    Connector
  • Ask the directory a customer question in natural language. Returns schema.org cards of businesses that genuinely answer it (LLM-reranked, strictly from the directory — never invented) + grounding links. Use when the customer describes a NEED rather than a search term.
    Connector