Zed, typed and ready to call.

Zed's agent panel speaks MCP, so the Deepline server drops in directly — call typed GTM tools from the editor, or shell out to the CLI in the terminal.

IDEZed IndustriesSupportedMCP · CLI
# Zedconnect
curl -s https://code.deepline.com/api/v2/cli/install | bash
01Connect over MCP

Connect Zed to Deepline. Same tools as every other surface.

zed
  1. // Step 1
    Install the Deepline CLI
    curl -s https://code.deepline.com/api/v2/cli/install | bash — one binary, no per-provider SDKs.
  2. // Step 2
    Add the Deepline MCP server
    Register the Deepline MCP endpoint with your agent, or call the CLI in the integrated terminal — both expose the identical typed tools.
02What you can do

Same typed tools as Claude Code and Codex

Per-call cost preview and spend caps on every run

No per-provider API keys to wire up

Save results to a Postgres database you own

The provider catalog is identical on every surface. Browse all providers →

03FAQ

Can I use Deepline with Zed? Yes.

Can I use Deepline with Zed?
Yes. Deepline ships as one CLI plus an MCP server, so Zed can call all 97+ GTM integrations as typed tools — over mcp · cli, with no per-provider setup.
How do I connect Deepline to Zed?
Install the Deepline CLI, then Add the Deepline MCP server. curl -s https://code.deepline.com/api/v2/cli/install | bash — one binary, no per-provider SDKs. Full steps are on this page.
Does Zed need a Deepline-specific plugin or integration?
No. Zed uses the same MCP · CLI surface as every other agent — there's no bespoke connector to build or maintain, and new providers appear automatically.
What can Zed do with Deepline?
Same typed tools as Claude Code and Codex; Per-call cost preview and spend caps on every run; No per-provider API keys to wire up — all priced per call with a spend cap you set, and results saved to a Postgres database you own.
// Try it

Your first GTM job,
shipping in two minutes.

Install once, then prompt Deepline from Claude Code.

// paste in your terminal
Book onboarding →Go to quickstartLive · cached responses across the network