Skip to main content
Glama
132,563 tools. Last updated 2026-05-11 02:21

"General search for file-related information" matching MCP tools:

  • Get contents of multiple files from a remote public git repository in a single call. Reduces round-trips when you need to read several related files. Max 10 files per batch, 5000 total lines budget across all files. Each file supports optional line ranges. Failed files return per-file errors without blocking other files.
    Connector
  • Search 70+ biological databases. SYNTAX: biobtree_search(terms="entity") BEFORE SEARCHING - Use your training knowledge to plan: 1. What type of entity is this? (disease, process, drug, gene, protein) 2. What is the query asking for? (drugs, genes, function, etc.) 3. What equivalent terms might give better results? (e.g., "temperature homeostasis" is a process → related condition is "fever") 4. Choose best entry point for query type (disease terms for drug queries) WORKFLOW: 1. Search WITHOUT dataset filter first (discover where entity exists) 2. Use IDs from results with biobtree_map QUERY PATTERNS (choose based on question): "DRUG FOR DISEASE/CONDITION X": - Prefer disease terms (mesh/mondo/efo) over GO terms for drug queries - If search only returns GO term, search for the related CONDITION instead (e.g., "temperature homeostasis" → search "fever" instead) - Search disease → mondo → clinical_trials → chembl_molecule - OR search drug class directly (e.g., "antipyretic", "NSAID", "antibiotic") - Verify mechanism for top 2-3 drugs only (don't enumerate all proteins!) "DRUG TARGETS" (use BOTH paths for complete picture): - chembl: >>chembl_molecule>>chembl_target>>uniprot (mechanism-level) - pubchem: >>pubchem>>pubchem_activity>>uniprot (protein-level, often 50+ targets) - Filter approved: >>chembl_molecule[highestDevelopmentPhase==4] "DISEASE GENES": - Search disease → mondo/hpo → gencc/clinvar/orphanet → hgnc "PROTEIN FUNCTION": - Search protein → uniprot → go/reactome "MECHANISM QUERIES" (drug-disease): - Use biobtree_entry to see what's connected (xrefs) - Check EDGES to see where each xref leads - Follow connections relevant to your question - Build chain: Drug → Target → [connections] → Disease RETURNS: id | dataset | name | xref_count
    Connector
  • Full-text search across recall reasons and product descriptions using PostgreSQL text search. Finds recalls mentioning specific terms (e.g. 'salmonella contamination', 'mislabeled', 'sterility'). Supports multi-word queries ranked by relevance. Filter by classification, product_type, or date range. Related: fda_search_enforcement (search by company name, classification, status), fda_recall_facility_trace (trace a recall to its manufacturing facility).
    Connector
  • Server-side regex text search over indexed project source files. Free tier: requires file_path (single file). Premium tier (XMP4_PREMIUM_GREP_WALK=true): allows file_glob multi-file walk. Prefer xmp4_tests_for/xmp4_usages for SCIP symbols — grep is for text not indexed (comments, literals, config keys).
    Connector
  • Loads one supported self-assessment into the widget by slug. Use `gad7` for anxiety screening, `phq9` for depression screening, and `who5` for general well-being screening when the user wants to take one of those assessments.
    Connector
  • Edit a file in the solution's GitHub repo and commit. Two modes: 1. FULL FILE: provide `content` — replaces entire file (good for new files or small files) 2. SEARCH/REPLACE: provide `search` + `replace` — surgical edit without sending full file (preferred for large files like server.js) Always use search/replace for large files (>5KB). Always read the file first with ateam_github_read to get the exact text to search for.
    Connector

Matching MCP Servers

  • A
    license
    -
    quality
    C
    maintenance
    Enables blazingly fast file and content searching in large codebases using ripgrep, with intelligent filtering, fuzzy finding, and directory tree visualization while respecting .gitignore and avoiding common bloat directories.
    Last updated
    11
    2
    MIT
  • F
    license
    -
    quality
    C
    maintenance
    Enables intelligent file searching in local directories using natural language queries. Supports searching by file type, filename patterns, and content across multiple formats including PDF, Word, Excel, and text files with AI-powered relevance scoring.
    Last updated

Matching MCP Connectors

  • Manage files and folders directly from your workspace. Read and write files, list directories, cre…

  • 4 web-search tiers (x402 USDC on Base) - simple/medium/deep/cached. Free health.

  • Search the ShippingRates database by keyword — matches against carrier names, port names, country names, and charge types. Use this for exploratory queries when you don't know exact codes. For example, search "mumbai" to find port codes, or "hapag" to find Hapag-Lloyd data coverage. Returns matching trade lanes, local charges, and shipping line information. FREE — no payment required. Returns: { trade_lanes: [...], local_charges: [...], lines: [...] } matching the keyword. Related tools: Use shippingrates_port for structured port lookup by UN/LOCODE, shippingrates_lines for full carrier listing.
    Connector
  • Returns usage statistics for your ThinkNEO API key. Shows calls today, this week, this month, monthly limit, remaining calls, top tools used, estimated cost, and current tier. Works without authentication (returns general info).
    Connector
  • Returns general information about the Makuri platform, including mission, target users, founding details, and company information. Use this tool when the user asks 'what is Makuri', 'who made it', or wants a general overview.
    Connector
  • Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.
    Connector
  • Search the web using Bing. Returns organic results, related searches and more. Alternative to Google for web search with different ranking algorithms and results.
    Connector
  • Book a handyman for general home repairs: furniture assembly, TV mounting, drywall patching, door fixes, minor plumbing fixtures, and similar non-specialist tasks. Returns a confirmed booking. Call /quote first.
    Connector
  • Search FDA Structured Product Labeling (SPL) data — full drug package inserts. Filter by drug name, manufacturer, application number, or specific label section (e.g., indications_and_usage, warnings, adverse_reactions, boxed_warning). Returns complete label text for matching sections. Related: fda_search_drugs (application-level data), fda_search_ndc (NDC product details).
    Connector
  • Get closed/resolved support tickets with pagination (20 per page) and search. Returns summary info only — use get_ticket with the case number to get full ticket details including notes, files, and collaborators. Supports filtering by subject/description text, platform (renaissance, api, general, overture, winners), and priority (1=Low, 2=Medium, 3=High). # fetch_closed_tickets ## When to use Get closed/resolved support tickets with pagination (20 per page) and search. Returns summary info only — use get_ticket with the case number to get full ticket details including notes, files, and collaborators. Supports filtering by subject/description text, platform (renaissance, api, general, overture, winners), and priority (1=Low, 2=Medium, 3=High). ## Parameters to validate before calling - search (string, optional) — Search by subject or description (case-insensitive) - platform (string, optional) — Filter by platform: renaissance, api, general, overture, winners - priority (number, optional) — one of: 1, 2, 3 — Filter by priority: 1 (Low), 2 (Medium), 3 (High) - page (number, optional) — Page number for pagination (default: 1, 20 tickets per page)
    Connector
  • Search FDA drug shortages by generic name, company, status, or availability. Drug shortages signal manufacturing capacity strain, quality issues, or supply chain disruption. Useful for identifying companies with operational challenges. Related: fda_search_drugs (drug application data by company), fda_search_ndc (NDC-level product details).
    Connector
  • Search for code snippets and examples in official Microsoft Learn documentation. This tool retrieves relevant code samples from Microsoft documentation pages providing developers with practical implementation examples and best practices for Microsoft/Azure products and services related coding tasks. This tool will help you use the **LATEST OFFICIAL** code snippets to empower coding capabilities. ## When to Use This Tool - When you are going to provide sample Microsoft/Azure related code snippets in your answers. - When you are **generating any Microsoft/Azure related code**. ## Usage Pattern Input a descriptive query, or SDK/class/method name to retrieve related code samples. The optional parameter `language` can help to filter results. Eligible values for `language` parameter include: csharp javascript typescript python powershell azurecli al sql java kusto cpp go rust ruby php
    Connector
  • Use this when the user mentions a place, neighbourhood, landmark, or area but does not give exact coordinates. Examples: 'near the Louvre', 'in Trastevere', 'around Times Square', "walking distance from St Paul's Cathedral". Returns experiences matched first by exact venue/neighbourhood, then by city centre fallback. Do not use for general city-wide search; use search_experiences for that.
    Connector
  • Search the web via Brave Search API with local QVAC LLM cleaning. Returns cleaned markdown summaries. Use for general web research, factual lookups, and topic exploration.
    Connector
  • Searches Brave's Place Search API. A single call may populate any combination of `results` (POIs), `cities`, `addresses`, `streets`, and `location` (the resolved search area), depending on the query shape. Use for POIs near coordinates or a named area, browsing general POIs (omit `query`, supply coords or `location`), disambiguating bare city names, resolving specific addresses, or looking up streets. Anchor via `latitude`+`longitude` or `location`; with neither, `query` is required.
    Connector
  • Get open support tickets with pagination (20 per page) and search. Returns summary info only — use get_ticket with the case number to get full ticket details including notes, files, and collaborators. Supports filtering by subject/description text, platform (renaissance, api, general, overture, winners), and priority (1=Low, 2=Medium, 3=High). # fetch_open_tickets ## When to use Get open support tickets with pagination (20 per page) and search. Returns summary info only — use get_ticket with the case number to get full ticket details including notes, files, and collaborators. Supports filtering by subject/description text, platform (renaissance, api, general, overture, winners), and priority (1=Low, 2=Medium, 3=High). ## Parameters to validate before calling - search (string, optional) — Search by subject or description (case-insensitive) - platform (string, optional) — Filter by platform: renaissance, api, general, overture, winners - priority (number, optional) — one of: 1, 2, 3 — Filter by priority: 1 (Low), 2 (Medium), 3 (High) - page (number, optional) — Page number for pagination (default: 1, 20 tickets per page)
    Connector