1. Add MCP Servers to the Hub
MCP servers connect to the private hub through the UI or API. The hub enables shared access across workspaces and team members. Portkey supports remote MCP servers via StreamableHTTP and SSE transports. StreamableHTTP servers are recommended—SSE will be deprecated in the future.- Add the complete server URL (e.g.,
https://mcp.linear.app/mcp
) - Set the transport type. When uncertain, select
Streamable HTTP
- Choose the auth type expected by the MCP server:
- OAuth: Portkey automatically handles dynamic client registration with authorization code flows
- Client Credentials
- Custom Headers
- Set auth granularity: org-wide, workspace-level, or user-level
- Add the server
2. Provision Access to Workspaces
MCP servers become available for sharing with any workspace in the account. Workspace managers can also initiate server addition directly from within their workspace. Portkey generates a URL for each MCP server, accessible by workspace members:3. Use MCP Servers in Apps and Agents
Integrate these MCP server URLs in your applications and agent workflows. For example, add it to cursor atCursor Settings > MCP & Integrations > New MCP Server
The final configuration would look like this
Next
- View logs & traces for MCP interactions
- Supported capabilities
- Authentication deep dive
- Add guardrails