MCP Server for AI Assistants

Connect SeekWhy to AI assistants like Claude, enabling natural language survey management. Create surveys, check responses, and analyze themes through conversational AI.

What is MCP?

The Model Context Protocol (MCP) is an open standard by Anthropic that allows AI assistants to securely interact with external tools and data sources. With SeekWhy's MCP server, you can manage surveys using natural language in Claude Desktop.

What You Can Do

Create Surveys

"Create a pulse survey about remote work satisfaction"

Check Responses

"How many people completed the Q1 survey?"

Extract Themes

"What are the main themes from the feedback?"

Manage Lifecycle

"Activate the survey and set deadline to Friday"

Setup Guide

Create an API Key

Go to your SeekWhy dashboard and create an API key with the scopes you need.

Navigate to Settings → API Keys
Click "Create API Key"
Give it a name (e.g., "Claude Desktop")
Select all scopes for full access
Copy the key - it's only shown once!

Note: API access requires a Team or Enterprise plan.

Open Claude Desktop Settings

In Claude Desktop, open the MCP configuration:

Open Claude Desktop
Click the hamburger menu (☰) in the top left
Go to Settings
Click Developer tab
Click Edit Config button

This opens the claude_desktop_config.json file.

Add SeekWhy MCP Server

Add the SeekWhy MCP configuration to the file:

claude_desktop_config.json

{
  "mcpServers": {
    "seekwhy": {
      "command": "npx",
      "args": ["-y", "@anthropic/mcp-remote", "https://seekwhy.ai/api/mcp"],
      "env": {
        "API_KEY": "sk_live_YOUR_API_KEY_HERE"
      }
    }
  }
}

Replace sk_live_YOUR_API_KEY_HERE with your actual API key.

Restart Claude Desktop

Save the config file and restart Claude Desktop for changes to take effect:

Quit Claude Desktop completely (Cmd+Q on Mac, or right-click tray icon on Windows)
Reopen Claude Desktop
You should see "seekwhy" in the MCP servers list when starting a new chat

Start Using It!

Open a new chat and try these example prompts:

"List all my surveys"

"Create a quick pulse survey with 3 questions about team morale"

"How many responses does my Q1 survey have?"

"What are the key themes from the employee feedback survey?"

Available MCP Tools

The SeekWhy MCP server provides 17 tools for comprehensive survey management:

Survey Management

Tool	Description
`survey_list`	List surveys with optional status filter
`survey_get`	Get survey details including questions
`survey_create`	Create a new survey (starts as draft)
`survey_update`	Update a draft survey
`survey_activate`	Activate survey for responses
`survey_close`	Close survey and finalize
`survey_status`	Get response statistics

Distribution

`survey_distribute`	Send survey to participants via email/Slack
`survey_send_reminders`	Send reminder to non-responders

Responses & Themes

`responses_list`	List survey responses
`themes_list`	Get extracted themes
`themes_extract`	Trigger AI theme extraction (async)

Reports & Utilities

`report_get`	Get generated report
`report_generate`	Generate AI report (async)
`audience_list`	List saved audiences
`audience_preview`	Preview filter matches
`job_status`	Check async job status

Example Conversation

You

I want to understand what engineers think about our GitHub to GitLab migration. Can you create a survey for this?

I'll create a survey to gather feedback on the GitHub to GitLab migration. Let me do that now...

[Uses survey_create tool]

Done! I've created "Engineering Feedback: GitHub to GitLab Migration" with 5 questions covering:

Overall satisfaction with the migration (NPS)
Biggest concerns about the transition
Training needs assessment
Timeline expectations
Open feedback

Would you like me to activate it and send it to the engineering team?

You

Yes, send it to Platform team first as a pilot. Give them a week.

[Uses survey_activate and survey_distribute tools]

Done! The survey has been distributed to 23 Platform team engineers via Slack and email. Due date is set to February 1st. I've scheduled automatic reminders at 3 days and 1 day before the deadline.

I'll check back when responses come in. Would you like me to notify you when we hit 50% response rate?

Troubleshooting

"Could not attach to MCP server"

Make sure you've saved the config file and restarted Claude Desktop
Verify your API key is correct and has the right permissions
Check that you have Node.js installed (required for npx)
Ensure you have internet connectivity

"API key not found" or "Unauthorized"

Double-check the API key in your config file
Make sure the key hasn't been revoked
Verify your organization is on a Team or Enterprise plan

"Insufficient permissions"

Check that your API key has the required scopes for the operation
You may need to create a new key with additional scopes

Claude doesn't know about SeekWhy tools

Start a new conversation after adding the MCP config
Check that "seekwhy" appears in the MCP servers indicator
Try asking "What SeekWhy tools are available?"

Security

Your API key is stored locally on your machine in the Claude Desktop config file. SeekWhy never sees or stores your full API key after creation - we only store a secure hash.

API keys are scoped to specific permissions
Optional IP allowlisting for extra security
All API calls are logged for audit purposes
Keys can be revoked instantly if compromised