Giveready vs Metatool App

A side-by-side look at the Giveready and Metatool App MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Giveready logoGivereadyAggregators · Local subprocess (stdio)Discover verified youth nonprofits with impact data, programmes, and donation links.43FairAuth: not declaredMetatool App logoMetatool AppAggregators · Local subprocess (stdio)MetaMCP is the one unified middleware MCP server that manages your MCP connections with GUI.45FairAuth: no auth required

Verdict: choose Giveready for aggregators work as a local process; choose Metatool App for aggregators as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Giveready logoChoose Giveready when

  • You need dedicated capabilities in the Aggregators domain.
  • You prefer a local stdio subprocess transport.
Explore Giveready

Metatool App logoChoose Metatool App when

  • You need dedicated capabilities in the Aggregators domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Metatool App

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGiveready logoGivereadyMetatool App logoMetatool App
CategoryAggregatorsAggregators
Quality signal43/100 · Fair45/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars02,720
Directory activity 1 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Giveready tools

No tool names declared yet. Check the project README from the listing page.

Metatool App tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Giveready

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "giveready": {
      "command": "npx",
      "args": [
        "giveready-mcp"
      ]
    }
  }
}

Metatool App

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "metatool-ai-metatool-app": {
      "command": "uvx",
      "args": [
        "mcp-hn"
      ]
    }
  }
}

Frequently asked questions

Giveready is categorized under Aggregators and uses a local stdio subprocess. Metatool App belongs to Aggregators and uses a local stdio subprocess. Pick Giveready for aggregators work and Metatool App for aggregators.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Giveready has no declared pricing — check the project's own site. Metatool App is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add giveready and metatool-ai-metatool-app as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Giveready has a quality signal of 43/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Metatool App has 45/100 (Fair) with 3 views, 0 installs and 2,720 GitHub stars.