Integrations

Connect Daeda AI to the AI app you already use and it can answer questions about your live HubSpot data, then draft changes for you to approve.

You do this once. After that you ask in plain English - “which deals slipped their close date this month?” - and the answer comes back from your own portal.

What You Need First

Requirement	Where it comes from
Daeda AI installed on your HubSpot portal	The HubSpot Marketplace
At least one connected portal	Connect a new portal
A license key	In HubSpot, open Daeda AI, go to Master Settings, then MCP License Keys

Keep the license key to hand. Every app asks for it, either on a sign-in screen or in its settings.

How Connecting Works

Every app connects to Daeda AI at the same address:

https://mcp-ws.daeda.tech/mcp

Some apps, like Claude and ChatGPT, only need that address. They open a Daeda sign-in screen and ask for your license key there.

Others, like Cursor, VS Code, Codex, and Windsurf, keep their settings in a file on your computer. For those you paste in the address and your license key together.

Find your app below. Wherever an example shows <YOUR_DAEDA_AI_LICENSE_KEY>, replace the whole thing, angle brackets included.

Claude

Nothing to install and no files to edit.

Open Customize, then Connectors.
Select +, then Add custom connector.
Paste in the address: https://mcp-ws.daeda.tech/mcp
Click Add, then Connect.
Enter your license key on the Daeda screen that opens, and approve access.

To use it in a conversation, click +, then Connectors, and switch Daeda AI on.

On Team and Enterprise plans an owner adds the connector once, under Organization settings then Connectors. Everyone else then finds it under Customize then Connectors and clicks Connect. Free plans can have one custom connector.

Anthropic’s guide: About custom connectors.

Run this in your terminal, with your own license key in place of the placeholder:

claude mcp add --transport http daeda-ai https://mcp-ws.daeda.tech/mcp \
  --header "Authorization: Bearer <YOUR_DAEDA_AI_LICENSE_KEY>"

Restart Claude Code, then run /mcp to check that daeda-ai is connected.

Anthropic’s guide: Claude Code MCP.

Only needed for Claude apps that have no Connectors screen. If yours does, use the first tab instead.

Open ~/Library/Application Support/Claude/claude_desktop_config.json and add Daeda AI to it.

Show the settings to paste in

{
  "mcpServers": {
    "daeda-ai": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp-ws.daeda.tech/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <YOUR_DAEDA_AI_LICENSE_KEY>"
      }
    }
  }
}

If that file does not exist, or your Claude app will not accept these settings, use the Connectors screen instead.

ChatGPT only needs the address, but custom connections are switched off by default. Someone with admin rights on your workspace has to turn them on first, and whether you can use them at all depends on your ChatGPT plan.

Once they are on, add https://mcp-ws.daeda.tech/mcp as a custom connector and enter your license key on the Daeda screen that opens.

OpenAI’s guide: Developer mode and MCP apps in ChatGPT.

Codex keeps its settings in ~/.codex/config.toml, and the Codex app and the command line version both read that same file.

Show the settings to paste in

[mcp_servers."daeda-ai"]
url = "https://mcp-ws.daeda.tech/mcp"
http_headers = { Authorization = "Bearer <YOUR_DAEDA_AI_LICENSE_KEY>" }

Leave everything already in that file alone and add this to it. Save, restart Codex, then ask it to list your Daeda AI HubSpot tools.

If you would rather your license key was not written in the file, Codex can read it from an environment variable instead using bearer_token_env_var.

OpenAI’s guide: MCP in Codex.

Cursor

Cursor keeps its settings in mcp.json. Use ~/.cursor/mcp.json to make Daeda AI available everywhere, or .cursor/mcp.json inside a single project.

Show the settings to paste in

{
  "mcpServers": {
    "daeda-ai": {
      "url": "https://mcp-ws.daeda.tech/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_DAEDA_AI_LICENSE_KEY>"
      }
    }
  }
}

Reload Cursor, then check that daeda-ai is listed and switched on under Customize.

Cursor’s guide: Model Context Protocol.

VS Code

Run MCP: Add Server from the Command Palette and follow the prompts, which writes the settings for you. To do it by hand, create .vscode/mcp.json in your workspace.

Show the settings to paste in

{
  "servers": {
    "daeda-ai": {
      "type": "http",
      "url": "https://mcp-ws.daeda.tech/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_DAEDA_AI_LICENSE_KEY>"
      }
    }
  }
}

VS Code’s guide: MCP configuration.

Windsurf

Windsurf keeps its settings in mcp_config.json.

Show the settings to paste in

{
  "mcpServers": {
    "daeda-ai": {
      "serverUrl": "https://mcp-ws.daeda.tech/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_DAEDA_AI_LICENSE_KEY>"
      }
    }
  }
}

If you would rather not write your license key into the file, Windsurf can read it from an environment variable with ${env:DAEDA_LICENSE_KEY}.

Windsurf’s setup documentation now sits with Cognition’s Devin Desktop: MCP servers.

Any Other App

Daeda AI works with any AI app that can connect to an outside tool, so you are not limited to the ones above. Give the app the address https://mcp-ws.daeda.tech/mcp, and your license key when it asks for one.

If the app has a settings file rather than a sign-in screen, this is the shape most of them use.

Show the settings to paste in

{
  "mcpServers": {
    "daeda-ai": {
      "type": "http",
      "url": "https://mcp-ws.daeda.tech/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_DAEDA_AI_LICENSE_KEY>"
      }
    }
  }
}

Technical detail, if your IT team asks

Daeda AI is a standard remote MCP server over Streamable HTTP. It accepts either an Authorization: Bearer <license key> header, or the built-in authorization flow, which supports dynamic client registration and PKCE so apps that connect by URL can register themselves.

Apps that run inside a web browser need their web address approved by us before they can reach the server.

Check It Worked

Whichever app you connected, ask it:

Which HubSpot portals am I connected to, and which one is selected?

If it names your portals, you are connected. If more than one is listed, tell it which to use before you start asking questions.

Try These First

What data is synced for my selected portal, and what can you answer questions about?

Which deals slipped their close date this month? Show the owner, the amount, and the new close date.

Draft a write plan that adds a "Renewal Owner" property to companies, then show it to me before submitting anything.

Nothing changes in HubSpot on its own. Your AI drafts Write Plans and you approve them inside Daeda AI.

If Something Goes Wrong

What you see	What it usually means	What to do
The app connects but cannot see any HubSpot data	The connection was never approved	Connect again and enter your license key on the Daeda screen
It says your license key is invalid	The key was mistyped, or it has been deleted	Create a new one under Master Settings then MCP License Keys
It says no portals are connected	No portal has been connected yet	Connect a portal
Questions come back empty	The first sync is still running	Wait a few minutes and ask again
Whole areas of your data are missing from answers	Those permissions were not granted when the portal was connected	Reconnect the portal and include the data you need
The app cannot reach Daeda AI at all, before it ever asks for a key	It runs in a web browser we have not approved yet	Get in touch and we will add it