Connect AI code editors to Ecobot

Cursor, Windsurf (now Devin Desktop), and Zed all support remote MCP servers over Streamable HTTP. The Ecobot endpoint is the same in every editor — public, read-only, no API key — and takes about a minute to add.

Ecobot MCP endpoint

https://ecobot.com/mcp

Requirements

  • Cursor, Windsurf (now Devin Desktop), or Zed on a recent stable release.
  • MCP is a core editor feature — no paid plan required to add a remote MCP server.

Setup steps

  1. 1

    Use the Ecobot remote MCP endpoint

    All three editors accept a remote Streamable HTTP MCP server. Point them at the Ecobot URL — do not wrap it in stdio/npx. It is a hosted server, not a local process.

    https://ecobot.com/mcp
  2. 2

    Cursor

    Open Settings → Features → MCP → Add new MCP server. Choose transport type SSE / HTTP and paste the URL above. See Cursor's MCP docs for the current UI: https://docs.cursor.com/context/model-context-protocol

  3. 3

    Windsurf (now Devin Desktop)

    In Windsurf / Devin Desktop, open Settings → MCP servers, add a new HTTP server, and paste the URL above. See the current Windsurf / Devin Desktop docs: https://docs.windsurf.com/

  4. 4

    Zed

    Zed configures MCP as a "context server". Open Command Palette → zed: open settings and add an entry under context_servers pointing at the URL above. See Zed's Assistant / context server docs: https://zed.dev/docs/assistant/introduction

    {
      "context_servers": {
        "ecobot": {
          "source": "custom",
          "url": "https://ecobot.com/mcp"
        }
      }
    }

Notes & caveats

  • Windsurf was rebranded to Devin Desktop, and its previous Cascade agent was end-of-lifed on July 1 2026 — ignore any older setup guides that reference a "Cascade MCP server".
  • Each editor may prompt for approval on the first tool call. Cursor and Windsurf/Devin Desktop can allow-list Ecobot so tool calls run without a confirm each time.
  • Some MCP features in Zed remain behind experimental flags — check release notes if a tool doesn't appear.

Ask IT to enable it

Copy this email and send it to whoever manages AI code editors at your organization. It has everything they need to add the connector in a few minutes.

Subject
Request: add Ecobot regulatory reference to AI code editors
Body
Hi IT,

Please add the Ecobot regulatory reference as an MCP (Model Context Protocol) connector to our AI code editors deployment. It gives our team citation-first answers from the 1987 Corps Manual, every USACE Regional Supplement, and the 2025 National OHWM Manual — verbatim quotes with page-anchored PDF links, no synthesis.

What I need:
  • Add a custom MCP connector in our AI code editors (Cursor · Windsurf (Devin Desktop) · Zed) tenant / workspace
  • Endpoint:        https://ecobot.com/mcp
  • Authentication:  None (public, read-only)
  • Scope:           Enable for my team (or org-wide if appropriate)

Why it matters:
  • Regulatory answers with verbatim quotes + page-anchored citations — audit-defensible
  • Reduces time spent digging through hundreds of pages of USACE guidance
  • Free to use — no license, no API key
  • Setup guide: https://ecobot.com/resources/ai/ai-code-editors

Please let me know once it's available, or if you need anything from me to move forward.

Thanks!

Example prompts by customer segment

Copy any of these into AI code editors once the connector is enabled.

Enterprise AEC firms

Learn more →

Multi-office consulting practices standardizing on Ecobot.

  • Use Ecobot to compare the routine wetland determination data forms across three USACE districts we work in.
  • Use Ecobot to pull the OHWM indicators cited in the Atlantic and Gulf Coastal Plain Regional Supplement.

Small firms

Learn more →

Solo delineators and small consulting practices.

  • Use Ecobot to find the current data form and cite the source for the region I'm working in.
  • Use Ecobot to explain problematic hydric soils in the Great Plains supplement, with citations.

Mitigation banks & PRM

Learn more →

Credit-bearing sites with long monitoring tails.

  • Use Ecobot to look up USACE-aligned success criteria language for a mitigation bank in the Eastern Mountains and Piedmont region.
  • Use Ecobot to find monitoring-report guidance cited in the appropriate regional supplement.

Federal government

Learn more →

Federal agencies with FedRAMP-aligned needs.

  • Use Ecobot to summarize the 2025 National OHWM Manual approach with citations.
  • Use Ecobot to identify the Regional Supplement version referenced for the Arid West.

State, tribal & local government

Learn more →

State DOTs, tribal nations, and local agencies.

  • Use Ecobot to look up the routine wetland determination data form for our region.
  • Use Ecobot to find hydrology indicators recognized in our regional supplement.

Academic programs teaching wetland delineation.

  • Use Ecobot to explain the difference between primary and secondary hydrology indicators in the Eastern Mountains and Piedmont supplement, citing pages.
  • Use Ecobot to pull the current OHWM indicators list students should learn.

Nonprofits

Learn more →

Land trusts, watershed groups, conservation orgs.

  • Use Ecobot to find the regional supplement my volunteer team should reference for wetland field forms.
  • Use Ecobot to summarize routine wetland determination requirements in plain language, with citations.

All customer segments

Learn more →

Every audience Ecobot serves.

  • Ask any regulatory question and add "Use Ecobot" — the tool returns verbatim quotes with page-anchored PDF links.

Not using Ecobot yet?

Sign up free or book a demo. Your field data plus AI assistants — one workflow.