Data & contentPublic source

Survey MCP Server

A survey platform for ADK-Rust Enterprise agents — create, deliver, and measure surveys. 21 MCP tools spanning authoring (typed questions with validation), distribution (collectors + email invitations with quotas),…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Authoring — surveys with 7 question types: single_choice, multi_choice, text, rating (bounded scale), nps (0–10), number, boolean. Questions are validated at authoring time and only…

Distribution — collectors as named channels (open web link, tracked email, or API). Email collectors carry deduplicated invitations with delivery/response status; collectors support a…

Collection — responses are type-validated against their questions, required-question completeness is enforced on completion, and quota/closed-collector/closed-survey states are respected.…

Measurement — response funnel (invited → started → completed with completion & response rates), per-question aggregation by type, NPS (promoter/detractor breakdown), CSAT (top-box), and…

Architecture

How Survey MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Survey MCP Server

Validates the request and owns 21 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Survey MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Survey MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

21 named tools

create_survey

Create a new survey (draft)

internal write

get_survey

Get a survey by id

read only

list_surveys

List surveys by category/status

read only

add_question

Add a typed question to a draft survey

internal write

list_questions

List a survey's questions in order

read only

set_survey_status

Set survey status; opening for collection is gated

internal write

create_collector

Create a distribution channel (web_link/email/api)

internal write

list_collectors

List a survey's collectors

read only

set_collector_status

Open or close a collector

internal write

add_invitations

Add email invitations to an email collector

internal write

send_invitations

Send pending email invitations (external delivery)

external write

list_invitations

List a collector's invitations and statuses

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

13 read only7 internal write1 external write

Two writes are gated (requires_approval): opening a survey for collection (set_survey_status → open) and sending email invitations (send_invitations, classed external_write — it delivers to…
Opening is guarded — a survey can't be opened with zero questions.
All measurement and listing is read_only — analytics never mutate state.
Everything is audited — every state change appends to an audit trail (audit_log). Sample data is fictitious.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

Prompts

Completion

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-survey

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-survey",
    ["mcp-survey"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/architecture.svg Issues and support ↗github.com issues

Keep exploring