Browse the docs

MCP server

Quickstart

Connect Alertedly to your AI assistant in about a minute. Signing in is the recommended path for every person; API keys are for scripts and automations.

Before you start

  • An Alertedly account. Tracking data needs a Pro or VC plan; any account can use the free report tools. You can create a free account during sign-in.
  • The server URL:
MCP server URL
https://mcp.alertedly.com

https://mcp.alertedly.com/mcp also works, for existing setups. Transport is streamable HTTP.

Pick your client

Admin tabs are for people rolling Alertedly out to a whole Claude or ChatGPT organization.

For: Claude.ai and Claude Desktop, individual plansAuth: Sign in (OAuth)
  1. Open Settings → Connectors and choose Add custom connector.
  2. Name it Alertedly and enter the URL https://mcp.alertedly.com.
  3. Click Connect, sign in with your Alertedly account and approve.
  4. In a chat, enable Alertedly from the tools menu and ask: “What happened across my tracked companies this week?”

If you used the old mcp-remote bridge in your Claude Desktop config file, remove that entry; the connector replaces it.

For: Organization owners on Claude Team or EnterpriseAuth: Sign in (OAuth), per member
  1. An owner opens the organization's connector settings (Settings → Connectors, under organization connectors) and adds a custom connector named Alertedly with URL https://mcp.alertedly.com. This is done once for the whole organization.
  2. Each member then opens their own Settings → Connectors, finds Alertedly, clicks Connect and signs in with their own Alertedly account.
  3. Members of a firm on Alertedly automatically see the firm's portfolio and dealflow. Nothing is configured per person.

No shared credentials

Every member signs in as themselves, so roles, rate limits and the audit log follow the person. Menu names in Claude can change; look for the organization-level connector settings if the labels differ.
For: ChatGPT plans that allow custom connectorsAuth: Sign in (OAuth)
  1. Open Settings → Connectors (called Apps & Connectors in some versions).
  2. If your plan requires it, turn on Developer mode in the advanced connector settings.
  3. Create a connector with URL https://mcp.alertedly.com and OAuth authentication.
  4. Sign in with your Alertedly account and approve. Add Alertedly to a chat from the tools menu.
For: Workspace admins on ChatGPT Business or EnterpriseAuth: Sign in (OAuth), per member
  1. A workspace admin opens the workspace's connector settings and adds a custom connector with URL https://mcp.alertedly.com and OAuth authentication.
  2. The admin enables or publishes the connector for the workspace (or for specific groups, if your workspace uses them).
  3. Each member connects Alertedly and signs in with their own Alertedly account.
ChatGPT admin menus change between releases. If you can't find the option, look for connector or app management in the workspace settings, or ask your ChatGPT account team.
For: Claude Code CLIAuth: Sign in, or API key for headless use

With sign-in (no key):

terminal
claude mcp add --transport http alertedly https://mcp.alertedly.com

Start a session, run /mcp, choose Alertedly and sign in in the browser. /mcp then lists the 16 tools.

With an API key (CI, scripts, remote machines without a browser):

terminal
claude mcp add --transport http alertedly https://mcp.alertedly.com \
  --header "X-API-Key: YOUR_ALERTEDLY_API_KEY"
For: Cursor editorAuth: Sign in, or API key

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). With sign-in, give only the URL; Cursor asks you to sign in when it connects:

~/.cursor/mcp.json
{
  "mcpServers": {
    "alertedly": {
      "url": "https://mcp.alertedly.com"
    }
  }
}

With an API key:

~/.cursor/mcp.json
{
  "mcpServers": {
    "alertedly": {
      "url": "https://mcp.alertedly.com",
      "headers": { "X-API-Key": "YOUR_ALERTEDLY_API_KEY" }
    }
  }
}

Save, then open Cursor Settings → MCP. Alertedly should show 16 tools.

For: Codex CLI and IDE extensionAuth: Sign in, or API key

With sign-in, on recent versions:

terminal
codex mcp add alertedly --url https://mcp.alertedly.com
codex mcp login alertedly

With an API key, add to ~/.codex/config.toml (or .codex/config.toml in a trusted project) and export the key before launching Codex:

~/.codex/config.toml
[mcp_servers.alertedly]
url = "https://mcp.alertedly.com"
bearer_token_env_var = "ALERTEDLY_API_KEY"
terminal
export ALERTEDLY_API_KEY="YOUR_ALERTEDLY_API_KEY"

Alternative using the explicit header instead of a bearer token:

~/.codex/config.toml
[mcp_servers.alertedly]
url = "https://mcp.alertedly.com"
env_http_headers = { "X-API-Key" = "ALERTEDLY_API_KEY" }

Run /mcp inside Codex to verify. If the server isn't detected on an older build, update Codex or enable the streamable-HTTP client (experimental_use_rmcp_client = true).

For: Copilot Studio makers and Microsoft 365 adminsAuth: Sign in where supported; read-only org key for shared automations

A maker or admin in your tenant adds Alertedly as a custom MCP connector:

  • Transport: Streamable HTTP
  • Endpoint: https://mcp.alertedly.com
  • Authentication, recommended: OAuth, where your Copilot setup supports it, so each person signs in with their own Alertedly account.
  • Authentication, shared automations: API key in header X-API-Key. Use an organization key created by a firm admin in Team settings, with read-only scope.

Don't hand one key to everyone

A shared key acts as the firm, not as a person: it can't tell partners apart in the audit log and shares one rate limit. Use per-person sign-in for anything people use interactively, and keep org keys for agents and scheduled flows.
For: VS Code with GitHub Copilot agent modeAuth: Sign in, or API key

Add to .vscode/mcp.json in your workspace, or run MCP: Add Server from the Command Palette. With sign-in, VS Code asks you to sign in when the server starts:

.vscode/mcp.json
{
  "servers": {
    "alertedly": {
      "type": "http",
      "url": "https://mcp.alertedly.com"
    }
  }
}

With an API key, prompted once and stored by VS Code:

.vscode/mcp.json
{
  "inputs": [
    { "type": "promptString", "id": "alertedly-key", "description": "Alertedly API key", "password": true }
  ],
  "servers": {
    "alertedly": {
      "type": "http",
      "url": "https://mcp.alertedly.com",
      "headers": { "X-API-Key": "${input:alertedly-key}" }
    }
  }
}
For: Meta MuseAuth: Sign in (OAuth)

Add https://mcp.alertedly.com as a connector and sign in with your Alertedly account. Once Alertedly is listed in the Muse connector directory, you can also connect from its listing.

Try it

Once connected, ask something only Alertedly can answer:

  • “What happened across my tracked companies this week?”
  • “Give me a brief on my top competitor, with sources.”
  • “Which companies have stale or missing data?”

More in the VC and startup prompt galleries.

API keys

Key typeCreated byWhereSees
Personal keyYouDashboard → API & IntelligenceYour companies, or your firm's if you belong to one
Organization keyA firm adminTeam settingsThe firm's portfolio and dealflow

Send the key as X-API-Key: YOUR_KEY or Authorization: Bearer YOUR_KEY. Each key has a scope (read, or read + write) and an optional expiry. Use read-only keys for anything that only reads.

Keep keys out of shared configs

Don't commit keys to a repository or paste them into a shared connector for a whole team. Give people sign-in, and give automations their own read-only key.

Verify the connection

  • Your client should list 16 tools for Alertedly. In Claude Code and Codex, run /mcp; in Cursor, open Settings → MCP.
  • Ask “List my Alertedly companies.” The answer should name your account or firm.
  • Problems? See Troubleshooting.