Pocketnook vs Foundry Zksync

In-depth architectural comparison of the Pocketnook and Foundry Zksync 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.

Which MCP Server Should You Choose?

P

Choose Pocketnook 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).
• Primary tools included: deploy, deploy_directory, list_nooks.

Explore Pocketnook Details

Choose Foundry Zksync 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).
• Primary tools included: init, compile, test.

Explore Foundry Zksync Details

Feature & Specification Comparison

Specification	P Pocketnook Developer Tools	Foundry Zksync Developer Tools
Summary	Deploy repositories or local folders to private Pocketnook URLs from any MCP client.	Expose foundry-zksync (forge, cast, anvil-zksync) tools for zkSync Era development
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

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

{
  "mcpServers": {
    "pocketnook": {
      "command": "npx",
      "args": [
        "-y",
        "@pocketnook/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "foundry-zksync": {
      "command": "npx",
      "args": [
        "-y",
        "foundry-zksync-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons