Skip to content

Add MCPRelay - Secure web access and crawling service for AI agents #2296

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

chetan1arora
Copy link

Description

This PR adds MCPRelay to the MCP servers directory - a production-ready MCP server that provides secure web access and crawling for AI agents through smart-proxy selection.

Server Details

  • Server: MCPRelay (new third-party server addition)
  • Changes to: README.md (adding new server entry to the official integrations list)

Motivation and Context

MCPRelay fills a critical need in the MCP ecosystem by providing:

  • Secure web access for AI agents that need to fetch content from websites
  • Smart proxy selection to handle sites with bot detection or geographic restrictions
  • Support for multiple proxy types (datacenter, residential, mobile)
  • Professional service with transparent pricing and usage analytics

This enables AI agents to reliably access web content that would otherwise be blocked or restricted.

How Has This Been Tested?

  • Live service deployed at api.mcprelay.dev
  • Tested with Claude Desktop using the MCP client
  • Successfully fetches content from various websites including those with bot protection
  • NPM package published and actively used by the community
  • Dashboard and analytics working at mcprelay.dev

Breaking Changes

None - this is a new server addition that doesn't affect existing functionality.

Types of changes

  • New feature (non-breaking change which adds functionality)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

MCPRelay follows MCP best practices with proper tool schemas, error handling, and secure authentication via API keys.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant