Ducky connection guide
Connect Ducky to Muse
Use Ducky research in Meta Muse Code, with a separate guide to Muse’s connector directory.
Ducky wrote this guide from the official documentation linked below. We have not completed sign-in and research tests in this app. Ducky has no confirmed public directory listing.
https://api.duckybot.app/mcp?profile=researchThis guide uses the read-only research connection. Saving changes requires the full connection and a separate permission.
Meta Muse web app
Muse documents approved connectors under Settings → Connectors. Ducky’s listing is not confirmed, and we have not verified a web entry for arbitrary MCP URLs.
For now, use Muse Code below. Publishing to the Muse directory requires a separate platform submission and review.
Muse connector guidelines ↗Muse Code
With Muse Code installed, configure the user settings file.
- Merge this entry into ~/.config/muse/settings.json (or $XDG_CONFIG_HOME/muse/settings.json). Preserve your existing settings and other servers.
{
"schema_version": 1,
"mcpServers": {
"ducky": {
"type": "streamable-http",
"url": "https://api.duckybot.app/mcp?profile=research"
}
}
}In your terminal, start OAuth sign-in:
muse mcp login duckyOpen a new Muse Code session after changing settings. In its chat, inspect the server:
/mcpMuse’s login command uses user settings; a project-only .mcp.json entry is insufficient. Do not add a static Authorization header to this OAuth configuration.
To clear this server’s saved OAuth credentials, run in your terminal:
muse mcp logout duckyCheck the connection
- Ask the AI which Ducky account is connected and what it can access.
- Ask the question below. Check the returned records and source links.
- Check the source dates and missing data. A completed sign-in does not prove that research queries work.
Use Ducky to find recent insider disclosures for NVDA. Include dates and source links. Explain any missing or delayed data. Do not create or change alerts.No records can mean a limited search window or coverage gap. It does not establish that no insider activity occurred.
If setup stops
- 401 / OAuth
- Sign in again through the client’s OAuth flow. Use the MCP URL above; do not paste a Ducky password or token into the chat.
- 403
- Check the signed-in Ducky account and the requested feature’s access. Repeated login does not change plan permissions.
- Tools are missing
- Refresh the client connection and check that Ducky is enabled. If it still fails, report the client version and error code to Ducky, without credentials.
Guide reviewed October 24, 2026. App availability and account permissions can change.