Skip to content

feat: set MCP server display Title to "DoubleZero Data"#638

Open
david-mci wants to merge 1 commit into
mainfrom
feat/mcp-display-title
Open

feat: set MCP server display Title to "DoubleZero Data"#638
david-mci wants to merge 1 commit into
mainfrom
feat/mcp-display-title

Conversation

@david-mci

@david-mci david-mci commented Jun 4, 2026

Copy link
Copy Markdown

What

Adds a Title to the MCP server's Implementation so clients display "DoubleZero Data" instead of the programmatic name "doublezero".

server := mcp.NewServer(&mcp.Implementation{
    Name:    "doublezero",      // unchanged — programmatic identifier
    Title:   "DoubleZero Data", // new — human-readable display name
    Version: "1.0.0",
}, ...)

Why

Per the MCP spec / go-sdk docs, Title is "intended for UI and end-user contexts" while Name is "for programmatic or logical use." This disambiguates the connector from other connectors.

Name is deliberately left as doublezero — it's the stable identifier and isn't user-facing.

Caveat

This only affects clients that render serverInfo.title. Claude's connector UI is known to ignore some serverInfo fields (e.g. it ignores icons and uses the favicon instead), so the rename may not surface in Claude until/unless its UI reads title. Landing this makes the server spec-correct either way.

Test

Extends TestMCPHandler_Initialize to assert serverInfo["title"].

🤖 Generated with Claude Code

Adds a Title to the MCP server's Implementation so clients display
"DoubleZero Data" instead of the programmatic name "doublezero". Per the
MCP spec / go-sdk docs, Title is for UI/end-user display while Name is for
programmatic use. Name is left unchanged as the stable identifier.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.

1 participant