Fetch Extract

io.github.CedricKoumaPublished by GitHub account CedricKoumav0.1.0Updated Oct 24, 2026

MCP server (stdio): fetch web pages as clean readable markdown via the AgentForge API

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

MCP server that fetches web pages and returns them as clean, readable markdown through the AgentForge API.

What you can do
  • Fetch web pages and get their content back as clean, readable markdown.
  • Content retrieval is handled by the AgentForge API rather than by the assistant directly.
  • Available as a remote endpoint or as a local stdio process via the npm package agentforge-fetch-extract-mcp.
When to use it
Useful when an assistant needs to read the text of a web page in a tidy markdown form, for example to summarize or quote an article, without handling raw HTML.
Requirements
An AgentForge APIM subscription key, supplied as the Ocp-Apim-Subscription-Key header or the AGENTFORGE_API_KEY environment variable; a free tier is said to work for smoke tests. Network access to the AgentForge gateway, whose base URL can be set with AGENTFORGE_BASE_URL. Local use needs Node.js for the npm package.
Before you install
The subscription key is a secret sent as a header or environment variable; keep it out of shared configs. Page URLs and fetched content pass through the third-party AgentForge gateway. The manifest lists no tools, so the exact operations are not documented here.

Installation

In SourceWeft

  1. Open Fetch Extract in the dashboard and add it to a workspace.
  2. Connect Ocp-Apim-Subscription-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.CedricKouma%2Ffetch-extract/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "fetch-extract": {
      "type": "http",
      "url": "https://apim-agentforge-6lfm33.azure-api.net/fetch-extract/mcp",
      "headers": {
        "Ocp-Apim-Subscription-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.