Skip to content

Cursor Chain Daddy Prompt/export-a-listing

How to: Cursor Chain Daddy export-a-listing

client:Cursor transport:streamable-http prompt:export-a-listing

Add Chain Daddy to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "mcp": {
      "url": "https://api.chaindaddy.io/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    export-a-listing is surfaced in the client's prompt or command menu. Unlike a tool, you invoke it deliberately — Cursor will not call it for you.

  3. 04

    If it does not appear, check that Chain Daddy is connected and that you are looking at its prompts rather than its tools.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Set these first

Chain Daddy will not start until these are set, so it never reaches Cursor.

  • CHAINDADDY_API_KEY
  • CHAINDADDY_IAP_KEY

Same prompt, other clients

Read from the server itself, by connecting to it and calling prompts/list on 14 November 2026. A listing does not declare its prompts, 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 prompt's arguments.