Pull Request Description

Changes

Added special handling for Zapier MCP server endpoints to differentiate between OAuth-authenticated (/a/) and server-specific URL (/s/) connection types.

(Types of connectivity with Zapier)

The OAuth discovery process now intelligently skips discovery for server-specific Zapier MCP server URLs while maintaining full OAuth flow support.

Implementation Details

1. Changes done on_discover_metadata method inOAuth class (libraries/python/mcp_use/auth/oauth.py)
   • Added URL parsing logic to detect Zapier MCP server endpoints
   • https://mcp.zapier.com/api/mcp/s/ endpoint (Pre-authenticated)**: RaisesOAuthDiscoveryError so that it will be handled as no authentication
   • https://mcp.zapier.com/api/mcp/a/* endpoint (OAuth)**: Proceeds with standard OAuth metadata discovery flow
   • Maintains existing edge case pattern (similar to GitHub API handling)

Example Usage (Before)

# Before: OAuth discovery would fail for Zapier /s/ endpoints with generic errorfrommcp_useimportMCPClient,MCPAgent# Zapierconfig= {"mcpServers": {"zapier": {"url":"https://mcp.zapier.com/api/mcp/s/XXXXXXXXX/mcp",        }    }}

This would attempt OAuth discovery

Example Usage (After)

No change, the system will handle as if there is no authentication

Testing

Describe how you tested these changes:

I've performed manual testing on both the oauth and direct url with Zapier

Backwards Compatibility

N/A - it does not impact any existing functionality as it is mainly to handle Zapier edge case scenario

Related Issues

Closes#309