Skip to main content
Glama
812,483 tools. Updated 2026-11-20 19:09

"A search for the greeting 'hi'" matching MCP tools:

  • Search JobYap job postings by natural-language query. Matches job titles, falling back to significant keywords when the full phrase finds little. Returns result ids, titles and citable URLs for use with fetch. For structured filtering (location, company, remote, freshness) prefer search_jobs.
    ConnectorNo auth
  • Owners only (needs sign-in): Sets the speech model voice for this business's phone line (inbound and every place_phone_call), until changed again. Default is Aoede. Pass a Gemini prebuilt voice name (letters only, e.g. "Aoede", "Puck"); pass an empty string to reset to the default. place_phone_call cannot pick a different voice per call — set it here or read phone.call_voice in receptionist_service. Tone and language on a specific outbound call belong in place_phone_call's purpose; the inbound opening line belongs in front_desk greeting (update_front_desk).
    ConnectorNo auth
  • Connectivity check that confirms the Nordic MCP server process is responding. Use this at the start of a session to verify the server is reachable before making other calls. Do not use as a proxy for database health — the server can respond while the Qdrant vector database is temporarily unavailable. To confirm data availability, call search_filings directly. Returns: A greeting string: "Hello {name}! Nordic MCP server is running."
    ConnectorNo auth
  • Rewrite a field's text to work better as an AI system prompt; returns the improved text. field ∈ persona | task | greeting | storyline_task | storyline_opening | storyline_ai_trigger | storyline_ai_criteria | skill_description | skill_instructions | kb_description | kb_instructions — determines the rewrite target (a Task should read like commands, a KB description says "what's inside / when it's relevant", a skill description says "when to use" in one line, …). current = the current text (empty = draft from scratch); hint = the direction you want this time (empty = general polish); context = on-site context (which KB is being edited, values of sibling fields) — the more specific, the better the fit. Returns only the improved text, no explanation, no wrapper — the caller places it next to the original for a human to accept or reject.
    ConnectorNo auth
  • Search the TCLP knowledge graph using fusion search (semantic + BM25). Args: query: Free-text search query (max 1000 characters). node_type: Content scope — "tclp" (clauses, glossary terms, guides) or "all". Laws, regulations, standards and frameworks are not searchable here: use `find_legal_resources`. content_type: Return only one content type: "clause", "glossary_term" or "guide". Omit to search every type. limit: Maximum number of results to return (1–50). rerank: Whether to apply RRF reranking when combining graph and text results. include_full_text: Include each hit's full body text (Markdown). Off by default — bodies are large; request only when you need the content, and prefer a small `limit` when you do. Returns: JSON with "meta" (totals, timing) and "results" (ranked hits with title, url, content_type, scores, summary, optionally relationships_text, related and full_text). `summary` is short plain text: the clause summary, the first paragraph of a glossary definition, or a guide's excerpt. It is null when the item has none. `child_name` is a clause's child name (e.g. "Odhran's Clause"), null for other content and for a clause that has none; text search also matches it. Each hit's "references" lists the instruments it cites: pass a reference's `work_id` to `get_legal_resource` for details. A reference's `edge` (governs, references, describes) says how the content relates to the instrument; it is not a statement of the instrument's legal effect. An empty list means the hit cites no instruments. null with "lrsf" in meta.degraded means references could not be loaded: do not conclude that the hit cites no instruments.
    ConnectorNo auth
  • Search the TCLP knowledge graph using fusion search (semantic + BM25). Args: query: Free-text search query (max 1000 characters). node_type: Content scope — "tclp" (clauses, glossary terms, guides) or "all". Laws, regulations, standards and frameworks are not searchable here: use `find_legal_resources`. content_type: Return only one content type: "clause", "glossary_term" or "guide". Omit to search every type. limit: Maximum number of results to return (1–50). rerank: Whether to apply RRF reranking when combining graph and text results. include_full_text: Include each hit's full body text (Markdown). Off by default — bodies are large; request only when you need the content, and prefer a small `limit` when you do. Returns: JSON with "meta" (totals, timing) and "results" (ranked hits with title, url, content_type, scores, summary, optionally relationships_text, related and full_text). `summary` is short plain text: the clause summary, the first paragraph of a glossary definition, or a guide's excerpt. It is null when the item has none. `child_name` is a clause's child name (e.g. "Odhran's Clause"), null for other content and for a clause that has none; text search also matches it. Each hit's "references" lists the instruments it cites: pass a reference's `work_id` to `get_legal_resource` for details. A reference's `edge` (governs, references, describes) says how the content relates to the instrument; it is not a statement of the instrument's legal effect. An empty list means the hit cites no instruments. null with "lrsf" in meta.degraded means references could not be loaded: do not conclude that the hit cites no instruments.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    面向 Codex、WorkBuddy 等 AI 工具的知你AI助手合并版 Skills,涵盖当前会话分诊、客户查询与画像、历史会话检索、客户分群和 API Key 用量查询,并连接个微、企微、视频号、微信小程序、公众号、服务号、微信客服、微信小店、抖音号、小红书、微博、网站及H5客服等渠道。
    MIT No Attribution
  • A
    license
    Not graded
    quality
    A
    maintenance
    . A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{
    7,386 npm
    MIT

Matching MCP Connectors

  • Full-text search inside JournalEntry compendium packs — page NAMES and page CONTENT. The tool for rules/lore text ("what does grappled say?" → query "grappled", pageTypes ["rule"]; class write-ups, spell lists): compendium-search sees only document names. Requires bridge module 8.11.0+. Each match carries the PAGE uuid — pass it to uuid-resolve for the full text. matchedIn tells what matched: name matches win (content not scanned, snippet null); content matches carry a ~200-char snippet. Query is a case-insensitive substring; packs are scanned in order until limit, results unsorted.
    ConnectorAPI key
  • Search this Cubite site's courses by keyword and get each match's public page URL, for linking to or citing it. This is the search half of the search/fetch pair that ChatGPT connectors and deep research require. The whole query is matched as one case-insensitive phrase, so use one or two distinctive words. Courses match on name or description and are listed in name order; a course without a URL slug has no public page and is never returned, while courses hidden from the catalog are. Returns up to 10 results as {id, title, url}; pass a result's id to `fetch` for its citable text. It is not an inventory: to list, count or manage courses use course_list, which has no keyword filter but returns every course, with or without a slug, with its id, settings and enrollment count.
    ConnectorAPI key
  • List a company's bank statement transactions, newest first, paged, with totalCount. Each has acDocumentId, date, amount, currency, movement, bank account, title, description and status (documentRequired while it needs a document or coding). Pass acDocumentId as transactionId to get-transaction-conversation, add-transaction-comment or list-transaction-cashcoding-recommendations. It has no text search; dateFrom and dateTo are inclusive. For ledger entries in every account, use search-accounting-transactions.
    ConnectorOAuth
  • Creates a new Google Ads campaign with a budget. The campaign is always created paused: it shows no ads and spends nothing until it is switched on in a separate step. SEARCH campaigns are created with Google search on, Search partners off, the Display Network off, and location targeting set to PRESENCE (people in the targeted locations). Pass search_partners, display_network or geo_target_type to choose other values. On a campaign of any other channel type, each of these three settings is set only when its argument is passed. Search campaigns have no language setting: Google Ads removed it in late September 2026 and matches Search ads to searchers by the language the ads are written in, so write the ads in the language customers search in. Searches in another language that cost money are stopped with add_negative_keywords. languages sets a DISPLAY campaign's language setting in the same request as the campaign; without it the campaign has no language setting, may show to people who use any language, and the result says so. languages is refused on SEARCH. SHOPPING is turned off until Shopping campaign creation is complete: a Shopping campaign needs a Merchant Center account, a feed label and a product group, which this tool does not set yet, so it is refused before anything is sent. VIDEO is refused before anything is sent: the Google Ads API cannot create or change Video campaigns. MULTI_CHANNEL (App) is refused before anything is sent: an App campaign needs an app ID, an app store and a bidding goal, which this tool does not set. The budget and the campaign are created together in one request, so if Google refuses the campaign no budget is left behind. The budget belongs to this campaign alone (it is not a shared budget). A channel type or bidding strategy outside the lists below, a strategy the channel type does not take, or a target missing or given to the wrong strategy, is refused before anything is sent. Bidding strategies by channel type: SEARCH: MANUAL_CPC, TARGET_SPEND, MAXIMIZE_CONVERSIONS, TARGET_CPA, MAXIMIZE_CONVERSION_VALUE, TARGET_ROAS. DISPLAY: MANUAL_CPC, TARGET_SPEND, MAXIMIZE_CONVERSIONS, TARGET_CPA, TARGET_ROAS. Google does not offer MAXIMIZE_CONVERSION_VALUE without a target ROAS on Display campaigns. Args: customer_id: The Google Ads customer ID (numbers only, no hyphens). name: The name for the new campaign. budget_amount_micros: Daily budget in micros of the account's currency (10000000 = 10.00: ₹10 on an INR account, $10 on a USD one). advertising_channel_type: Channel type. One of: SEARCH, DISPLAY. Default: SEARCH. SHOPPING is turned off until Shopping campaign creation is complete; VIDEO is refused (the Google Ads API cannot create Video campaigns); MULTI_CHANNEL (App) is refused (it needs an app ID, an app store and a bidding goal this tool does not set). For Performance Max use create_performance_max_campaign. status: Initial campaign status: PAUSED, the only status a build takes. Every campaign is built paused and is switched on in a separate step; ENABLED is refused, and nothing in that call runs. Default: PAUSED. bidding_strategy_type: Bidding strategy. One of: MANUAL_CPC, MAXIMIZE_CONVERSIONS, MAXIMIZE_CONVERSION_VALUE, TARGET_CPA, TARGET_ROAS, TARGET_SPEND, as the channel type takes it (list above). Default: MANUAL_CPC. target_cpa_micros: Target CPA in micros of the account's currency. Required with TARGET_CPA, refused with any other strategy. target_roas: Target ROAS (e.g., 2.0 for 200%). Required with TARGET_ROAS, refused with any other strategy. cpc_bid_ceiling_micros: Maximize Clicks' max CPC cap — the most Google may bid for one click — in micros of the account's currency (10000000 = 10.00: ₹10 on an INR account, $10 on a USD one). Only with bidding_strategy_type TARGET_SPEND. Optional. start_date: Campaign start date in YYYY-MM-DD format. Optional. end_date: Campaign end date in YYYY-MM-DD format. Optional. search_partners: Whether ads may serve on the Google Search Partners network. SEARCH default: False. Optional. display_network: Whether ads may serve on the Google Display Network. SEARCH default: False. Optional. geo_target_type: Positive location targeting. One of: PRESENCE (only people in the targeted locations), PRESENCE_OR_INTEREST (also people elsewhere who show interest in them), SEARCH_INTEREST. SEARCH default: PRESENCE. Optional. languages: Google Ads language codes (e.g. en, hi, es, pt, de, fr, ja, zh_CN) a DISPLAY campaign may show to. ["all"] sets no language setting on purpose. Refused on SEARCH. Optional. over_comfort_ack: The user's own words or reason when they asked for a budget above their saved comfort (e.g. "user asked for 6,000/day on 2026-09-23"). Recorded with the change by the hosted connector; never sent to Google. Optional. Returns: Dictionary with created campaign and budget resource names; on a DISPLAY campaign also the language codes set (an empty list means every language). Tools revision: 7a2c68c7.
    ConnectorOAuth
  • Answers "are we showing up in AI search for X" from the visibility results Hi, Moose has stored for a project: the prompts the brand tracks, run on AI engines (ChatGPT, Perplexity, Gemini and others) and scored for brand mention and citation. Pass the user's question or topic in their own words; Hi, Moose matches it to the tracked prompts, in any language. Returns, per engine, whether the brand was mentioned or cited in the latest run and in an earlier run so the change is visible, the mention and citation rates over the window, a short excerpt from the latest answer where the brand appeared, the prompts matched, and other brands seen in those answers. Each excerpt carries an answer id; call visibility_get_answer with it when the user wants the full text of that answer. Results cover the tracked prompts on the tracked engines only, never the whole of AI search; state the window and sample size plainly and never claim causation. When no tracked prompt matches, the result lists the topics the project tracks; tell the user and suggest adding a prompt on the Visibility screen in Hi, Moose. Reads stored results only, it does not run new checks. Takes a few seconds.
    ConnectorOAuth
  • Creates a "listen to this article" audio episode in Hi, Moose: a two-voice spoken conversation about the content, rendered as an MP3 and hosted by Hi, Moose, plus the HTML snippet for the embeddable player to paste into the page. The source is required: the url of a live page, the draftId of a saved draft (from create_draft or list_drafts), or the content as text with a title (at least 1200 characters). Before calling, if the user named no voices, length or player look, offer the settings page once: https://himoose.com/hi-moose-mcp/audio/ lets them hear every voice, pick the length, language and player look, and copy a settings line to paste back here; map that line onto these parameters. If they decline or say to go ahead, call with the defaults (Sulafat and Fenrir, short, dark full player). Rendering takes about 5 minutes for short, 9 for standard and 15 for deep, and the host device works on nothing else meanwhile. If the result says the episode is still rendering, call get_audio_embed with the audioId a few minutes later. The audio plays on the project's own domain and on himoose.com; to hear it before publishing, the user pastes the snippet into the preview box on the settings page. Give the snippet to the user in full, in a code block. Voices: Sulafat (warm, measured, female); Fenrir (curious, lively, male); Zephyr (bright, crisp, female); Puck (upbeat, playful, male); Charon (informative, steady, male); Kore (firm, direct, female); Leda (youthful, light, female); Orus (firm, grounded, male); Aoede (breezy, open, female); Callirrhoe (easy-going, relaxed, female); Autonoe (bright, quick, female); Enceladus (breathy, soft, male); Iapetus (clear, precise, male); Umbriel (easy-going, calm, male); Algieba (smooth, low, male); Despina (smooth, warm, female); Erinome (clear, neutral, female); Algenib (gravelly, textured, male); Rasalgethi (informative, measured, male); Laomedeia (upbeat, animated, female); Achernar (soft, gentle, female); Alnilam (firm, confident, male); Schedar (even, level, male); Gacrux (mature, rich, female); Pulcherrima (forward, assertive, female); Achird (friendly, easy, male); Zubenelgenubi (casual, loose, male); Vindemiatrix (gentle, calm, female); Sadachbia (lively, bright, male); Sadaltager (knowledgeable, assured, male).
    ConnectorOAuth
  • Find the best-matching PAGES for a query, ranked by how many of your query terms each page covers. Searches one wiki if `wiki` is given, otherwise every active wiki. Each result has its wiki, path, matched terms, and a short snippet for orientation — then read_document the page to get the answer. Returns a `confident` flag: if false, the wiki(s) likely lack this — fall back to web search.
    ConnectorNo auth
  • For research and citation lookups (deep research): free-text search of live Northern Cyprus (KKTC/TRNC) property listings on Evlek, in Turkish, English, Russian, German or Arabic. Returns matching listings as id/title/url, newest first (sale and rent as two groups when the query names neither). The answer language follows the language of the query. OpenAI deep-research compatible format, for research and citation clients. Use when: the caller only has a free-text query ("2+1 apartment in Kyrenia under 150000 pounds", "EVL-100464"). Not for: structured filters, paging or choosing the answer language.
    ConnectorNo auth
  • Search the Melvea local honey directory by free-text query and return matching producers as a list of results (id, title, url). Designed for ChatGPT Deep Research and Company Knowledge. Use for any local-honey discovery query that names or implies a place; the tool parses place and varietal from the query. Returns an honest empty list when nothing matches — never fabricate. Pair with fetch to retrieve full producer detail.
    ConnectorNo auth
  • List the MU × JiuFlow sponsored gi's 17 sponsor placements with each logo's slot, brand, position, finished size, thread color, logo file/url, status (ok=hi-res | low=low-res | request=not collected | missing), and consent (yes=written permission to embroider on apparel | requested | no). ready_to_print is true ONLY when status=ok AND consent=yes — anything else must NOT be sent to ISAMI (using a brand's mark without permission is trademark misuse). Owner-only.
    ConnectorNo auth
  • Create a NEW campaign (saved as 'draft' — it does NOT start sending until the user activates it in the app). BEFORE calling, ask the user which campaign type they want unless they already said it — never choose it yourself: 1. Outreach with 2 messages: visit → connect (48 h) → message 1 (24 h) → message 2 (7 days) 2. Outreach with 1 message: visit → connect (24-48 h) → message 1 (48 h) 3. Nurturing – 3 messages: visit → connect (24-48 h) → messages after 24 h, 5 days, 7 days 4. Connection only: visit → connect (12-48 h), no messages 5. Existing connections – 3 messages: messages now, after 5 days, after 7 days (1st-degree connections only) 6. One-off message to existing connections: one message (1st-degree connections only). Confirm the planned steps with the user first. Provide a name, the profile_id to send from, and an ordered list of steps. Each step has an action ('connect', 'message' or 'visit'), an optional delay_hours (wait before this step), and AI/template settings for messages. Returns the new campaign_id. Use add_contacts_to_campaign next to add leads. MESSAGE PLACEHOLDERS (for ai_template / when use_ai is false, also cleaned up after AI): - {oslovení} or [Oslovení]/[Jméno] → Czech vocative greeting (e.g. 'pane Nováku' / first-name vocative like 'Petře') - {{first_name}} or {jméno}/{jmeno} or [Name]/[first_name] → contact first name - {{company}} or {firma} or [Firma]/[Company] → company name ({firma} = sender company from sender_context; {{company}}/[Firma] = lead's company) - {{jmeno_5p}} → Czech first-name vocative ('Petře'); {{prijmeni_5p}} → Czech surname vocative without 'pane' ('Kubíčku', women unchanged) - Language: when the sample/prompt is English (or the prompt says 'in English'), Czech salutation rules are off and all name variables give plain names ('Hi Petr,') - Also: {{last_name}}, {{full_name}}, {{position}}, {{location}}, {{headline}} - {{company_info}} → one-sentence description of what the lead's company does. Optional: it exists only if you saved it with update_contact (company_info, e.g. from read_company_website); if missing, it falls back to the generic "ve firmě". Never invent it. Prefer {{first_name}} / {{company}} / {oslovení} in new templates; square brackets like [Jméno] and [Firma] are supported aliases.
    ConnectorAPI key
  • Create or fully replace a page playbook. `context` is the page background the **server** injects for the agent — write "who lands on this page, what they are deciding, what they usually worry about"; do NOT write facts like prices or quotas (those belong in a knowledge base, which also ranks higher in authority). `url_pattern` is a glob (`*/pricing`, `*/solutions/*`), matches the path only, ignores query strings and trailing slashes; without it the page must report the key explicitly. Resolution order: explicit key > url_pattern > default. `greeting_mode="generated"` produces the greeting and suggested questions on the fly in the visitor's language (recommended); `"static"` uses your fixed `greeting` / `questions`. **This is a full replace**: fields you don't pass fall back to defaults rather than staying as they are. To change one field, `list_page_contexts` first, merge, then send.
    ConnectorNo auth
  • Search tasks across the workspace. Ranked lexical search over title and description: exact and prefix matches rank first, then word-boundary, substring, and fuzzy matches, with recency and status factored in. Multi-word queries match in any order. Searches every state by default, completed and archived included. Use this when the user names a task by its words; use task_list to browse a view (Today, Inbox, …) and task_show once you have the task number.
    ConnectorNo auth
  • Search tasks across the workspace. Ranked lexical search over title and description: exact and prefix matches rank first, then word-boundary, substring, and fuzzy matches, with recency and status factored in. Multi-word queries match in any order. Searches every state by default, completed and archived included. Use this when the user names a task by its words; use task_list to browse a view (Today, Inbox, …) and task_show once you have the task number.
    ConnectorNo auth
  • Search every public dataset on Mostly Right and return up to 20 matches, most relevant first, as {results: [{id, title, url, snippet, matching_table, why}]}, where `id` is the dataset slug, `url` its canonical page, and snippet, matching_table and why say what matched. No account needed. Example: {"query": "hourly airport weather observations"}. Pass a result's `id` straight to fetch for the full dataset document. This is the plain search-and-fetch pair; search_datasets is the richer, paged version with topics, publishers and summaries. matching_table can name a raw input table. Tables named source_* hold raw inputs; prefer main_table from list_tables.
    ConnectorNo auth