6DuckLearn MCP
com.6ducklearn由 6ducklearn.com 发布官方发布者v0.1.1更新于 Oct 24, 2026
Connect agents to 6DuckLearn memory, approvals, and runtime control.
概览
托管的 6DuckLearn MCP 服务器,让已连接的助手在账户授权下进行研究、整理、提醒、投资组合回顾、知识检索和画布创建。
- 可以做什么
- 在账户启用相应能力时,执行研究、整理、提醒、投资组合回顾、知识检索、画布创建和 Skill Builder 发现等账户授权工作流。生成只读的金融研究包,例如包含未来日期以及过期或缺失证据的 90 天缓存股票研究包。查询已发布的香港信用卡证据,并按给定的消费场景评估信用卡,数据不足时返回受限或证据不足状态而非排名。将受保护的写入提交到 6DuckLearn Inbox 等待人工审批,然后用服务器签发的审批 ID 恢复并执行一次该锁定请求。
- 适用场景
- 当你希望助手在 6DuckLearn 账户内工作——收集研究、整理材料、设置提醒、回顾投资组合、检索知识或在画布上起草——时使用。它也适合必须基于证据且只读的金融研究和香港信用卡比较。
- 运行要求
- 远程托管端点,必须通过 OAuth 登录,无需本地包。公开安装助手申请 mcp:read、mcp:write 和 approval:request 权限范围。Codex 可通过 npx 从 GitHub 运行安装;Claude Code 以 HTTP 传输方式添加并在工具选择器中授权。npm 包尚未发布。
安装
在 SourceWeft 中
- 打开 控制台中的 6DuckLearn MCP,将其添加到工作区。
- 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/com.6ducklearn%2Fmcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。
{
"mcpServers": {
"6ducklearn": {
"type": "http",
"url": "https://6ducklearn.com/mcp"
}
}
}README
6DuckLearn MCP
Official public setup docs, registry metadata, and local connector package for 6DuckLearn integrations.
This repository contains two separate integrations: Hosted MCP lets Codex use 6DuckLearn tools; the AI Runtime Connector lets Agent Console send work to Codex, Hermes, or OpenClaw.
Use 6ducklearn as the local client key in Codex or Claude Code. The official MCP Registry name is com.6ducklearn/mcp, and the hosted endpoint is:
This repository is intentionally hosted-first. It does not contain the private 6DuckLearn SaaS backend, Supabase edge functions, service-role database access, billing logic, user memory store, or production deployment scripts.
Quick Start
Codex
From GitHub:
This configures the hosted 6DuckLearn MCP server in local Codex, adds the hosted OAuth compatibility header, and starts the OAuth login flow.
If a matching, authenticated 6ducklearn hosted entry already exists, the setup command keeps it in place and does not reopen OAuth. A different local or stdio entry is replaced, while a matching but signed-out entry resumes OAuth, so repeated setup stays deterministic without creating duplicates.
Manual fallback:
Do not use codex mcp add for this fallback: current Codex versions can start OAuth immediately from that command, before explicit scopes are supplied. Inspect the entry first with codex mcp get 6ducklearn --json:
- If it is missing, add the full block below to
~/.codex/config.toml. - If it already uses the URL below, keep its server table and add only the missing
http_headerstable. - If it uses another URL or transport, run
codex mcp remove 6ducklearn, then add the full block.
Start only the explicitly scoped login:
Claude Code
Then open the MCP tool picker in Claude Code and authorize 6DuckLearn when prompted.
npm Package Status
The npm packages @6ducklearn/mcp and @6ducklearn/connector are not published yet. Until npm publication is available, use the GitHub npx command above for copy/paste setup.
Hosted MCP Identity
- local client key:
6ducklearn - MCP Registry name:
com.6ducklearn/mcp - title:
6DuckLearn MCP - MCP URL:
https://6ducklearn.com/mcp - OAuth discovery:
https://6ducklearn.com/.well-known/oauth-authorization-server - protected resource metadata:
https://6ducklearn.com/.well-known/oauth-protected-resource/mcp
The public Codex helper requests only mcp:read, mcp:write, and approval:request. Control-plane access and local-runtime authorization use separate, explicitly named flows; the hosted-MCP setup never requests approval:decide. A protected write is submitted to 6DuckLearn Inbox with a server-issued approval ID. The human decides there, then Codex calls resume_approved_write with only that ID to execute the locked request once.
What Agents Can Do
6DuckLearn MCP gives connected agents account-authorized workflows for research, organization, reminders, portfolio review, knowledge retrieval, canvas creation, and Skill Builder discovery. Finance research includes bounded stock-research bundles and issuer-grounded Hong Kong credit-card evaluation when those capabilities are enabled for the connected account.
For the full public catalog, see MCP tool use cases. The catalog describes each tool by practical use case and example prompt without exposing private schemas or backend implementation details.
Finance-related capabilities are for research, organization, summaries, alerts, and user-authorized workflows. 6DuckLearn MCP is not an order-routing service or source of investment recommendations.
Finance Research Examples
Ask for a stock bundle when you want the available value, timing, event, risk, saved-research, and portfolio inputs in one read-only response:
For Hong Kong credit cards, separate evidence lookup from evaluation:
query_credit_card_catalog never ranks cards. recommend_credit_cards evaluates only the currently published, source-linked catalog and may return a limited, stale, or insufficient-data status instead of a winner. Missing normalized fields remain disclosures; they are not permission to invent reward rates, eligibility, fees, or ranking evidence.
Advanced: AI Runtime Connector
The connector is for users who want a local runtime bridge between 6DuckLearn and AI runtimes such as Codex, OpenClaw, or Hermes. The preferred setup path is OAuth from the 6DuckLearn web app.
After login, keep the connector process running when using a local runtime:
Most users should start from the hosted 6DuckLearn setup page rather than cloning this repository directly.
MCP Registry Publication
The official registry manifest lives in server.json. It is a hosted-only listing because the canonical 6DuckLearn MCP server runs at https://6ducklearn.com/mcp; the local connector is a runtime bridge, not a standalone stdio MCP server package.
Before publishing, validate the manifest and hosted endpoint:
Publish with domain-based authentication so the registry name can stay under the 6DuckLearn domain namespace:
The required HTTP proof must be served from https://6ducklearn.com/.well-known/mcp-registry-auth. After the official MCP Registry lists com.6ducklearn/mcp, request GitHub MCP Registry inclusion by emailing [email protected] with the registry name, official registry URL, GitHub repository, website, hosted endpoint, and validation evidence. GitHub's MCP Registry is a separate curated surface, so listing there currently requires GitHub review rather than relying on automatic community registry sync.
What Is Public Here
- hosted MCP setup instructions
- official MCP Registry manifest
- sanitized client examples
- local connector source and tests
- live hosted endpoint smoke checks
- secret scans that prevent private SaaS details from entering this public repo
What Stays Private
- 6DuckLearn SaaS application source
- production Supabase functions and migrations
- service-role database patterns
- user memory, PKM, billing, approval trails, and runtime health data
- internal release scripts and production deploy credentials
Development
Validation runs TypeScript build, connector tests, package dry-run, MCP Registry manifest checks, hosted MCP smoke checks, and a public-release secret scan.
Security
Report security issues privately. See SECURITY.md.
License
Code is licensed under Apache-2.0. Documentation examples are licensed under CC BY 4.0. See TRADEMARK.md for 6DuckLearn brand usage.
来源:README.md,提交 b83b5fc
工具
0版本历史
1- v0.1.1最新Sep 16, 2026
评分
已满足适用检查项的 85%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
- 已声明认证方式必需10 分
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分