MCPRemoteServer
The MCPRemoteServer resource configures routing to external MCP servers.
Purpose
Use MCPRemoteServer to connect your gateway to:
- Public MCP servers (e.g., Context7, DeepWiki)
- Internal MCP servers running outside your cluster
- Third-party MCP services
Example
apiVersion: mcp-gateway.ohcs.io/v1alpha1
kind: MCPRemoteServer
metadata:
name: context7
namespace: default
spec:
gatewayRef:
name: my-gateway
path: /context7
url: https://mcp.context7.com/mcp
transport: httpKey Fields
spec.gatewayRef
Reference to the MCPGateway that will route to this server.
spec.path
URL path on the gateway for this server (e.g., /context7).
spec.url
The URL of the remote MCP server.
spec.transport
Transport type:
sse- Server-Sent Events (default)http- Standard HTTP
spec.headers
Custom headers to include in requests to the remote server. Useful for authentication.
Authentication
For authenticated servers, use secrets to pass API keys or tokens in headers.
Example: Firecrawl MCP Server
Firecrawl provides a remote hosted MCP server that requires Bearer token authentication:
apiVersion: mcp-gateway.ohcs.io/v1alpha1
kind: MCPRemoteServer
metadata:
name: firecrawl
namespace: default
spec:
gatewayRef:
name: my-gateway
path: /firecrawl
url: https://mcp.firecrawl.dev/v2/mcp
transport: http
headers:
- name: Authorization
valueFrom:
secretKeyRef:
name: firecrawl-credentials
key: token
---
apiVersion: v1
kind: Secret
metadata:
name: firecrawl-credentials
namespace: default
type: Opaque
stringData:
token: "Bearer fc-YOUR_API_KEY"Related Resources
- MCPGateway - Gateway configuration
- MCPContainerServer - Containerized MCP servers