What is the key difference between EdgarTools and FetchRelay?

EdgarTools belongs to the Developer Tools category with local stdio execution, while FetchRelay belongs to the Developer Tools category with cloud HTTP/SSE execution.

How do I install EdgarTools or FetchRelay in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are EdgarTools and FetchRelay free or paid?

EdgarTools operates under a Free / Open Source model (No auth required). FetchRelay operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

EdgarTools lists 0 tools with 0 views and 2,679 GitHub stars. FetchRelay lists 0 tools with 0 views and 0 GitHub stars.

Can I use both EdgarTools and FetchRelay together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

EdgarTools vs FetchRelay

In-depth architectural comparison of the EdgarTools and FetchRelay MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

EdgarTools

Developer Tools · Local stdio

Quality: 44/100 (Fair) | Auth: No auth required

FetchRelay

Developer Tools · Remote HTTP/SSE

Quality: 42/100 (Fair) | Auth: No auth required

Verdict Summary: Choose EdgarTools if you need specialized Developer Tools tools running via a local process. Choose FetchRelay if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose EdgarTools when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore EdgarTools Details

Choose FetchRelay when:

You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore FetchRelay Details

Feature & Specification Comparison

Specification	EdgarTools Developer Tools	F FetchRelay Developer Tools
Summary	Open-source SEC EDGAR toolkit — 11 tools, 7 prompts, every filing type. No API key required.	Extract public webpages as Markdown, map sites, and run bounded crawl jobs. API key required.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

EdgarTools Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

FetchRelay Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

EdgarTools Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "edgartools": {
      "command": "uvx",
      "args": [
        "--from"
      ]
    }
  }
}

FetchRelay Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "fetchrelay": {
      "url": "https://fetchrelay.com/integrations/mcp?utm_source=mcp&utm_medium=integration&utm_campaign=mcp-launch"
    }
  }
}

Frequently Asked Questions

EdgarTools is categorized under Developer Tools and uses a local stdio subprocess. In contrast, FetchRelay belongs to Developer Tools using remote streaming HTTP/SSE transport. Select EdgarTools when you need capabilities focused on developer tools and FetchRelay when you require tools for developer tools.

More alternatives to EdgarTools More alternatives to FetchRelay Developer Tools category hub