369 Federation Db049f00

Federation Guide - External Registry Integration

The MCP Gateway Registry supports federation with external registries, allowing you to import and manage servers/agents from multiple sources through a unified interface.

Supported Federation Sources

Quick Setup

1. Environment Variables

Add to your .env file:

# Anthropic MCP Registry (no auth required)
ANTHROPIC_REGISTRY_ENABLED=true

# Workday ASOR (requires OAuth credentials and token)
ASOR_CLIENT_ID=your_client_id
ASOR_CLIENT_SECRET=your_client_secret
ASOR_TENANT_NAME=your_tenant_name
ASOR_HOSTNAME=your_host_name

2. Federation Configuration

Create or update ~/mcp-gateway/federation.json:

{
  "anthropic": {
    "enabled": true,
    "endpoint": "https://registry.modelcontextprotocol.io",
    "servers": []
  },
  "asor": {
    "enabled": true,
    "endpoint": "https://wcpdev-services1.wd103.myworkday.com/ccx/api/asor/v1/awsasor_wcpdev1",
    "auth_env_var": "ASOR_ACCESS_TOKEN",
    "agents": []
  }
}

3. Start Services

./build_and_run.sh

Anthropic MCP Registry Integration

Configuration

{
  "anthropic": {
    "enabled": true,
    "endpoint": "https://registry.modelcontextprotocol.io",
    "servers": [
      {"name": "io.github.jgador/websharp"},
      {"name": "another-server-name"}
    ]
  }
}

Configuration Options

Import Specific Servers for Anthropic

Option 1: Configuration File

{
  "anthropic": {
    "servers": [
      {"name": "io.github.jgador/websharp"},
      {"name": "modelcontextprotocol/filesystem"},
      {"name": "modelcontextprotocol/brave-search"}
    ]
  }
}

Import All Available Servers for Asor

Set servers to empty array:

{
  "asor": {
    "servers": []
  }
}

Workday ASOR Integration

Prerequisites

1. Workday ASOR Access: Valid Workday tenant with ASOR enabled
2. OAuth Credentials: Client ID and Secret for ASOR API
3. Access Token: Valid OAuth token with "Agent System of Record" scope

Step 1: Get OAuth Token

Add to .env:

# ASOR OAuth Credentials
ASOR_CLIENT_ID=your_client_id
ASOR_CLIENT_SECRET=your_client_secret
ASOR_TENANT_NAME=your_tenant_name
ASOR_HOSTNAME=your_host_name

Use the provided token generator:

```bash
python3 get_asor_token.py

This will:

1. Generate authorization URL
2. Guide you through OAuth flow
3. Provide access token for .env file

Step 2: Environment Configuration

OAuth Access Token (generated by get_asor_token.py)

ASOR_ACCESS_TOKEN=your_oauth_token_here

### Step 3: Federation Configuration

```json
{
  "asor": {
    "enabled": true,
    "endpoint": "https://wcpdev-services1.wd103.myworkday.com/ccx/api/asor/v1/awsasor_wcpdev1",
    "auth_env_var": "ASOR_ACCESS_TOKEN",
    "agents": []
  }
}

Configuration Options

Token Management

Token Expiration: ASOR tokens expire every 4 hours. You'll need to:

1. Monitor logs for authentication errors
2. Regenerate tokens using python3 get_asor_token.py
3. Update .env with new token
4. Restart services to apply new token

Automated Token Refresh (Future Enhancement):

# Set up cron job for token refresh
0 */3 * * * cd /path/to/mcp-gateway && python3 get_asor_token.py --auto-update

Visual Identification

Federated servers and agents are visually tagged in the UI:

Server Cards (MCP Servers Tab)

• ANTHROPIC: Purple gradient badge for Anthropic MCP Registry servers

Agent Cards (A2A Agents Tab)

• ASOR: Orange gradient badge for ASOR-sourced agents

Troubleshooting

Common Issues

1. Anthropic Servers Not Importing

# Check logs
docker-compose logs registry | grep -i anthropic

# Verify connectivity
curl https://registry.modelcontextprotocol.io/servers

# Check configuration
cat ~/mcp-gateway/federation.json

2. ASOR Authentication Errors

# Check token in logs
docker-compose logs registry | grep -i asor

# Verify token
echo $ASOR_ACCESS_TOKEN

# Test token manually
curl -H "Authorization: Bearer $ASOR_ACCESS_TOKEN" \
     https://wcpdev-services1.wd103.myworkday.com/ccx/api/asor/v1/awsasor_wcpdev1/agentDefinition

3. Duplicate Entries

• ASOR agents should only appear in A2A Agents tab
• If appearing in both tabs, check federation service logs for duplicate registration

Debug Mode

Enable detailed federation logging:

# Add to .env
FEDERATION_DEBUG=true
LOG_LEVEL=DEBUG

