Juno AI Customer Research

io.github.hey-junoPublished by GitHub account hey-junov1.0.0Updated Oct 26, 2026

AI-moderated qualitative customer interviews, study authoring, participant links, and CSV exports.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Hosted MCP server for Juno that lets an assistant draft AI-moderated customer interview studies, review interviews and export transcripts.

What you can do
  • Draft and brief qualitative research studies, then take them live
  • Inspect study and interview status and metadata
  • Export completed Live-mode interviews as CSV transcripts and answers
  • Explain findings using the brief, participant quotes and transcript context
When to use it
Use it when product analytics, support tickets or existing research leave a question that needs customers' own explanations, and you want an assistant to help brief a study, review interviews and pull the evidence.
Requirements
Remote streamable HTTP endpoint at api.heyjuno.co; OAuth is required, and self-service API keys (bearer) are also supported. A Juno account and workspace permissions are needed. No local runtime or environment variables are declared for the MCP connection.
Before you install
It works with real customer research data: transcripts and answers are exported under the organisation's permissions and redaction settings. Creating and going live with a study affects real participants, so review the brief before going live. Treat API keys as secrets and keep them out of prompts, source files and committed configuration. Test-mode simulations are not customer evidence.

Installation

In SourceWeft

  1. Open Juno AI Customer Research in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.hey-juno%2Fjuno/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "juno-ai-customer-research": {
      "type": "http",
      "url": "https://api.heyjuno.co/v1/mcp/"
    }
  }
}

README

Juno Agent Toolkit

An agent skill, a small Python client, and runnable workflows for Juno: AI-moderated customer interviews with real people.

Use Juno when product analytics, support tickets or existing research leave a question that needs customers' own explanations. Brief a study, review the interview, collect responses, and retrieve the evidence through the supported API.

Self-service API keys and OAuth 2.1. Production supports self-service Juno API keys (jsk_live_… / jsk_test_…) and OAuth 2.1 with dynamic client registration and PKCE S256. Native MCP clients (Claude Code, OpenAI Codex, ChatGPT) can connect directly over OAuth or with a bearer key; this Python toolkit uses JUNO_API_KEY and does not implement signup or credential issuance. Juno's remote MCP server is listed in the Official Model Context Protocol Registry as io.github.hey-juno/juno (server.json). See validation and limitations for what has been tested.

Choose your interface

InterfaceUse it forStart here
Agent skillTeach a skill-capable assistant how to use Juno for an authorised research taskJuno research skill
Python clientCall Juno from your application or agentClient and the quickstart below
MCPConnect a compatible client to Juno's hosted toolsMCP connection guide
Research workflowFollow a study from a brief to participant evidenceWorkflow and runnable example

Python quickstart

Python 3.11 or later; no third-party runtime dependencies. Clone this repository and run from its root:

sh
git clone https://github.com/hey-juno/juno-agent-toolkit.gitcd juno-agent-toolkitpython -m examples.research_workflow --help

Set JUNO_API_KEY in your environment using your normal secret-management method. Do not put it in a source file, prompt, committed client configuration or issue report.

python
import osfrom juno_client import JunoClient
client = JunoClient(api_key=os.environ["JUNO_API_KEY"])identity = client.me()print(identity["org_id"], identity["scopes"])

When the user has authorised creating a study:

sh
python -m examples.research_workflow draft \  --guidance "Understand why customers abandon onboarding and what they expected instead."

A new study starts in Test mode. Review its brief before choosing to go live. The example separates drafting, going live, inspecting interviews and exporting results; it does not recruit or contact participants automatically.

The client covers the core study/evidence workflow, not every public API operation. The live REST reference and OpenAPI document define the full interface. This preview is distributed from GitHub; it has not been published to PyPI.

What an agent can retrieve

Study and interview endpoints provide status and metadata. Interview metadata does not contain transcripts. For completed Live-mode interviews, use the export workflow to retrieve CSV transcripts and answers under the organisation's permissions and redaction settings. Test-mode simulations are rehearsal material and are not customer evidence.

Use the research brief, participant quotes and transcript context to explain findings. Keep uncertainty and conflicting accounts visible. Juno does not turn a small qualitative sample into population-wide prevalence or a measured causal effect.

Public MCP, hosted service

Juno publishes a remote MCP endpoint at https://api.heyjuno.co/v1/mcp/. Public connection information makes it discoverable; credentials and workspace permissions control use. See the connection guide for client configuration and verification status.

This repository contains client-side integration material. The hosted MCP server and Juno's research engine remain part of the Juno service. There is no second MCP server, local proxy or self-hosted Juno backend here.

Research in practice

These are published customer stories, not fixtures or benchmark results for this client.

Development

sh
python -m unittest discover -s tests -v

Tests use a local HTTP server and synthetic data. They need no Juno or model API key and do not create live research. Contract provenance explains the public schema snapshot. Please report reproducible client issues in GitHub, with credentials and research data removed; use Juno Support for account or private-data issues.

The toolkit is MIT licensed. Access to the hosted service follows Juno's current terms and entitlements.

Source: README.md at commit 556b0f5

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 20, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts