6ducklearn MCP Server

6DuckLearn MCP

Official public setup docs, registry metadata, and local connector package for the hosted 6DuckLearn MCP server.

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:

https://6ducklearn.com/mcp

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

codex mcp add 6ducklearn --url https://6ducklearn.com/mcp
codex mcp login 6ducklearn

Claude Code

claude mcp add --transport http 6ducklearn https://6ducklearn.com/mcp

Then open the MCP tool picker in Claude Code and authorize 6DuckLearn when prompted.

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 hosted server uses OAuth scopes such as mcp:read, mcp:write, runtime:connect, control:read, and approval-related scopes. Write-capable and sensitive actions remain controlled by 6DuckLearn policy and user approval.

Local Connector

The connector is for users who want a local runtime bridge between 6DuckLearn and local agents such as Codex, OpenClaw, or Hermes. The preferred setup path is OAuth from the 6DuckLearn web app.

npm install
npm run build
SIXDUCK_PUBLIC_BASE_URL=https://6ducklearn.com node packages/connector/dist/index.js login

After login, keep the connector process running when using a local runtime:

SIXDUCK_RUNTIME_TYPE=codex \
SIXDUCK_CODEX_CWD=/absolute/path/to/your/workspace \
SIXDUCK_CODEX_QUIET_PROFILE=true \
node packages/connector/dist/index.js

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:

npm run validate:registry
npm run smoke:hosted

Publish with domain-based authentication so the registry name can stay under the 6DuckLearn domain namespace:

# After generating the DNS proof key and adding the apex TXT record:
mcp-publisher login dns --domain 6ducklearn.com --private-key "$PRIVATE_KEY"
mcp-publisher publish
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.6ducklearn/mcp"

The required DNS TXT proof must be placed at the apex 6ducklearn.com, not under a selector subdomain. After the official MCP Registry lists com.6ducklearn/mcp, GitHub's MCP Registry should be able to discover it through the 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

npm install
npm run validate

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.