Ducky connection guide

Connect Ducky to Gemini

Set up a custom app in Gemini, or connect from Gemini CLI.

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=research

This guide uses the read-only research connection. Saving changes requires the full connection and a separate permission.

Gemini web app

Google currently requires a US personal account, age 18+, English, and Keep Activity enabled. Work and school accounts are excluded.

  1. Open gemini.google.com → Settings → Connected Apps (sometimes under Personal Intelligence).
  2. On Connected Apps, choose Create custom app. Paste the Ducky MCP URL and select Next. Review Google’s data-sharing notice before accepting.
  3. Complete Ducky sign-in and review the requested permissions.
  4. In chat, type @ and select the connected app. Initial setup is on the web; connected apps can also be used on mobile.

To revoke access: Connected Apps → the app → More details → Disconnect.

Google’s custom-app guide ↗

Gemini CLI

With Gemini CLI installed, run these commands in your terminal:

gemini mcp add --transport http ducky "https://api.duckybot.app/mcp?profile=research"
gemini mcp list
gemini

Inside the Gemini session, complete OAuth sign-in:

/mcp auth ducky

Then inspect the connected tools in the same session:

/mcp list
Gemini CLI MCP documentation ↗

Check the connection

  1. Ask the AI which Ducky account is connected and what it can access.
  2. Ask the question below. Check the returned records and source links.
  3. 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.
Connect your AI →Muse setup →

Guide reviewed October 24, 2026. App availability and account permissions can change.