What is the key difference between Wundervault MCP and Fetch?

Wundervault MCP belongs to the Other Tools and Integrations category with local stdio execution, while Fetch belongs to the Other Tools and Integrations category with local stdio execution.

How do I install Wundervault MCP or Fetch 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 Wundervault MCP and Fetch free or paid?

Wundervault MCP operates under a Free / Open Source model (API Key required). Fetch operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Wundervault MCP lists 6 tools with 1 views and 2 GitHub stars. Fetch lists 4 tools with 2 views and 90,185 GitHub stars.

Can I use both Wundervault MCP and Fetch 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

Wundervault MCP vs Fetch

In-depth architectural comparison of the Wundervault MCP and Fetch 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

Wundervault MCP

Other Tools and Integrations · Local stdio

Quality: 63/100 (Good) | Auth: API Key required

Fetch

Other Tools and Integrations · Local stdio

Quality: 75/100 (Great) | Auth: No auth required

Verdict Summary: Choose Wundervault MCP if you need specialized Other Tools and Integrations tools running via a local process. Choose Fetch if your workspace requires Other Tools and Integrations integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Wundervault MCP when:

You need dedicated capabilities in the Other Tools and Integrations domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: WUNDERVAULT_AGENT_VAULT_URL, WUNDERVAULT_AGENT_VAULT_API_KEY, WUNDERVAULT_AGENT_KEY.
Primary tools included: vault_entries_list, vault_entry_get, vault_exec.

Explore Wundervault MCP Details

Choose Fetch when:

You need dedicated capabilities in the Other Tools and Integrations domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Fetches web content over HTTP, Converts web pages for efficient LLM usage, Reference implementation demonstrating MCP SDK usage.

Feature & Specification Comparison

Specification	Wundervault MCP wundervault Other Tools and Integrations	Fetch VerifiedOther Tools and Integrations
Summary	Zero-knowledge secret vault for AI agents: use API keys, passwords, and SSH keys to run real commands (exec/rsync) with the secret injected into a single command — never returned to the model or shown in chat. Client-side AES-256-GCM, per-agent scoping, append-only audit log.	Web content fetching and conversion for efficient LLM usage.
Category & Scope

Tools & Capabilities Breakdown

Wundervault MCP Tools (6)

vault_entries_list

List all vault entries available to this agent. Returns entry IDs and secret names — no values.

vault_entry_get

Retrieve and decrypt a vault secret. Optionally execute a command with it.

vault_exec

Execute a shell command with a vault secret injected as an env var — locally or on a remote host over SSH. The secret is injected into the subprocess and the buffer is zeroed immediately after spawn; escape patterns are rejected before decryption.

vault_entry_inject_env

Write a vault secret directly into a config file (`~/.npmrc`, `~/.netrc`, `~/.docker/config.json`, or a project `.env`) without the plaintext passing through the agent.

vault_rsync

Sync a local directory to a remote host using rsync over SSH, with the SSH key fetched from the vault (temp keyfile deleted immediately after transfer).

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).

Wundervault MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "wundervault-wundervault-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@wundervault/mcp-server"
      ],
      "env": {
        "WUNDERVAULT_AGENT_VAULT_URL": "YOUR_WUNDERVAULT_AGENT_VAULT_URL_HERE",
        "WUNDERVAULT_AGENT_VAULT_API_KEY": "YOUR_WUNDERVAULT_AGENT_VAULT_API_KEY_HERE",
        "WUNDERVAULT_AGENT_KEY": "YOUR_WUNDERVAULT_AGENT_KEY_HERE"
      }
    }
  }
}

Fetch Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "fetch": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ]
    }
  }
}

Frequently Asked Questions

Wundervault MCP is categorized under Other Tools and Integrations and uses a local stdio subprocess. In contrast, Fetch belongs to Other Tools and Integrations using local stdio subprocess. Select Wundervault MCP when you need capabilities focused on other tools and integrations and Fetch when you require tools for other tools and integrations.