An AI coworker for any tool with an MCP server.

What Doozy can do in Any MCP server

The Model Context Protocol is how AI tools plug into software, and most vendors now ship a server. Doozy connects to any of them: a hosted one at an address, signing in with OAuth or a header, or a local one run from an npm or Python package. Its tools show up on the Integrations page, each with a switch, the same as a prebuilt connector.

• Connect a hosted MCP server by its address, with OAuth or a header for sign-in
• Run a local MCP server from an npm or Python package, with the variables it needs
• See every tool the server offers, and switch each on or off
• Keep any key the server needs in Secrets, out of the task's workspace

Things people ask

In a thread, after @Doozy. It answers in that thread, with what it did.

• You

  @Doozy using the Shopify server, which orders came in overnight?

• You

  @Doozy through the Airtable server, add this request to the Feedback base.

• You

  @Doozy ask the Datadog server whether the API's error rate changed in the last hour.

• You

  @Doozy with the Google Sheets server, append today's numbers to the tracker.

How to connect Any MCP server

A few minutes, by whoever owns the workspace. No engineer needed.

1. 1

   On the Integrations page, choose Add an MCP server.

2. 2

   Paste its address and sign in, or name its package and give it the variables it needs, from Secrets.

3. 3

   Doozy lists the server's tools. Switch off the ones you don't want, and ask.

What stays off, and what's always true

Doozy works like a teammate, so it doesn't stop to ask. You decide what it can reach.

More in Security and AI & Data Use.

Works well with

One ask often crosses tools: a Sentry error becomes a GitHub pull request and a Linear issue. Doozy uses whichever it needs.

• ZapierUse the actions you set up in Zapier across thousands of apps.
• SlackWhere Doozy works: mention it in a thread and the result comes back there.
• PostgresAsk questions of your own database, read-only, in plain words.

Questions people ask before they connect Any MCP server

Which servers work?

Any that follows the MCP standard over HTTP, or runs as an npm or Python package. The prebuilt connectors on this page are the same thing with the address and sign-in filled in.

Where do the server's keys live?

In Doozy's Secrets, encrypted, added to the connection outside the task's workspace. A secret's value is never shown again after it's saved.

Can Doozy see our Any MCP server credentials?

No. Every task runs in its own isolated workspace, and credentials stay outside it: they're added to each call on its way out. Nothing it reads or writes there can expose a key.

Will it change things in Any MCP server without asking?

It works like a teammate, so it doesn't stop to ask, and you decide what it can reach. Tools that delete or overwrite start switched off, you can switch off any other, and every action it takes is on the audit log with who asked.

Who can connect it?

Owners and admins of your Doozy workspace. Members see what's connected and can't change it. Everyone in your Slack can ask Doozy once it's connected.

What does it cost?

Nothing extra. Every integration is included on every plan, and the 14-day trial needs no card.

Something else? Write to [email protected].