> ## Documentation Index
> Fetch the complete documentation index at: https://docs.earthcare.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Earth Care Network MCP

> Connect Claude, Cursor, or any MCP client to your ECN workspace to search the directory, read AI-ready context, find prospects with buying signals, and manage your CRM.

## What is ECN MCP?

The **Model Context Protocol (MCP)** is an open standard for connecting AI clients
to external tools and data. ECN runs an MCP server so tools like **Claude Code**
and **Cursor** can work directly inside your Earth Care Network workspace — using
your organization's context and credits.

## Why use it?

* **Talk to your workspace in natural language.** Search the directory, read a
  business Context Pack, qualify a lead, or draft outreach — without leaving your editor.
* **Run the prospecting engine from anywhere.** Discover aligned buyers, talent,
  and investors with live [buying signals](/guides/prospecting-engine).
* **Org-scoped and metered.** Every key is tied to one organization, and every AI
  action is [metered in credits](/guides/metering-credits) just like in the app.

## Getting started

<Steps>
  <Step title="Create an MCP key">
    Sign in as an org owner → **Settings → Connect external AI tools → Create key**.
    The `ecn_mcp_…` secret is shown once — copy it.
  </Step>

  <Step title="Connect your client">
    Follow the guide for your tool:

    <CardGroup cols={2}>
      <Card title="Claude Code" icon="terminal" href="/mcp/connect-claude-code" />

      <Card title="Cursor" icon="code" href="/mcp/connect-cursor" />
    </CardGroup>

    Using Claude.ai connectors or a ChatGPT app? See [Official connectors](/mcp/connectors).
  </Step>

  <Step title="Use a tool">
    Ask your assistant to search the directory or find prospects. Browse the full
    [tools reference](/mcp/tools) and [sample prompts](/mcp/sample-prompts).
  </Step>
</Steps>

## Endpoint

| Environment | URL                                         |
| ----------- | ------------------------------------------- |
| Production  | `https://api.earthcare.network/mcp/`        |
| Test        | `https://ecn-test-test.up.railway.app/mcp/` |
| Local       | `http://localhost:8000/mcp/`                |

<Note>
  The MCP server lives on the **API origin**, not the web origin — use
  `api.earthcare.network`, not `earthcare.network`. Friendly API hostnames are being
  finalized during the v2 rollout; on test, the backend origin is currently the
  Railway URL shown above.
</Note>

Health check (no auth): `GET /mcp/health/` returns the protocol version and the
list of available tool names.

## Generic / remote MCP setup

Any MCP client that supports a remote HTTP server can connect by pointing at the
endpoint above and sending the API key as a bearer token:

```
URL:    https://api.earthcare.network/mcp/
Header: Authorization: Bearer ecn_mcp_YOUR_KEY
```

The server speaks JSON-RPC 2.0 and implements `initialize`, `tools/list`, and
`tools/call`. `tools/list` is public; `tools/call` requires a valid key.

<Note>
  ECN's MCP surface is part of the active v2 refactor. The Claude Code and Cursor
  paths below are supported today; the OAuth-based one-click connectors are tracked
  on the [roadmap](/mcp/connectors).
</Note>