Skip to main content
Glama
726,824 tools. Updated 2026-10-30 23:54

"mcp server fetch" matching MCP tools:

  • Fetch the full content for one id returned by `search`: a rental listing (rental:<uuid>), a plan set (plan:<uuid>) or a published page (page:<route>). Returns {id, title, text, url, metadata}. Always cite the url. Hosts that can call specific tools should prefer get_rental or the resources.
    ConnectorNo auth
  • [ChatGPT Connector compat] Fetch memory by ID. Exists to satisfy ChatGPT Deep Research's required `search`/`fetch` tool contract. Native MCP clients should fetch via `recall` + memory_id, or use the API's GET /memories/{id} endpoint directly. Returns a single memory with citation support (id, title, url, text fields). Args: id: Memory UUID to fetch ctx: MCP context Returns: Dict with id, title, url, text, metadata fields
    ConnectorOAuth
  • Fetch one document's full extracted text by id (a file id from search / search_files / list_files), in the deep-research result shape. ALIAS: this is the SAME read as get_file (same data, same permissions, same audit, same size guard - large files are truncated) - use it when your client requires the id/title/text/url fetch contract (ChatGPT deep research); otherwise prefer get_file, which also serves download links and inline images. Read-only; audited.
    ConnectorNo auth
  • Fetch original text by an opaque id from search or document_outline. Pass ids unchanged. Navigation containers have citable=false and child ids, not source evidence. Historical page identifiers return migration guidance.
    ConnectorNo auth
  • Read one map document by the id a search result handed you. Ids: object:<name>, finding:<id> or finding:<finding_key> (stable across rescans), process:<object type>, metric:<name>, statement:<id> (run-scoped: search again after a rescan), playbook:<id>. It is the second half of the search/fetch pair that connector clients such as ChatGPT require, and returns id, title, text, url and metadata with the direct tools' data flattened to text. If your client can call the direct tools, use them instead (structured, no search first): get_object for an object you can name, get_process for a process, get_metric for a metric, list_findings for findings by status. Use fetch for a result search handed you, or a finding_key.
    ConnectorOAuth
  • Fetch one search result by id. 'site:<site_id>' returns a readable summary of the site (title, live URL, status, storage, dates, first 100 files). 'file:<site_id>:<path>' returns the file's content as UTF-8 text when it is a text type of at most 1 MB, otherwise a short note pointing at its live URL. Returns {id, title, text, url, metadata}.
    ConnectorOAuth

Matching MCP Servers

