Eden MCP

Using Custom AI as slash commands

Once Eden is connected through the MCP, your Custom AI can show up as /eden- slash commands in Claude, Cursor, and ChatGPT.

·4 min read

When you connect Eden through the MCP, the Custom AI in your default workspace come with you. Each one can appear as an /eden- command, carrying its current instructions and source-routing contract into the assistant you already use.

This article assumes Eden is already connected. If it isn't, start with connecting AI assistants.

Your Custom AI, everywhere

Eden registers each Custom AI as a command named after it. Newsletter Writer becomes /eden-newsletter-writer; Idea Partner becomes /eden-idea-partner. Picking one loads the latest saved definition and starts the conversation in that role.

How they look in each client

Claude web and Cursor

Type / in the composer. Eden commands are prefixed /eden- so they group together.

Claude Desktop

Claude Desktop may place MCP prompts in the attachment menu instead of the / picker:

  1. 01

    Click the + in the composer

    Open the attachment or connector menu beside the message box.

  2. 02

    Choose Add from Eden

    Eden may sit under a Tools or connector section.

  3. 03

    Pick a Custom AI

    Claude loads its instructions and starts the conversation.

ChatGPT

If your ChatGPT client doesn't expose MCP prompts in a picker, ask in plain language: “list my Custom AI” or “run my Newsletter Writer.” The assistant uses eden_list_custom_ai and eden_get_custom_ai to load it.

Giving it a first request

Each command accepts one optional input. Add your topic, draft, URL, or question when you select the command, or run it empty and choose from the Custom AI's starter prompts.

Changes refresh automatically

Create, rename, update, or archive a Custom AI in Eden and the connected command catalog refreshes within about a minute of activity. If it remains stale, follow getting the latest Eden MCP tools and commands.

How sources work outside Eden

  • Instructions travel. The outside assistant adopts the Custom AI's current instructions.
  • Workspace and creator sources stay permission-checked. The assistant opens only the relevant boards, documents, creators, or posts through Eden tools.
  • Managed knowledge can be protected. Publisher-protected runtime knowledge remains inside Eden; viewable documents can be searched or read through the Custom AI knowledge tools.
  • Actions use the outside client's tool set. The Custom AI's method travels, but it can call only tools available in that conversation.

Eden's Skills are exposed through dedicated MCP tools (list, get, import, export), not as slash commands. The retired legacy Prompts surface is not exposed at all.

Where to go next

Still stuck?

Email us. A real person reads every message.

Tell us what you tried and where you got stuck. We answer within one business day.

[email protected]