MCP Gateway
The MCP (Model Context Protocol) Gateway enables AI coding assistants like Claude Code, Cursor, and Roo Code to securely connect to MCP servers through Requestyβs unified API, providing tool access, authentication management, and comprehensive analytics.
What is MCP?
The Model Context Protocol is an open standard that enables AI assistants to interact with external tools and services. Through MCP, your AI coding assistant can:- π§ Access databases and execute queries
- π Manage files and repositories
- π Interact with web services and APIs
- π€ Use specialized AI tools and models
- π Connect to productivity platforms (Notion, Linear, Asana)
Key Benefits
Universal Compatibility
Works with Claude Code, Cursor, Roo Code, and any MCP-compatible AI tool
Centralized Management
Single dashboard to manage all MCP servers and authentication across your organization
Enterprise Security
AES-256 encryption, organization isolation, and granular access controls
How It Works
- Register MCP Servers: Admins configure MCP server URLs and authentication
- Whitelist Tools: Select specific tools from each server to make available
- Manage Keys: Configure authentication (org-wide or per-user)
- Use Tools: AI assistants automatically discover and use available tools
- Monitor Usage: Track performance, costs, and usage patterns
Feature Overview
Server Management
Register, configure, and manage MCP servers for your organization
User Key Management
Enterprise users can manage their personal API keys for MCP servers
Analytics & Monitoring
Monitor and analyze MCP server usage, performance, and user activity
AI Tool Integration
Connect Claude Code, Cursor, Roo Code and other AI assistants
Authentication Models
Requesty supports two authentication approaches depending on your plan:Standard Plan: Organization-Wide Keys
For non-enterprise organizations, authentication is managed at the organization level:1
Admin Configuration
Organization admins configure API keys for each MCP server
2
Shared Access
All users in the organization share the same authentication
3
Simplified Management
Single point of configuration for the entire team
Enterprise Plan: Per-User Keys
Enterprise organizations can enable individual authentication:1
Admin Setup
Admins register servers and define required authentication headers
2
User Configuration
Each user provides their own API keys through the dashboard
3
Individual Access
Users authenticate with their personal credentials
Important Enterprise Distinction:
- Admins can choose whether users are allowed to add their own keys
- If disabled, only organization-wide keys are used (same as Standard plan)
- This provides flexibility between convenience and security
Quick Start
1. Enable MCP Gateway
Navigate to Settings β Integrations β MCP Gateway in your Requesty dashboard.2. Add Your First Server
- Use Template
- Custom Server
Choose from pre-configured templates for popular services:
- GitHub: Repository management and code search
- Notion: Workspace and content management
- Linear: Issue tracking and project management
- Context7: Advanced AI context management
- Asana: Task and project coordination
3. Explore and Select Tools
Click Explore Server to discover available tools, then select which ones to enable:4. Configure Authentication
- Organization Key (Admin)
- User Keys (Enterprise)
Set organization-wide authentication in the server configuration:
5. Connect Your AI Tool
Configure your AI coding assistant to use Requestyβs MCP gateway:- Claude Code
- Cursor
- Roo Code
Claude Code automatically discovers MCP servers through your Requesty API key.
No additional configuration needed.
Supported MCP Servers
Popular Templates
GitHub
GitHub
- URL:
https://api.githubcopilot.com/mcp/
- Features: Repository management, code search, pull requests, issue tracking
- Authentication: Personal GitHub token required
Notion
Notion
- URL:
https://mcp.notion.com/mcp
- Features: Page management, database queries, content creation
- Authentication: Notion integration token required
Linear
Linear
- URL:
https://mcp.linear.app/sse
- Features: Issue management, project tracking, team collaboration
- Authentication: Linear API key required
Context7
Context7
- URL:
https://mcp.context7.com/mcp
- Features: AI context management, knowledge graphs, semantic search
- Authentication: Context7 API key required
Protocol Support
Currently, the MCP Gateway supports HTTP-based MCP servers (streamable-http and SSE protocols). Support for stdio-based servers is coming soon.
Protocol | Status | Description |
---|---|---|
streamable-http | β Supported | Standard HTTP with JSON streaming |
sse | β Supported | Server-Sent Events for real-time updates |
stdio | π§ Coming Soon | Direct process communication |
Analytics & Monitoring
Track your MCP usage with comprehensive analytics:Key Metrics
Request Volume
Total MCP server requests and trends over time
Average Latency
Response times for each server and tool
Success Rate
Percentage of successful tool executions
Tool Usage
Most frequently used tools and servers
Usage Dashboard
Monitor real-time and historical MCP usage through the intuitive web dashboard:- Real-time Metrics: Live monitoring of active MCP requests and server status
- Historical Analysis: Trend analysis over time periods (24h, 7d, 30d)
- Server Breakdown: Usage statistics per MCP server and tool
- Performance Insights: Latency distribution and error rate tracking
- User Activity: Individual usage patterns (Enterprise only)
Security & Compliance
Encryption
- At Rest: All API keys and sensitive headers encrypted with AES-256
- In Transit: TLS 1.3 for all MCP communications
- Key Storage: Encrypted database with automatic key rotation
Access Control
- Standard Plan
- Enterprise Plan
- Organization admins manage all MCP servers
- Users can view available tools but cannot modify
- Shared authentication across the organization
Data Isolation
- Complete separation between organizations
- No cross-organization data access
- Isolated request routing and analytics
Best Practices
Tool Selection
Tool Selection
- Only enable tools your team actually needs
- Review tool descriptions and permissions carefully
- Test tools in a development environment first
- Regularly audit enabled tools for security
Key Management
Key Management
- Rotate API keys regularly (every 90 days)
- Use separate keys for development and production
- Never share personal API keys
- Immediately revoke compromised keys
Performance Optimization
Performance Optimization
- Monitor latency metrics for each server
- Disable unused tools to reduce overhead
- Use caching for frequently accessed data
- Configure appropriate timeout values
Security Guidelines
Security Guidelines
- Review MCP server documentation before connecting
- Validate server certificates and URLs
- Use environment-specific configurations
- Enable audit logging for compliance
Troubleshooting
Common Issues
Server exploration fails
Server exploration fails
Symptoms: Cannot discover tools from MCP serverSolutions:
- Verify the server URL is correct
- Check authentication headers are properly configured
- Ensure the server supports MCP protocol
- Test connectivity with curl or Postman
Tools not appearing in AI assistant
Tools not appearing in AI assistant
Symptoms: Registered tools donβt show in Claude/CursorSolutions:
- Confirm tools are selected and saved
- Restart your AI assistant
- Check your Requesty API key is valid
- Verify organization permissions
Authentication errors
Authentication errors
Symptoms: 401/403 errors when using toolsSolutions:
- Verify API keys are correctly entered
- Check if keys have required permissions
- For enterprise: ensure user keys are configured
- Confirm keys havenβt expired
Plan Features
MCP Gateway usage is included in your Requesty plan:Feature | Standard | Enterprise |
---|---|---|
MCP Server Registration | β Unlimited | β Unlimited |
Organization-wide Keys | β | β |
Per-user Keys | β | β |
Tool Whitelisting | β | β |
Basic Analytics | β | β |
Advanced Analytics | β | β |
Audit Logs | β | β |
Custom RBAC | β | β |
MCP requests count toward your regular API usage. There are no additional charges for using the MCP Gateway.
Coming Soon
- π Stdio Protocol Support: Direct process-based MCP servers
- π― Smart Tool Recommendations: AI-powered tool suggestions
- π Cost Allocation: Per-user and per-project MCP cost tracking
- π Secrets Management: Integrated vault for API keys
- π Global Edge Deployment: Reduced latency worldwide
Need Help?
Contact our support team at [email protected] or visit our GitHub repository for examples and updates.