Connect your agent

One URL. Every agent.

Question Relay is an MCP server. Add it once to whichever agent you use, sign in when prompted, and your agent can create questionnaires and pick up answers.

https://questionrelay.com/mcp

OAuth 2.1 · Streamable HTTP · leave Client ID and Secret empty.

ChatGPT has no install link — it takes about a minute by hand. Click a step to preview what you'll see.

https://questionrelay.com/mcp

Web app only, on Plus, Pro, Business, Enterprise, and Edu plans. On workspace plans an admin must allow developer mode first. ChatGPT shows a warning about custom connectors — that's expected.

chatgpt.com

Settings

General

Notifications

Personalization

Connectors

Data controls

Security and login

Account

Security and login

Multi-factor authentication

Log out of all devicesLog out all

Developer modeBuild and test unverified connectors, like Question Relay.

Preview of step 1 — turn on developer mode.

Add the server

claude mcp add --transport http question-relay https://questionrelay.com/mcp

Then run /mcp, pick question-relay, and choose Authenticate — your browser opens to sign in. (Or run claude mcp login question-relay.)

Or share it with your whole repo

Commit a .mcp.json at the repo root:

{ "mcpServers": { "question-relay": { "type": "http", "url": "https://questionrelay.com/mcp" } } }

claude mcp list shows ✔ Connected.

--transport http is required — without it Claude Code treats the entry as a local command. In .mcp.json, a url without "type": "http" is a config error.

Add to Cursor

Cursor installs the server immediately but signs in lazily — it shows “Needs login” under Settings → MCP until your first use opens the browser.

Or add it by hand

In ~/.cursor/mcp.json:

{ "mcpServers": { "question-relay": { "url": "https://questionrelay.com/mcp" } } }

Settings → MCP lists question-relay with its five tools.

If the button does nothing (some Linux setups), paste the JSON instead.

Add to VS Code

Using Insiders? Install in VS Code Insiders.

Or add it by hand

In .vscode/mcp.json (note the key is servers, not mcpServers):

{ "servers": { "question-relay": { "type": "http", "url": "https://questionrelay.com/mcp" } } }

From the command line:

code --add-mcp '{"name":"question-relay","type":"http","url":"https://questionrelay.com/mcp"}'

Command Palette → MCP: List Servers shows question-relay.

Needs a GitHub Copilot entitlement (the free tier counts). Some organizations block MCP servers by policy.

Google ships no install link — add the server to ~/.gemini/config/mcp_config.json (or .agents/mcp_config.json inside a workspace):

{ "mcpServers": { "question-relay": { "serverUrl": "https://questionrelay.com/mcp" } } }

Then open Agent Settings (⌘,) → Customizations → Authenticate, complete the sign-in in your browser, and paste the returned code back into the panel.

Antigravity uses serverUrl. url and httpUrl are rejected — a config copied from Gemini CLI docs will silently fail.

https://questionrelay.com/mcp

Any client that speaks MCP Streamable HTTP and OAuth 2.1 with dynamic client registration will work. Leave Client ID and Secret empty.

Universal installer

Detects your installed agents and writes the config for you:

npx add-mcp https://questionrelay.com/mcp

Generic JSON

{ "mcpServers": { "question-relay": { "type": "http", "url": "https://questionrelay.com/mcp" } } }

Key-name exceptions: Windsurf uses serverUrl, VS Code uses servers, Zed uses context_servers.

Codex CLI

codex mcp add question-relay --url https://questionrelay.com/mcp
codex mcp login question-relay

Not yet connectable: the consumer Gemini app supports only Google's partner connectors — there's no way to point it at an MCP URL. Gemini Enterprise accepts custom MCP servers but requires a manually issued OAuth client ID and secret, which Question Relay doesn't hand out yet — get in touch if you need one.

After you connect

Try one of these — each maps to one of the four tools:

“Ask the client five questions about the brief and send me the link.”create_questionnaire
“Have they answered yet?”get_results
“What questionnaires are still open?”list_questionnaires
“That link expired — send them a fresh one.”reissue_questionnaire

Quick check: ask your agent “what Question Relay tools do you have?” — you should see all four.

Sign-in and access

Sign in with your normal Question Relay account. There's no API key to create, copy, or store.
Your agent sees only your own questionnaires and results.
Disconnect any time from your client's connector settings.

If something doesn't work

Claude says it can’t connect.

Check the URL is exactly https://questionrelay.com/mcp — no trailing slash, no extra path.

Claude Code shows “Needs authentication”.

Run /mcp, select question-relay, choose Authenticate. Over SSH, use claude mcp login question-relay --no-browser.

Sign-in loops or fails in VS Code on the web or Codespaces.

Run “Authentication: Remove Dynamic Authentication Providers” from the Command Palette to clear the stale registration, then retry.

My org’s Claude doesn’t show “Add custom connector”.

On Team and Enterprise plans only an organization Owner can add connectors — ask them to add Question Relay once under Organization settings → Connectors.

Cursor’s install button does nothing.

Some Linux setups don’t handle the deeplink — paste the JSON from the Cursor tab into ~/.cursor/mcp.json instead.

Got a link from someone? Just open it — there's nothing to install and nothing to sign up for. If the link has expired, reply to whoever sent it and ask for a fresh one.

Agents: a plain-text version of this page lives at /connect.md.