Cue
Back to blog
mcp
chatgpt
agents

Connect Cue to ChatGPT and MCP Clients

Connect your private Cue library once, then use it from ChatGPT, MCP clients, and compatible agent CLIs.

•By Cue Team•
5 min read

Cue gives your agents a private, searchable prompt library. A connected client can locate the right instruction and retrieve its full text without copying prompts between browser extensions, local folders, and different machines.

Start in Cue

Sign in to Cue and open Integrations from the dashboard. That page shows the MCP endpoint for your Cue workspace and the connections you have already approved. Copy the endpoint from there instead of typing a URL by hand; it will match the Cue environment you are using.

Add the MCP connection

In your ChatGPT connection settings, MCP client, or compatible agent CLI, add the endpoint from Cue. The exact screen differs by client, but the flow is the same: add the remote server, sign in to Cue, and approve the requested read access.

Each connection is tied to your Cue account. A client can only see the Cues your account is allowed to read.

How agents use your library

Cue exposes two read-only tools:

  • search finds saved Cues from a natural-language query and returns matching titles and IDs.
  • fetch retrieves the complete instruction for a Cue after the agent has selected it.

The tools do not create, edit, or delete Cues. Keep authoring and curation in the Cue dashboard, where you can review the current text and its version history.

Use Cue in ChatGPT

When your ChatGPT plan or workspace supports custom connections, add Cue using the MCP endpoint shown in Integrations. After you sign in, ask normally: “Find my prompt for evaluating a product idea,” for example. ChatGPT can search your library, fetch the relevant Cue, and use it with the context of the current conversation.

You do not need to invoke a rigid prompt command. Cue supplies the reusable instruction; you supply the goal, constraints, and fresh context.

Use Cue with MCP clients and agent CLIs

The same endpoint works with MCP-compatible desktop clients and agent CLIs that support remote servers and OAuth. Add Cue once per client profile, authenticate, and then keep working in your usual interface. Your library remains maintained in one place.

If a client cannot complete sign-in, update the client, confirm that it supports remote MCP authentication, and try the connection again from the Integrations page. Never paste a password, reset link, or access token into a prompt or a support request.