Support

Last updated: April 26, 2026

1. System Requirements

macOS 14.6 (Sonoma) or later
Apple Silicon or Intel Mac

2. Quick Start

Get MCPizer up and running in 3 steps:

Step 1 — Install

Download MCPizer from the Mac App Store and launch it.

Step 2 — Copy MCP Config

Go to the Config tab inside MCPizer and click Copy to copy the generated JSON configuration snippet:

{
  "mcpServers": {
    "MCPizer": {
      "url": "http://127.0.0.1:3100/mcp"
    }
  }
}

Step 3 — Paste into Your AI Client

Paste the configuration into your AI client's MCP settings file. MCPizer works with:

Claude Desktop
Cursor
Windsurf
Any MCP-compatible client that supports Streamable HTTP transport

That's it — your AI assistant can now call HTTP APIs and browse the web through MCPizer.

3. Known Limitations

HTTP API responses must be in JSON format. The http_request tool is designed for JSON-based HTTP APIs. Non-JSON responses (HTML, XML, plain text, etc.) are not supported. If you enable the Force JSON option, non-JSON responses will return an error directly.

JSON depth truncation — Large JSON responses are automatically truncated at a default depth of 8 levels. Nodes beyond this depth are replaced with summaries to save tokens. Use the explore_json tool to drill into deeper layers.
JSON cache limit — Up to 20 cached JSON responses are kept in memory using an LRU eviction policy. Each cached entry expires after 10 minutes.
HTTP request timeout — All HTTP requests have a 30-second timeout.
Custom tools support GET and POST only — The visual tool builder supports GET and POST methods. For other HTTP methods (PUT, DELETE, PATCH, etc.), use the built-in http_request tool directly.

4. Cookie & Authentication

MCPizer provides flexible cookie management for authenticated API access:

Cookie rules — Define per-domain cookie key-value pairs in the Cookie tab. Enabled rules are automatically injected into HTTP requests matching the domain.
Domain matching — Supports both exact and subdomain matching. For example, a rule for example.com also applies to api.example.com.
Browser sync — The built-in browser's cookies are bidirectionally synced with cookie rules. You can log in via the browser, and the authentication cookies will be automatically available to API requests.

5. FAQ

The Config tab shows a different path than expected

The config path is based on the actual location of the MCPizer app on your system. If you move the app to a different folder, go back to the Config tab and copy the updated configuration.

My AI client can't connect to MCPizer

Make sure MCPizer is running.
Verify the config JSON is pasted correctly in your AI client's MCP settings.
Restart your AI client after updating the configuration.

HTTP requests return errors for non-JSON APIs

MCPizer's http_request tool is designed for JSON APIs. If the target API returns HTML, XML, or plain text, the tool will not be able to parse the response correctly. Consider using only JSON-based endpoints.

Browser data is lost after quitting

The built-in browser uses non-persistent (in-memory) storage by design. Web content data such as local storage and session cookies are cleared when MCPizer quits. Cookie rules you explicitly define in the Cookie tab are persisted.

6. Contact Us

If you need further assistance or want to report a bug, please contact us at 254553782@qq.com.