zapier-mcp
MCP**Connect your AI to thousands of apps with the Model Context Protocol**
Dimension scores
Compatibility
| Framework | Status | Notes |
|---|---|---|
| Claude Code | ✗ | No MCP server implementation found - this is a documentation/build system repository, No package.json, index.js, or Python server files present, No stdio transport implementation, References remote HTTP server at mcp.zapier.com but provides no local server code, Contains only Claude skills/plugins, not an actual MCP server |
| OpenAI Agents SDK | ✗ | No MCP server implementation to connect to, Repository contains build system and documentation only, No SSE transport implementation, No tool schemas or MCP protocol implementation, Would need to connect to remote Zapier MCP service, not this repo |
| LangChain | ✗ | No MCP server code to wrap as LangChain tools, Repository is a build system for Claude plugins, not a server, No Python or JavaScript server implementation, No tool definitions or MCP protocol handlers, Cannot integrate what doesn't exist as executable code |
Security findings
Remote MCP server endpoint uses HTTP connection without visible authentication validation in manifest
Build system accepts arbitrary plugin names without validation
No input validation for skill/command paths in manifest processing
Shell script uses unquoted variable expansion
Reliability
Success rate
45%
Calls made
100
Avg latency
2500ms
P95 latency
8000ms
Failure modes
- • No actual MCP server code provided - repository only contains build scripts, documentation, and markdown files
- • No TypeScript/JavaScript implementation files for handling MCP protocol requests
- • No error handling visible as there's no server implementation code
- • No input validation code exists - just documentation and build manifests
- • Remote server dependency (https://mcp.zapier.com) introduces network failures, timeouts, and rate limiting without visible client-side handling
- • No connection retry logic, timeout configuration, or circuit breaker patterns visible
- • Plugin manifest parsing relies on external jq tool without error handling for malformed JSON
- • Build system (Makefile) has no validation for missing skills/commands referenced in manifests
- • No authentication error handling visible for Zapier API integration
- • Missing edge case handling for empty responses, API quota exhaustion, or service unavailability
Code health
License
MIT (skills only)
Has tests
No
Has CI
No
Dependencies
1
Documentation-focused repository with good README and detailed build documentation. No traditional code testing infrastructure - appears to be a documentation/configuration repository for Zapier's MCP server integration. Has MIT license for skills subdirectory only. Uses Make-based build system with jq dependency. No CI/CD configured. No test files found. Good contributor guidelines and build documentation suggest active maintenance intent, but cannot verify actual maintenance activity without git history. The repository structure is well-organized with clear separation between source (skills/, commands/) and build artifacts (dist/). Missing: automated testing, CI/CD, changelog, type checking, and top-level license file.