feat(mcp): advertise CodeGraph server branding#879
Conversation
fedosov
force-pushed
the
mcp-server-branding-icon
branch
from
20a4463 to
88fb811
Compare
fedosov
force-pushed
the
mcp-server-branding-icon
branch
from
88fb811 to
b817e60
Compare
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b817e60756
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| export const SERVER_ICON = { | ||
| src: `data:image/svg+xml;base64,${SERVER_ICON_BASE64}`, | ||
| mimeType: 'image/svg+xml', | ||
| sizes: '32x32', |
There was a problem hiding this comment.
The MCP Icon schema defines sizes as string[] (see https://modelcontextprotocol.io/specification/2025-11-25/schema#icon), but this shared icon constant serializes it as a string. Because SERVER_ICON is emitted in both serverInfo.icons and every tool's icons/_meta.icons, clients that validate icon metadata can reject or drop the initialize/tools-list branding; use sizes: ['32x32'] or omit it for the SVG.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Alright! I will do this myself. Thanks anyway mister Codex 🫡
1 participant
feat(mcp): advertise CodeGraph server branding
Why
CodeGraph already has a clear identity on the website and in docs, but MCP clients can only show a plain
codegraphserver unless we advertise branding metadata.This makes CodeGraph easier to recognize in source/tool pickers instead of blending into generic server or tool entries (also feels good).
Screenshot
Summary
CodeGraphtitle and embedded SVG icon during MCPinitialize.tools/list, so tool-level UI entries can render the CodeGraph icon too.Risks and mitigations
data:image/svg+xml;base64,..., so hosts do not need to resolve a remote URL.Tests
npm run buildnpx vitest run __tests__/mcp-initialize.test.ts __tests__/mcp-unindexed.test.tsnpx vitest run __tests__/mcp-daemon.test.ts/Users/fedosov/Dev/psnpricesconfirmed Base64 icon metadata in bothserverInfoand all visible CodeGraph tools.