← All integrations

Deepline MCP server

115 operations0 webhooks

Find GTM tools, run and manage enrichment Plays and their triggers, deploy Monitors, manage provider credentials, secrets, notifications and billing through Deepline.

Try Deepline with your agent

Connect Deepline, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Deepline on my account, then run one read-only example and show me the result.

Runs once, when you ask

Deepline tools and triggers

Tools are what your agent can do in Deepline through Corsair's MCP server. Triggers are the Deepline events a routine can start from.

Monitors

  • AccessRead-only

    Check whether the workspace can use Deepline Monitors

    monitors.access

  • AvailableRead-only

    List deployable monitor tools, or describe the payload, outputs and pricing of one tool

    monitors.available

  • Batch.GetRead-only

    Read a monitor batch operation, such as the plan from a dry-run start or stop

    monitors.batch.get

  • CheckRead-only

    Validate a monitor definition and show its plan and pricing without deploying or spending credits

    monitors.check

  • DeleteDestructive

    Delete a deployed monitor and deprovision its upstream resource; dryRun shows the plan

    monitors.delete

  • DependentsRead-only

    List the published Plays that react to one monitor

    monitors.dependents

  • DeployDestructive

    Deploy a monitor from a definition; creates an upstream provider resource and may spend credits

    monitors.deploy

  • Fleets.ListRead-only

    List Monitor Fleets, or their overview with status counts

    monitors.fleets.list

  • GetRead-only

    Get one deployed monitor by its public key

    monitors.get

  • HealthRead-only

    Read monitor delivery and convergence health

    monitors.health

  • Jobs.CancelDestructive

    Cancel a running Monitor Job

    monitors.jobs.cancel

  • Jobs.GetRead-only

    Get the state, phase and counts of a Monitor Job

    monitors.jobs.get

Connect Deepline to Claude, ChatGPT or Cursor

  1. 1

    Connect Deepline in Corsair

    Add your Deepline API key once in Corsair. Corsair stores the credential encrypted and makes the Deepline API calls for your agent, so it never goes into a prompt or a config file. Connect Deepline

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Deepline. On a ChatGPT personal plan, connect Deepline here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Deepline's read and write operations run right away and its 32 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/deepline, add the Deepline plugin, and connect with an API key. Then call methods like corsair.deepline.api.auth.status() from your app. Corsair keeps each tenant isolated.

Yes. Deepline requires an API key from your Deepline account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Deepline, GitHub, Notion, Stripe, and the rest. Trigger Deepline from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for find GTM tools, run and manage enrichment Plays and their triggers, deploy Monitors, manage provider credentials, secrets, notifications and billing through Deepline. Common builds include sync jobs, admin tooling, and agents that call Deepline APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Deepline API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/deepline in the open repo. When Deepline ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Deepline data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Deepline data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Deepline on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 32 destructive Deepline operations. You can change a link's mode at hub.corsair.dev/me.