Skip to content

Grok MyLegend — public profiles, rich cards and personal agents Resource/MyLegend person card ui://mylegend/person-card-v20-neon-emblem.html

How to: Grok MyLegend — public profiles, rich cards and personal agents MyLegend person card ui://mylegend/person-card-v20-neon-emblem.html

client:Grok transport:streamable-http resource:MyLegend person card ui://mylegend/person-card-v20-neon-emblem.html

Add MyLegend — public profiles, rich cards and personal agents to Grok

  1. 01

    Open .mcp.json (in your project root) and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "mylegend": {
      "type": "http",
      "url": "https://mylegend.id/mcp"
    }
  }
}
  1. 02

    Save the file and restart Grok.

  2. 03

    MyLegend person card ui://mylegend/person-card-v20-neon-emblem.html is surfaced wherever your client lets you attach context. It is context to attach, not an action to run.

  3. 04

    If it does not appear, check that MyLegend — public profiles, rich cards and personal agents is connected and that you are looking at its resources rather than its tools.

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

Same resource, other clients

Read from the server itself, by connecting to it and calling resources/list on 9 October 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.