Add support for client credentials method when connecting to remote MCP | Voters

Add support for client credentials method when connecting to remote MCP

complete

Ryan Anderson

We want to connect to an existing MCP server that supports "Client credentials" .

It is hosted in AWS agentcore and we need port to support "Client credentials" to connect to the MCP server.

Created by Haim Natan

May 18, 2026

Sagi Keren

updated the status to

complete

Client credentials auth is now available - read about it here https://docs.port.io/agent-management/ai-registry/mcp-connectors/#supported-server-types

Sagi Keren

updated the status to

in progress

Mike Longlais

Looking for the same thing to be able to add the Port MCP server to our Gemini Enterprise deployment as a data source using oauth2 OBO. It supports PKCE but requires:
MCP Server URL: https://mcp.us.port.io/v1
Authorization URL: https://mcp.us.getport.io/v1/authorize
Authorization Parameters: &prompt=consent
Token URL: https://mcp.us.getport.io/v1/token
Client ID: 7GC3bsR****
Client Secret:
Scopes: openid profile email offline_access
We also need to ability to share additional trusted redirect URI's: https://vertexaisearch.cloud.google.com/oauth-redirect

Sagi Keren

Mike Longlais: What you're looking for is already available - please check the following guide

https://docs.port.io/agent-management/port-mcp-server/token-based-authentication/

Sagi Keren

updated the status to

under review

Photo Viewer