Claude MarketplacesSubmit
sunsiyuan avatar

Human Survey

sunsiyuan/human-survey

Lets Claude create and manage surveys through a JSON schema based API, then retrieve structured responses once humans have filled them out. Exposes five MCP tools: create_key for self-provisioning credentials, create_survey from schema definitions, get_results for aggregated data, list_surveys, and close_survey. Built for agents running long-horizon workflows that need to pause and collect feedback from groups over hours or days. Supports single choice, multi choice, text, scale, and matrix questions with conditional logic via showIf rules. Survey URLs are public for respondents while creation and results retrieval require API key authentication. Useful when your agent needs structured human input that doesn't fit into a single synchronous prompt.

GitHub stars
1
tool
1
auth
Secret needed
transport
STDIO
env var
1
last updated
Aug 1, 2026
View on GitHub

Tools

1 tools

Public tool metadata for what this MCP can expose to an agent.

survey

No parameter schema in public metadata yet.

Sponsors

Promote your product hereReach 125k+ visitors monthlyPromote your product hereReach 125k+ visitors monthlyAgent CaffeineSponsoredClose your lid, come back to finished workSnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthlyWaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthlyknobsSponsoredSee your site on any phone, any day, in any language

Configuration

HUMANSURVEY_API_KEY*secret

Your HumanSurvey API key (starts with hs_sk_). Get one at https://www.humansurvey.co

Readme

HumanSurvey

Discontinued (2026-11-12). The hosted service at humansurvey.co is shut down and its database deleted; API keys no longer work. The humansurvey-mcp npm package is deprecated. The code stays here, read-only, for reference.

human-survey MCP server

Attribution for the channels that have no referrer.

HumanSurvey asks one question — how did you hear about us — inside the host's own signup or payment flow, at a granularity that is actually actionable: the platform first, then which creator, podcast, event or store.

Agent configures a form   → platforms from the catalog, creators supplied by the caller
Host embeds /s/{id}       → in its signup flow, its payment flow, or both
Respondent answers        → picks a platform; that pick expands the follow-up in place
Host pushes conversions   → POST /api/attribution/events, keyed on its own user id
Agent reads back          → rollup, raw response stream, free text awaiting a mapping

What is this?

View the full README on GitHub

Details

Repository
github.com/sunsiyuan/human-survey
Package
humansurvey-mcp
Transport
STDIO
Auth
Required
Registry
MCP registry, active