Matching MCP Connectors

  • web-fetch — fetch ONE public URL live from its origin, verbatim.

  • [生态] modelcontextprotocol 官方参考实现(MIT) — 想 7×24 常驻 → 萬星

  • Read one result found via `search` as plain text with its public page URL, for quoting or citing it in an answer; this is the fetch half of the search/fetch pair. Pass the result's id exactly as search returned it (e.g. "course:..."). Returns {id, title, text, url, metadata}. A course's text is its public catalog summary (name, description, level, duration in hours, price, subjects, topics), not its lessons. A missing document, another site's content, and a type this connection cannot read all return the same not-found error; an id without a type prefix is rejected as invalid. To work with a course rather than quote it, use course_get for its settings record (ids, flags, dates, enrollment count) and course_content_get for its lessons as EditorJS blocks.
    ConnectorAPI key
  • Fetch one or more URLs and return their content as clean markdown. Use this to read articles, documentation, blog posts, or any page where you need the complete text, not just a snippet from search. Also supports PDF, DOCX, and other document formats. Costs 1 credit per URL. Max 10 URLs per request. Failed URLs are not charged. Set include_raw_html=true to also get the raw HTML source in each result. Useful for inspecting embedded URLs, data attributes, iframes, or script tags that are stripped during markdown conversion. May be null for non-HTML content (PDF, DOCX, etc.) and for some sites. Same cost. Returns: results (array of {title, url, content, raw_html, published_time, success, error}), credits_used, credits_remaining. Args: urls: List of URLs to fetch (max 10) include_raw_html: Include raw HTML source in each result (default false)
    ConnectorOAuth
  • Fetch a blob's bytes by id, base64-encoded in the result. Pass 'modelId' to fetch a blob referenced by a specific model (access-scoped); omit it for a direct store fetch. Large blobs may exceed the result-size limit — this channel suits small binaries only.
    ConnectorNo auth
  • Fetch one Indian enactment by the `id` from a `search` result, returning `{id, title, text, url, metadata}`. Also accepts a source URL or a bare path. NOTE: the India corpus serves an enactment as publisher links rather than inline text, so `text` carries the title and `metadata` carries the PDF, HTML and plain-text URLs to read. Prefer `get_act_text` if you can call it.
    ConnectorNo auth
  • ChatGPT connector contract: fetch one article by the id returned from search. Returns the enriched digest (summary, per-ticker analysis, category, relevance) — not the full article body — plus the canonical alphai.io URL for citation. When the article has a published SEC earnings read, text also includes its reported metrics with year-over-year and sequential comparisons, segments, guidance, concerns and missing items. Raises not_found for an unknown id.
    ConnectorAPI key
  • Fetch one node in full by its shareable id (TASK-N/KNOW-N/COMP-N/DOC-N/DIAG-N/EPIC-N/NODE-N), with its edges — this is how you read a full body (recall/search return summaries). Pass version to fetch a historical snapshot instead of the current one.
    ConnectorOAuth
  • Fetch the full published answer for a Pinnacle Ask result. `id` accepts a slug from `search`, an /ask path, or a full pinnacleblooms.org/ask URL. Returns the complete answer document (markdown), Everyday Therapy™ tip, what-to-watch guidance, FAQs, and the canonical URL to cite.
    ConnectorNo auth
  • Return bounded rows for a dataflow — the completion path for hosted clients. Use this when the client cannot execute a client-download plan locally (no shell/filesystem — e.g. a hosted store app or connector) but still needs actual values. ``fetch`` server-side downloads the exact GET/fan-out plan ``build_url`` would produce, concatenates it, runs one bounded literal-equality query, and releases the artifact — the raw dataset never enters model context. Clients that CAN execute locally should keep using ``ask``/``build_url`` and run the plan themselves; ``fetch`` is the affinity-free hosted shortcut, not the power path. POST-only selections have no hosted download path: ``fetch`` raises ``fetch_shape_unsupported`` and the caller must execute the ``build_url`` plan client-side. A rejected/over-length selection raises the same reason ``build_url`` would report; narrow the selection and retry. **``fetch`` does not page, deliberately.** It holds no dataset between calls: every call rebuilds the plan, re-downloads every part from the provider, and releases the artifact. An offset over that would be unsound as well as wasteful — there is no snapshot behind the cursor, so rows shifting upstream between calls would silently skip or duplicate observations, and N pages would mean N full downloads of the same dataflow from an agency that may rate-limit. When a result is ``truncated``, narrow it (``select``, ``where``, ``time_range``) or switch to ``stage_url`` + ``query_dataset``, which pages with ``offset`` over ONE immutable staged artifact and downloads once. Rows are ordered by series key, then period, before ``limit`` applies. A series with a period that cannot be placed unambiguously keeps the provider's order. ``no_records_for_selection`` is TERMINAL, not a fault: the request was well-formed and the source holds no observations for it. Widen the selection or state that no data exists — do not retry the same selection. Only ``upstream_origin_error`` (an origin fault) and ``upstream_rate_limited`` are worth retrying.
    ConnectorOAuth
  • Fetch one result by the id search returned (rh:<address>, sol:<mint> or learn:<slug>). A token id returns the stored read as text with its citation and as-of time; a learn id returns the lesson's full text and, when it has a video, the transcript. Never triggers a scan; a missing read says so.
    ConnectorNo auth
  • Fetch the full text of one directory record by an id returned from search. Ids are prefixed to say which collection they belong to: "product:<id>" or "community:<id>". Call this after search, on the ids it returned, when the lightweight result is not enough to answer the question. It is the second half of the search/fetch pair that deep-research clients expect. Do not call it with an id you constructed yourself or took from a URL — use get_product or get_community for those, which take a bare id and return structured fields instead of text. Prose in, prose out: this returns a readable record, not a typed object.
    ConnectorNo auth
  • Fetch one URL from a residential IP and get the raw response as JSON: status, final URL, headers and body (text or base64), up to 10 MB. GET, HEAD or POST, your own headers, an optional country. No JavaScript rendering. You pay for the megabytes delivered; a fetch that fails is not charged. Pay per call in stablecoins.
    ConnectorNo auth
  • Fetch one public Cannon Studio knowledge record by id after search. Public read-only: no auth, no state changes, no charges; use search first when you do not already have a record id.
    ConnectorNo auth
  • Fetch the full record for an ID returned by search. Routes by prefix to the appropriate register: - company:{number} → Companies House full profile - charity:{number} → Charity Commission full profile - disqualification:{officer_id} → Disqualified director full record - notice:{notice_id} → Gazette notice full legal text
    ConnectorNo auth
  • Fetch compact, curated details for one published hut-to-hut tour. The returned `url` is the canonical huettentouren.org detail page — link users there.
    ConnectorNo auth
  • Fetch full detail for one product by id (from a prior search result). Returns citable text with price, savings, 90-day price history, and buying options.
    ConnectorNo auth