MCP Client
Other (please specify below)
MCP Client Version
Hermes
Authentication Type
OAuth
OAuth Scopes (if applicable)
No response
MCP Server Configuration
`/opt/data/config.yaml`
mcp_servers:
cloudflare:
url: https://mcp.cloudflare.com/mcp?codemode=false
auth: oauth
enabled: true
tools:
exclude:
- docs
- '*_radar_*'
- '*_accounts_magic_*'
- '*_accounts_mnm_*'
- '*_accounts_cni_*'
- '*_accounts_teamnet_*'
- '*_accounts_cloudforceone_*'
- '*_accounts_dlp_*'
- '*_accounts_devices*'
- '*_accounts_dex_*'
- '*_accounts_datasecurity_*'
- '*_accounts_emailsecurity_*'
- '*_accounts_scim_*'
- '*_accounts_gateway*'
- '*_accounts_zerotrust_*'
- '*_accounts_one_*'
- '*_accounts_brandprotection_*'
- '*_accounts_intel_*'
- '*_accounts_urlscanner_*'
- '*_accounts_vuln_scanner_*'
- '*_zones_securitycenter_*'
- '*_accounts_securitycenter_*'
- '*_zones_api_gateway_*'
- '*_zones_schema_validation*'
- '*_zones_token_validation*'
- '*_zones_waiting_rooms*'
- '*_accounts_addressing_*'
- '*_accounts_shares*'
- '*_accounts_slurper_*'
- '*_zones_web3_*'
- '*_accounts_flagship_*'
- '*_zones_secondary_dns_*'
- '*_accounts_secondary_dns_*'
- '*_user_load_balancers*'
Failing Endpoint / Tool
No response
Bug Description
Setting up a new hermes agent and using the built in connector to authenticate the MCP via OAuth.
Hit the same issue as described here: NousResearch/hermes-agent#99984 - specifically bug 1 with the iss parameter validation.
Thought best to raise here for visibility as well
Steps to Reproduce
- Setup new hermes agent
- Use built in connector to auth to cloudflare mcp
- Witness the iss parameter validation error appearing in the hermes UI
Expected Behavior
OAuth flow to work as normal
Actual Behavior
Hermes rejects due to missing iss parameter
Relevant Logs / Error Output
Additional Context
No response
MCP Client
Other (please specify below)
MCP Client Version
Hermes
Authentication Type
OAuth
OAuth Scopes (if applicable)
No response
MCP Server Configuration
Failing Endpoint / Tool
No response
Bug Description
Setting up a new hermes agent and using the built in connector to authenticate the MCP via OAuth.
Hit the same issue as described here: NousResearch/hermes-agent#99984 - specifically bug 1 with the iss parameter validation.
Thought best to raise here for visibility as well
Steps to Reproduce
Expected Behavior
OAuth flow to work as normal
Actual Behavior
Hermes rejects due to missing iss parameter
Relevant Logs / Error Output
Additional Context
No response