# Restart services
docker-compose restart registry

Log Analysis

# Federation startup
docker-compose logs registry | grep -i "federation.*enabled"

# Sync operations
docker-compose logs registry | grep -i "sync.*servers\|sync.*agents"

# Authentication
docker-compose logs registry | grep -i "token\|auth"

# Errors
docker-compose logs registry | grep -i "error\|failed"

Advanced Configuration

Custom Endpoints

For enterprise deployments with custom registry endpoints:

{
  "anthropic": {
    "endpoint": "https://your-custom-mcp-registry.company.com"
  },
  "asor": {
    "endpoint": "https://your-workday-tenant.myworkday.com/ccx/api/asor/v1/your_tenant"
  }
}

Selective Import

Import only specific servers/agents:

{
  "anthropic": {
    "servers": [
      {"name": "modelcontextprotocol/filesystem"},
      {"name": "modelcontextprotocol/brave-search"}
    ]
  },
  "asor": {
    "agents": [
      {"id": "aws_assistant"},
      {"id": "data_analyst"}
    ]
  }
}

Security Considerations

Token Security

1. Environment Variables: Store tokens in .env, never in code
2. Token Rotation: Regularly rotate ASOR tokens
3. Access Control: Limit federation access to admin users
4. Audit Logging: Monitor federation sync operations

Network Security

1. HTTPS Only: All federation endpoints use HTTPS
2. Firewall Rules: Allow outbound HTTPS to federation endpoints
3. Proxy Support: Configure HTTP proxy if required

# Proxy configuration in .env
HTTP_PROXY=http://proxy.company.com:8080
HTTPS_PROXY=http://proxy.company.com:8080

API Reference

Federation Endpoints

Response Examples

Federation Status:

{
  "enabled_federations": ["anthropic", "asor"],
  "anthropic": {
    "enabled": true,
    "last_sync": "2024-01-15T10:30:00Z"
  },
  "asor": {
    "enabled": true,
    "last_sync": "2024-01-15T10:25:00Z"
  }
}

Sync Response:

{
  "success": true,
  "results": {
    "anthropic": {
      "synced": 25,
      "errors": 0,
      "duration_ms": 1250
    },
    "asor": {
      "synced": 3,
      "errors": 0,
      "duration_ms": 850
    }
  }
}

Contributing

1. New Federation Sources: Guidelines for adding new sources
2. Bug Reports: How to report federation issues
3. Feature Requests: Process for requesting new federation features
4. Testing: How to test federation changes

Last Updated: November 2024

ASOR to Agent Card Field Mapping

This section documents how ASOR agent data is mapped to the MCP Gateway Registry Agent Card format.

Field Mapping Table

ASOR Data Structure

Based on the actual ASOR API response, the agent data structure is:

{
  "capabilities": {
    "stateTransitionHistory": false,
    "pushNotifications": false,
    "streaming": true
  },
  "url": "https://bedrock-agentcore.us-west-2.amazonaws.com/runtimes/arn%3Aaws%3Abedrock-agentcore%3Aus-west-2%3A218208277580%3Aruntime%2Faws_assistant-XYx9SWFOvW/invocations?qualifier=DEFAULT",
  "description": "None",
  "name": "aws_assistant",
  "supportsAuthenticatedExtendedCard": false,
  "workdayConfig": [
    {
      "skillId": "skill_extractContent"
    },
    {
      "skillId": "skill_searchQuery"
    }
  ],
  "skills": [
    {
      "id": "skill_extractContent",
      "description": "Extract and parse content from up to 20 URLs simultaneously",
      "name": "extractContent"
    },
    {
      "id": "skill_searchQuery",
      "description": "Performs a search query using Tavily Search and returns comprehensive results including answer, images, and search results",
      "name": "searchQuery"
    }
  ],
  "version": "1"
}

Available but Unmapped ASOR Fields

The following ASOR fields are available but not currently mapped:

1. capabilities - Object with streaming, notifications, state history flags
2. workdayConfig - Array of skill configurations
3. supportsAuthenticatedExtendedCard - Boolean flag for extended card support

Missing Fields from ASOR

The following Agent Card fields are not provided by ASOR:

1. Security Configuration

   • security_schemes - No authentication schemes provided
   • security - No security requirements specified

2. Licensing

   • license - License information not available

Recommendations

To improve ASOR integration:

1. Map available fields:

   streaming=agent_data.get("capabilities", {}).get("streaming", False)
   metadata={
       "capabilities": agent_data.get("capabilities", {}),
       "workdayConfig": agent_data.get("workdayConfig", []),
       "supportsAuthenticatedExtendedCard": agent_data.get("supportsAuthenticatedExtendedCard", False)
   }
   

2. Request additional fields from ASOR API:

   • License information
   • Security/authentication schemes