DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to give a team chat access to its own tools via MCP with Whirl

Add MCP integrations, with OAuth, so Whirl can work with the tools your team already uses.

Credentials. OAuth connections give Whirl access to a team tool, so grant only the scopes the team needs and review who can add integrations.

Who it is forA team lead or developer who runs Whirl for a group and wants the assistant to reach internal tools.

The problemA general chat model cannot see a team's internal tools, so answers stay generic and people copy data in by hand.

The outcomeWhirl connected to one or more of your own MCP tools, with OAuth sign-in where the tool requires it.

What you need first

  • Bun installed
  • A free Convex account
  • A Clerk application
  • An OpenRouter API key
  • Git and a terminal

Steps

  1. Complete the self-host steps so the Whirl web app runs locally.
  2. Start the admin console in apps/console, since the README says it manages integrations, and follow its setup notes. (inferred, check the README)
  3. Add an MCP integration in the admin console and enter the tool details you want Whirl to use.
  4. Complete the OAuth sign-in for that integration if the tool asks for it.
  5. Open a new chat in Whirl and ask a question that needs that tool.

Prompt for your agent

In the whirlchat/whirl repo, read the apps/console directory and the docs/configuration.md file, then describe how to add an MCP integration with OAuth for <target-tool>. Output the exact steps and any environment variables needed. Verify each claim against the README or docs before reporting.

Caveat. The README names MCP and OAuth support but does not describe the admin console steps, so confirm the exact flow in the console before rolling it out.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page