Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
AI-moderated qualitative customer interviews, study authoring, participant links, and CSV exports.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://api.heyjuno.co/v1/mcp/在终端中运行这条命令
claude mcp add --transport http juno https://api.heyjuno.co/v1/mcp/粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"juno": {
"url": "https://api.heyjuno.co/v1/mcp/"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"juno": {
"type": "http",
"url": "https://api.heyjuno.co/v1/mcp/"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://api.heyjuno.co/v1/mcp/菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 hey-juno 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于16天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Context7, Codebase Memory, Exa
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
| Interface | Use it for | Start here |
|---|---|---|
| Agent skill | Teach a skill-capable assistant how to use Juno for an authorised research task | Juno research skill |
| Python client | Call Juno from your application or agent | Client and the quickstart below |
| MCP | Connect a compatible client to Juno's hosted tools | MCP connection guide |
| Research workflow | Follow a study from a brief to participant evidence | Workflow and runnable example |
Python 3.11 or later; no third-party runtime dependencies. Clone this repository and run from its root:
git clone https://github.com/hey-juno/juno-agent-toolkit.git
cd juno-agent-toolkit python -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.
import os
from 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:
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.
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.
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.
These are published customer stories, not fixtures or benchmark results for this client.
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.