Skip to content

Conversation

gpeal
Copy link
Contributor

@gpeal gpeal commented Oct 3, 2025

Motivation and Context

Many MCP Servers use client_name for a variety of things including:

  • Whitelisting
  • Logos
  • Copy shown directly on the page
  • etc

As a result, it's important for MCP Clients to be able to override the client name.

How Has This Been Tested?

Successfully tested with the Codex CLI talking to the Figma MCP.

Breaking Changes

A new (optional) parameter to AuthorizationSession::new

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
    • New API parameter
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

This is currently preventing Codex from connecting to the Figma MCP (and likely others)

@github-actions github-actions bot added T-core Core library changes T-examples Example code changes T-transport Transport layer changes labels Oct 3, 2025
gpeal added a commit to openai/codex that referenced this pull request Oct 3, 2025
…vers (#4689)

The `experimental_use_rmcp_client` flag is still useful to:
1. Toggle between stdio clients
2. Enable oauth beacuse we want to land
modelcontextprotocol/rust-sdk#469,
#4677, and binary signing before we
enable it by default

However, for no-auth http servers, there is only one option so we don't
need the flag and it seems to be working pretty well.
@alexhancock alexhancock self-requested a review October 3, 2025 21:29
Many MCP Servers use client_name for a variety of things including:
* Whitelisting
* Logos
* Copy shown directly on the page
* etc

As a result, it's important for MCP Clients to be able to override the client name.
@gpeal gpeal force-pushed the gpeal/client_name branch from 1351011 to f0e8d61 Compare October 3, 2025 21:50
@alexhancock
Copy link
Contributor

I have a separate commit for the spellcheck fix on #470

Merging this in the interest of time despite the failing conventional commit check

@alexhancock alexhancock merged commit 6011f34 into modelcontextprotocol:main Oct 4, 2025
9 of 11 checks passed
@github-actions github-actions bot mentioned this pull request Sep 30, 2025
thomast8 pushed a commit to thomast8/codex that referenced this pull request Oct 5, 2025
…vers (openai#4689)

The `experimental_use_rmcp_client` flag is still useful to:
1. Toggle between stdio clients
2. Enable oauth beacuse we want to land
modelcontextprotocol/rust-sdk#469,
openai#4677, and binary signing before we
enable it by default

However, for no-auth http servers, there is only one option so we don't
need the flag and it seems to be working pretty well.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-core Core library changes T-examples Example code changes T-transport Transport layer changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants