MCP: Setup

https://greatquestion.co/api/mcp/v1

​

Claude Desktop

1. Open Settings → Connectors → Add custom connector.
2. Enter the name Great Question and the server URL above.
3. Click Save, then Connect. Authenticate via your browser.
4. Restart Claude Desktop. Great Question tools will appear when you start a new chat.

​

Claude Code

claude mcp add --transport http GreatQuestion https://greatquestion.co/api/mcp/v1

​

ChatGPT/Codex Desktop app

1. Go to Settings → Plugins → MCPs.
2. Click + Add server, then enter:
   • Name: Great Question
   • Type: Streamable HTTP
   • URL: https://greatquestion.co/api/mcp/v1
   • Leave other fields blank
3. Click Save, and then authenticate.

​

Cursor

1. Open Cursor Settings (Cmd/Ctrl + Shift + J), then select MCP from the sidebar.
2. Click + New MCP Server to open your mcp.json file.
3. Add the following:

{
  "mcpServers": {
    "great-question": {
      "url": "https://greatquestion.co/api/mcp/v1"
    }
  }
}

4. Save the file, then click Connect on the settings page. Authenticate via your browser.

​

Copilot

• Add the MCP server in Copilot Studio by using the MCP onboarding wizard (recommended)
• Create a custom connector to your server through Power Apps

1. Go to the Tools page for your agent.
2. Select Add a tool.
3. Select New tool.
4. Select Model Context Protocol. The MCP onboarding wizard appears.
5. Fill in the required fields Server name, Server description, and Server URL. Write a brief, but clear description of what your MCP server does. The agent orchestrator uses this information to identify whether to call your server at runtime.
   1. Server name: Great Question
   2. Server URL: https://greatquestion.co/api/mcp/v1
   3. Server description: Give the agent read and write access to Great Question’s research platform — studies, screeners, candidates, sessions, transcripts, highlights, and insights. Use it to create and configure interview, survey, and unmoderated studies, manage participants and recruitment, pull transcripts and screener responses, and search past research for findings and highlights. Feel free to adjust the server description as desired.
6. Select the authentication type for your MCP server. Great Question requires authentication, so don’t choose None. Use one of:
   1. OAuth 2.0 (recommended): Great Question supports dynamic client registration. Configure OAuth 2.0 authentication
   2. API key: send a Great Question API token in the Authorization header as Bearer <token>. See Connecting an agent for how to create one. Configure API key authentication
7. Create a new connection and add the MCP server to your agent.
   1. On Add tool, select Create a new connection for your MCP server or use an existing one.
   2. Select Add to agent to finish adding the MCP server to your agent.

​

Verifying your connection

1. See your studies. Ask for your recent studies. You should see titles, statuses, and IDs you recognize.
2. Find participants. Ask for the participants in one of those studies. Names and emails should appear as expected, unless your admin turned on PII hiding for the MCP, in which case they’re masked.
3. Pull a transcript. Ask for transcripts from that study, then request the full content of one. Look for speaker labels and timestamps.
4. Connect the dots. Pick a participant and ask what sessions they had and what their transcripts say.
5. Try a write action. Create a test candidate or draft study to confirm write access is working. You can delete it afterward. Write actions follow your role, so an observer’s test write may be refused.
6. Try a repo session. Ask for recent repo sessions, pick one, and request its transcript.

​

Connecting an agent (no human login required)

1. A workspace admin creates a token under Settings → API Tokens. This page is available to admins on plans that include API access.
2. Copy the token immediately. The page shows the full token only if loaded within 20 seconds of creation; later page loads show a masked version. If you miss that window, revoke the token and create a new one.
3. Configure the agent to send it with every request to the server URL above, in the Authorization header as Bearer <token>.

​

Troubleshooting

• Use a single connector and re-authenticate when switching. Disconnect the connector and authenticate it again to point it at a different workspace.
• Create a separate connector for each workspace. When you create a connector, you can give it a name to make the workspaces easy to tell apart, for example:
  • GQ-product-lab
  • GQ-dtx