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 分