MCP Gateway

​

What is an MCP Gateway?

• Exposes tools from attached capabilities (built-in, plugins, and connectors)
• Implements the MCP protocol for seamless client integration
• Provides SSE (Server-Sent Events) and HTTP transports
• Supports authentication via API keys or JWT tokens
• Manages request routing and tool execution

​

Creating an MCP Gateway

https://mcp-{gateway-id}.noorle.com

​

Attaching Capabilities

• Built-in Capabilities - Pre-configured services (Web Search, Code Runner, etc.)
• Plugins - Custom WebAssembly tools you’ve created
• Connectors - REST APIs, MCP registry services, or custom MCP servers

​

To Attach a Capability

1. Open your gateway settings
2. Click the Capabilities tab
3. Click Attach Capability
4. Choose capability type (Built-in, Plugin, or Connector)
5. Select from available options
6. Configure optional per-gateway settings
7. Click Save

​

Gateway Specifications

​

Key Specification Fields

​

Omni Tool Configuration

​

Visibility Modes

​

Configuration Example

{
  "omni_tool": {
    "visibility": "Omni"
  }
}

​

Authentication

​

Requiring Authentication

1. Open gateway settings
2. Toggle Require Authentication
3. Choose authentication method:
   • API Key - Static key (easiest for development)
   • JWT Token - Time-bound tokens (better for production)
   • Both - Accept either method

​

Using API Keys

1. In your gateway settings, click API Keys
2. Click Generate API Key
3. Store the key safely (shown only once)
4. Pass in requests via X-API-Key: ak-... header

​

Using JWT Tokens

1. In your gateway settings, click JWT Configuration
2. Configure issuer, audience, and public key
3. Your MCP client will validate tokens using the public key

​

Gateway Endpoints

​

MCP Protocol Endpoint

https://mcp-{gateway-id}.noorle.com

• SSE Transport - Server-Sent Events (recommended for browsers)
• HTTP Transport - Standard HTTP requests with /tools, /resources, /prompts endpoints

​

Status & Health

GET https://mcp-{gateway-id}.noorle.com/health

​

Best Practices

​

Development

• Use public gateways for early testing
• Enable request logging to debug issues
• Attach only capabilities you need

​

Production

• Enable authentication (API Key or JWT)
• Set reasonable rate limits
• Monitor request patterns in usage dashboard
• Use meaningful names for easy identification
• Document attached capabilities in the description

​

Security

• Rotate API keys regularly
• Use JWT tokens with short expiration times
• Audit attached capabilities for permissions
• Restrict sensitive connectors to trusted clients
• Monitor for unusual activity via request logs

​

Monitoring & Troubleshooting

​

Check Gateway Status

1. Go to gateway settings
2. View Status section
3. See recent request metrics and error rates

​

Debug Issues

1. Enable Request Logging in specifications
2. Check logs in Activity tab
3. Verify capabilities are properly attached
4. Test endpoint directly with curl:

curl https://mcp-{gateway-id}.noorle.com/health \
  -H "X-API-Key: ak-..."

​

Common Issues

​

Advanced Configuration

​

Custom Headers

{
  "custom_headers": {
    "X-Custom-Header": "value"
  }
}

​

Request/Response Transformation

{
  "request_transform": {
    "input_mapping": {"user_input": "prompt"}
  },
  "response_transform": {
    "output_path": "$.result"
  }
}

​

API Access

# Create gateway
curl -X POST https://api.noorle.com/v1/mcp-gateways \
  -H "Authorization: Bearer {jwt_token}" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "My Gateway",
    "description": "Testing"
  }'

# Attach capability
curl -X POST https://api.noorle.com/v1/mcp-gateways/{gateway_id}/capabilities \
  -H "Authorization: Bearer {jwt_token}" \
  -H "Content-Type: application/json" \
  -d '{
    "capability_id": "{capability_id}",
    "metadata": {}
  }'

​

Next Steps

• Attach Built-in Capabilities
• Create REST Connectors
• Configure Authentication
• Connect MCP Client
• MCP gateway platform overview