Connecting Tools

Cosmo connects to external tools through MCP (Model Context Protocol) servers. This allows the AI to read from and write to your tools — Slack, GitHub, Google Drive, and more.

How to Connect

1. Navigate to Settings → Integrations
2. Browse or search for the tool you want to connect
3. Follow the OAuth or API key setup flow
4. The integration is now available in your workspaces

Finishing an OAuth connection

OAuth integrations hand you off to the provider's own sign-in page in your browser. Once you approve access, Cosmo shows a confirmation card telling you whether the connection succeeded, then brings the desktop app back to the front by itself.

Some browsers ask permission before switching apps, or block it entirely. The card carries an Open Cosmo button for those cases, so you never have to hunt for the window yourself. If the connection failed, the same card says so and the button still takes you back, so you can retry from Settings → Integrations.

Asking for a list

When you ask for a list from a connected tool — "fetch all my Jira tickets", "show my ClickUp tasks", "list my latest emails" — Cosmo shows you every record it fetched, not a sample:

• Grouped the way you work. Records are laid out by project (or list, space, repository — whatever the tool calls it) when they span more than one, then by status, and every heading shows its count.
• Counted, not estimated. The totals and per-group counts are calculated from the data itself, so they always add up.
• Every page, within limits. When a tool returns results in pages, Cosmo fetches the rest itself before answering — up to 20 pages or 500 records. Past that, or for a very broad search (one matching thousands of items), Cosmo says that more exist rather than calling the list complete; narrow the request ("open bugs in project X") to see the rest. Asking for a specific number ("my 5 most recent PRs") fetches just that many.
• Yours when you say "my". "My tickets" is filtered to the account you connected; "the board" or "the project" means everyone's.

The list appears in the chat with a short summary alongside it. The full detail of any single record — its description, comments, IDs — is still available: just ask about it by name or key.

When Cosmo asks a question first

Cosmo looks things up rather than asking you for them. Ask for "my Jira board tasks" or "the sprint report" and it finds the board, project or list itself, and tells you which one it used. Once you've named a project or board in a chat ("I work on the Cosmo project in Jira"), follow-up requests reuse it, and Cosmo won't ask again.

It asks only when the answer genuinely depends on a choice it can't make for you:

• More than one tool could hold it. With both Jira and ClickUp connected, "give me the sprint report" doesn't say which one, so Cosmo asks which tool and board you mean.
• More than one sprint is open. If a board has several active sprints at once, Cosmo asks which sprint to report on instead of merging them into one report.
• Several boards fit equally well, and nothing earlier in the chat says which one.

Answer once, in the form Cosmo shows you, and it carries on from there.