Which URL should I paste into Codex or Claude?

Use the complete private URL generated inside your ContextHint MCP account. Do not use the public /api/mcp endpoint by itself; the private connection credential is embedded in your generated URL.

Do I need a separate API key?

No. The private connection URL generated by ContextHint contains the credential required for this early-access flow. Treat the URL as a secret and do not publish it.

Why does the server connect but no tools appear?

Restart or refresh the client after saving, confirm the complete private URL was pasted, and verify the connector is enabled for the current conversation. If the issue remains, generate a new private URL from your MCP account and reconnect.

One-time connection

Connect ContextHint MCP to Codex or Claude

Q: Can I use the same Codex MCP configuration in the desktop app, CLI, and IDE?

OpenAI documents that the ChatGPT desktop app, Codex CLI, and IDE extension share MCP configuration on the same Codex host.

Create one private Streamable HTTP URL, add it to the AI client you already use, and verify the six ChatGPT Ads research and targeting tools.

Start here

Generate the URL before opening your AI client.

01
Create or sign in to your free ContextHint MCP account.
02
Generate the private MCP URL shown in the account.
03
Copy the complete URL. Treat it like a password.

Create account and get private URL

Codex

Add a Streamable HTTP server

01
Open Settings → MCP servers, then choose Add server.
02
Name the server ContextHint and choose Streamable HTTP.
03
Paste the complete private URL from your ContextHint account and save.
04
Restart the app. Use /mcp in the composer to confirm the server and tools are connected.

OpenAI says the desktop app, Codex CLI, and IDE extension share MCP configuration on the same host. Read the official Codex MCP guide ↗

Claude

Add a custom connector

01
Open Customize → Connectors, select +, then Add custom connector.
02
Enter ContextHint and paste the complete private URL.
03
Leave optional OAuth client fields blank for this private-URL connection and add the connector.
04
Enable ContextHint for the conversation from the connector/tool controls, then ask a campaign question.

Team and Enterprise organizations require an Owner to add the custom connector first. Read Anthropic's current connector guide ↗

Connection check

Verify the workflow with one real request.

“Use the product brief in this workspace to generate a context hint, show the matched prompts, and explain whether the selected niche fits the buyer.”

A healthy response should contain a primary hint, an alternate direction, a targeting breakdown, prompt evidence, and linked advertiser context when relevant.

See the complete worked transcript →

Setup troubleshooting