# EDT-MCP as secondary MCP

[EDT-MCP](https://github.com/DitriXNew/EDT-MCP) complements **1C MCP Gateway** — it does not replace Gateway profiles, billing, or Agent Result Loop.

## Use EDT-MCP when

- You work inside **EDT** with a live project and need LSP-grade navigation tied to the IDE workspace.
- You run **YAXUnit** or EDT-specific validation from the agent.
- You need **full metadata business-model cascade** that is easier to drive from EDT export on disk.

## Use Gateway native tools when

- You need a **single hosted entry point** (https://mwi.yatsuk.pro) with policy and audit.
- You want **unified context** (`get_unified_context_for_task`), semantic FTS5 search, patch proposals, and Result Loop.
- You operate on **Git/Designer export** without EDT running.

## Typical split

```
Agent
  ├─ onec-gateway     discover_1c_context, get_unified_context_for_task, propose_* patches
  └─ edt-mcp (local)  run tests, EDT-only metadata ops, IDE-tied navigation
```

Install EDT-MCP locally and add to MCP config — see [TRI_STACK_MCP.md](./TRI_STACK_MCP.md).

## Mapping (conceptual)

| Gateway | EDT-MCP area |
|---------|----------------|
| `bsl_go_to_definition` | LSP definition in EDT workspace |
| `bsl_find_references` | LSP references |
| `preview_metadata_refactor_impact` | Metadata BM tools |
| `run_agent_result_loop` | YAXUnit / EDT validation steps (optional second server) |

Gateway heuristic index + SQLite FTS5 works **offline** on export; EDT-MCP works best with **EDT project open**.

## Related

- [BSL_LANGUAGE_SERVER.md](./BSL_LANGUAGE_SERVER.md) — BSL LS in Gateway diagnostics
- [METADATA_EXTENSION_EDIT.md](./METADATA_EXTENSION_EDIT.md) — native metadata/extension write tools