Analysis connection

Ask your assistant about your Spryng study

Connect your assistant through a local Model Context Protocol (MCP) relay. Read permitted study patterns with Spryng’s privacy limits intact.

Included with annual Inquiry, Praxis, Spryng Field Study, and Research Organization plans.
Setup guideView on PyPISee pricing

v0.2.0 · Python 3.10+ · Read-only Analysis relay · Works with any MCP-compatible assistant

Version 0.2.0 can also read a study file you downloaded from Spryng and answer from that file on your computer. The local model guide explains that file mode.

What Analysis MCP supports

Read-only access within your existing permissions and privacy limits.

Study & question discovery

List the Spryng studies you can access and describe their questions, response counts, and active sensors.

Floored statistics

Request supported statistics and pattern summaries with small-group privacy floors to prevent identifying participants.

Cited story search

Search and open analysis-visible stories that cite back to Spryng, with story excerpts treated as untrusted data.

Segments & journeys

Compare segments and follow journey paths the study already defines, without exporting unredacted data.

Read-only safety

Stay read-only — the assistant cannot change instruments, modify responses, invite users, or alter billing.

Setup guide

Follow these steps when Analysis MCP is enabled for your organization.

1

Confirm your plan and enablement

Available for annual Inquiry, Praxis, Spryng Field Study, or Research Organization plans when Analysis MCP is enabled for your organization. In Spryng, open Analysis → Connect your assistant (or Organization settings → Analysis MCP). Create a personal token (prefix smcpa_) and copy the Analysis MCP URL. The token is shown once.

2

Install the relay

Install spryng-analysis-mcp with pipx or uv tool in an isolated environment (requires Python 3.10+). The relay runs locally on your machine.

3

Configure your assistant

Add the spryng-analysis server block to your assistant’s MCP settings with the absolute command path, your organization’s Analysis URL, and your token.

4

Try a question

Ask your assistant: “List the Spryng studies I can access. For one study, describe its questions and the statistics available.”

5

Revoke when done

You can revoke personal tokens at any time under Organization settings → Analysis MCP → Manage tokens. Also remove the token from your assistant config.

# Install with pipx (isolated — recommended)
      $ pipx install 'spryng-analysis-mcp==0.2.0'

      # …or with uv tool
    $ uv tool install 'spryng-analysis-mcp==0.2.0'

Pinning ==0.2.0 matches the verified release, including the downloaded study file. Check PyPI for newer updates.

⚡ Setup prompt

Let your assistant configure itself

Paste this instruction into your MCP-compatible assistant. Drop in your organization's Analysis URL and personal token first.

Setup prompt · paste into your assistant
Set up the Spryng Analysis MCP server ("spryng-analysis") in this assistant for me.

1) Install the relay:  pipx install 'spryng-analysis-mcp==0.2.0'  (or: uv tool install 'spryng-analysis-mcp==0.2.0')
2) Register an MCP server named "spryng-analysis" in this assistant's configuration with:
     command: "/absolute/path/to/spryng-analysis-mcp"
     args: ["--url", "https://app.spryng.io/api/organizations/YOUR_ORGANIZATION/mcp/analysis/rpc/"]
     env: SPRYNG_ANALYSIS_MCP_TOKEN=<paste-your-token-with-smcpa_-prefix>
   (Copy the exact Analysis MCP URL and personal token from Spryng under Analysis → Connect your assistant)
3) Restart the assistant, then verify by asking: "List the Spryng studies I can access."

Prefer manual configuration? The generic MCP server configuration JSON is below.

Generic MCP configuration

Add this server block to your assistant's MCP configuration file. Use the absolute path to the installed relay. 

{
  "mcpServers": {
    "spryng-analysis": {
      "command": "/absolute/path/to/spryng-analysis-mcp",
      "args": [
        "--url",
        "https://app.spryng.io/api/organizations/YOUR_ORGANIZATION/mcp/analysis/rpc/"
      ],
      "env": {
        "SPRYNG_ANALYSIS_MCP_TOKEN": "YOUR_PERSONAL_ANALYSIS_TOKEN"
      }
    }
  }
}
SettingDefaultDescription
SPRYNG_ANALYSIS_MCP_TOKENrequired—Your personal Analysis token (prefix smcpa_) generated in Spryng under Analysis → Connect your assistant. Shown once.
--urlrequired—Hosted Analysis MCP RPC URL for your organization (e.g. https://app.spryng.io/api/organizations/<org>/mcp/analysis/rpc/). Passed as an arg.

Using a local model instead of cloud AI?

Connect the relay to a tool-capable local model running in LM Studio or Jan on your own machine.

View local model guide →

Sample analysis questions

Once connected, ask questions in plain language — your assistant calls Spryng's read-only analysis tools directly.

“List the Spryng studies I can access.”
“For the active study, describe its questions and available statistics.”
“Show aggregate patterns for the intake collection, respecting privacy floors.”
“Search for stories mentioning team handoffs that cite back to Spryng.”
“Compare segments across cohorts for question 2.”
“What journey flows are defined for this study?”

Connect in Spryng

In Spryng, open Analysis → Connect your assistant (or Organization settings → Analysis MCP). Create a personal token (prefix smcpa_) and copy the Analysis MCP URL. It is shown once:

https://app.spryng.io/api/organizations/your-org/mcp/analysis/rpc/

Open SpryngReview annual plans

Read-only & privacy-first

  • Reaches only studies your Spryng user account is already authorized to analyze.
  • Cannot modify instruments, delete responses, invite members, or change billing.
  • Small-group privacy floors suppress cells under reporting thresholds.
  • Respondent story text is marked as untrusted data for external assistants.
  • Revoke personal tokens at any time under Organization settings → Analysis MCP.

Data handling & security FAQ

Common questions about privacy floors, model training, and assistant boundaries.

What can the assistant see?

Only what your Spryng user may already analyse for that organization, through the Analysis MCP tools. Requests still go to Spryng. Small groups under the privacy floor are suppressed (no counts or rows for that cell).

What can it change?

Nothing in the study. Analysis MCP is read-only. It cannot edit instruments, delete responses, invite users, or change billing.

Where does data go?

Hosted Spryng stores study data and enforces authorization and privacy limits. The local relay forwards calls to the configured Analysis URL and does not keep the token itself. A cloud assistant may send prompts and returned study data to its model provider — check your organization’s policy and that provider’s settings before connecting. A local model stays on the runtime you configure; installing the relay does not choose a model.

How do we turn it off?

Revoke the personal token in Organization settings → Analysis MCP. Remove it from the assistant. Organization administrators control whether Analysis MCP setup is available for the organization.

Is story text safe to send to an assistant?

Spryng marks respondent text as untrusted data for the assistant. Treat assistant output as a draft to check against the returned evidence. Do not treat a missing answer as a refusal.

Is this the same as ScrumDo MCP or Runner?

No. ScrumDo MCP connects assistants to the board. ScrumDo Runner / Spryng Runner runs local coding agents. Analysis MCP is only for reading Spryng study analysis.

Ask your assistant about study patterns

Install spryng-analysis-mcp, connect your organization's URL, and analyze with confidence.

Setup guideSee pricing

The connector is Apache License 2.0 (Copyright 2026 ScrumDo LLC). The license covers the connector; it does not grant access to hosted Spryng services or trademark rights beyond describing origin.