Skip to content

Update RFC 0004: address review feedback and add enhancements#18

Merged
mprahl merged 1 commit into
mlflow:mainfrom
jonburdo:mcp-registry-updates-1
May 26, 2026
Merged

Update RFC 0004: address review feedback and add enhancements#18
mprahl merged 1 commit into
mlflow:mainfrom
jonburdo:mcp-registry-updates-1

Conversation

@jonburdo

@jonburdo jonburdo commented May 13, 2026

Copy link
Copy Markdown
Contributor

Changes from reviewer feedback (TomeHirata, mprahl, thkim-us):

  • Add server_version and server_alias as direct params on search_mcp_access_bindings for common binding lookups
  • Add description fallback from server_json (API resolves like status)
  • Change icon to icons on MCPServer (list of sized variants matching upstream server.json icon schema)
  • Add environment variables display paragraph to UI section
  • Add transport_type filter for access binding search
  • Update server.json schema reference from 2025-09-29 to 2025-12-11

@jonburdo

Copy link
Copy Markdown
Contributor Author

This mainly contains minor adjustments to address feedback from:

This uses the latest version of the server.json schema and follows its use of icons: dict instead of icon: str.

This also simplifies fetching of access bindings for a given alias or server version:

Before (filter_string only):

bindings = mlflow.genai.search_mcp_access_bindings(
    server_name="io.github.anthropic/brave-search",
    filter_string="server_alias = 'production'"
)
GET /ajax-api/3.0/mlflow/mcp-servers/io.github.anthropic%2Fbrave-search/bindings?filter_string=server_alias%20%3D%20%27production%27

After (direct params):

bindings = mlflow.genai.search_mcp_access_bindings(
    server_name="io.github.anthropic/brave-search",
    server_alias="production",
)
GET /ajax-api/3.0/mlflow/mcp-servers/io.github.anthropic%2Fbrave-search/bindings?server_alias=production

| `display_name` | `String(256)` | mutable human-readable label |
| `status` | `String(20)` | default `'draft'` |
| `tools` | `JSON` | nullable; mutable tool metadata (names, descriptions, input schemas) |
| `transport_types` | `JSON` | nullable; read-only; extracted from server_json at creation (e.g., `["stdio", "streamable-http"]`) |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if this is included in server_json, why do we need this separate field?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point - I was thinking it would be a convenience, but maybe it is easy enough to go into the server_json.

I've removed this

Changes from reviewer feedback (TomeHirata, mprahl, thkim-us):

- Add server_version and server_alias as direct params on
  search_mcp_access_bindings for common binding lookups
- Add description fallback from server_json (API resolves like status)
- Change icon to icons on MCPServer (list of sized variants matching
  upstream server.json icon schema)
- Add environment variables display paragraph to UI section
- Add transport_type filter for access binding search
- Update server.json schema reference from 2025-09-29 to 2025-12-11

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Jon Burdo <jon@jonburdo.com>
@jonburdo jonburdo force-pushed the mcp-registry-updates-1 branch from dcc56dc to cda0388 Compare May 19, 2026 21:46
@jonburdo jonburdo requested a review from TomeHirata May 19, 2026 21:48
@mprahl

mprahl commented May 26, 2026

Copy link
Copy Markdown
Collaborator

Since the only comment from @TomeHirata was addressed, I'll go ahead and merge this. Feel free to post any additional feedback that comes up here or in Slack!

@mprahl mprahl merged commit 8cf58ba into mlflow:main May 26, 2026
@jonburdo jonburdo deleted the mcp-registry-updates-1 branch May 27, 2026 22:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants