The official Model Context Protocol endpoint for
Dadan. It connects your workspace — recordings, transcripts,
summaries, engagement analytics, and captured leads — to any MCP-compatible assistant or agent.
Each user signs in with their own Dadan account and gets exactly their own access.
Gateway…MCP…OAuth…Streamable HTTP · OAuth 2.1
Setup
MCP endpoint ✔ verified live
Streamable HTTPOAuth 2.1 · PKCEAuto-discoveryNo API keys
Requires a paid Claude plan (Pro, Max, Team, or Enterprise). On Team/Enterprise, admins can also enable the connector organization-wide from admin settings.
Open Settings → Connectors (claude.ai or the desktop app) and select Add custom connector.
Name it Dadan, paste the endpoint URL above, and select Add. No client ID or secret is needed — the connector self-registers.
Select Connect. Your browser opens the Dadan sign-in page — authenticate with Google, Microsoft, or your email and password.
In a conversation, open the search & tools menu and make sure Dadan is enabled.
Verify: ask “Ping my Dadan server.” A pong reply confirms the full round trip.
From Claude Code (terminal) — adds it for the current project; append --scope user to make it available everywhere:
Check status or re-authenticate anytime with claude mcp list or the /mcp command inside a session. To revoke access, remove the connector in Settings → Connectors.
Requires a paid ChatGPT plan. Custom MCP connectors are gated behind Developer mode; on Business/Enterprise workspaces an admin may need to enable it.
Open Settings → Apps & Connectors and enable Developer mode (under Advanced settings).
Select Create, name the connector Dadan, and paste the endpoint URL above.
Choose OAuth as the authentication method. Leave client credentials empty — discovery and registration are automatic.
Acknowledge the trust prompt, then complete the Dadan sign-in when your browser opens it.
Verify: in a new chat, enable Dadan from the composer's tools menu and ask “What's my Dadan plan?”
Connector availability differs by surface: chat conversations support all tools; research features may only use read tools.
Works in Agent mode. Available on all Cursor plans that include MCP.
Use the one-click install: Add to Cursor — or open Cursor Settings → MCP → Add new MCP server.
For manual/team setup, commit this to .cursor/mcp.json in your repo (project-wide) or ~/.cursor/mcp.json (personal, all projects):
Cursor detects the OAuth requirement and shows a sign-in prompt next to the server — complete the Dadan login in your browser.
Verify: the server shows a green status in MCP settings with 13 tools listed; in Agent mode, ask it to search your Dadan library.
Requires VS Code 1.102 or later with GitHub Copilot; MCP tools run in Copilot's agent mode.
Command Palette → MCP: Add Server → HTTP, paste the endpoint URL, and choose where to save it (workspace or user profile) — or create .vscode/mcp.json yourself:
Start the server from the editor prompt and approve the trust dialog; VS Code opens the Dadan sign-in on first connection.
Verify: run MCP: List Servers — Dadan should show as running. Its tools appear in Copilot Chat's agent-mode tool picker.
To re-authenticate later, select the server in MCP: List Servers and choose the account/auth action.
Any MCP-compatible client or agent framework works — Windsurf, Gemini CLI, the official MCP SDKs (TypeScript, Python, C#, Java), or your own stack.
Configure a remote server with streamable HTTP transport. Most clients accept this shape:
Authorization is standard OAuth 2.1 with PKCE: metadata at /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource, dynamic client registration at /oauth/register. Spec-compliant clients need no manual auth configuration.
Verify from the command line: an unauthenticated request must return 401 with a WWW-Authenticate challenge:
Interactive testing:npx @modelcontextprotocol/inspector, then connect to the endpoint URL — the Inspector walks the OAuth flow and lets you call every tool by hand.
If the connection fails: the most common cause is a URL without the /mcp path — the bare domain serves this page, not the protocol. If sign-in previously worked and tools suddenly report an authorization error, disconnect and reconnect the connector; sessions are periodically reset.
Sign-in supports Google, Microsoft, and email — the same login as the Dadan apps. No API keys are issued or managed by you.
Tools: library search & metadata · transcripts, summaries, chapters · engagement analytics ·
captured leads & form responses · video upload & share links · plan usage. Reads and writes
are annotated, paginated, and scoped to the signed-in user.
Security & data
Nothing persists here. Authorization grants are held in memory only; your videos, transcripts, and leads stay in the Dadan platform and are relayed per request, never stored.
Credentials stay with the provider. Google and Microsoft sign-in happens on their pages; email passwords go directly to Dadan's authentication API over TLS and are never retained.
Per-user access only. Every call executes as the signed-in user against Dadan's own permission checks — there is no master credential.
Revoke anytime. Disconnect in your AI client or revoke the authorization in Dadan; gateway tokens expire within an hour regardless.