Skip to content
Development
Agent

mcp

- `src/main/core/mcp/services/McpService.ts` - `src/main/core/mcp/utils/` — adapters, catalog, config IO, config paths, conversion - `src/main/core/mcp/controller.ts` - `src/core/primitives/mcp/api/` - `src/core/features/mcp/browser/` (`mcp-view.tsx`, `components/`)

From plugin
emdash
5.8k32 skills32 agents

How it fires

How this agent gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.

Context preview

The summary Claude sees to decide when to auto-load this agent.

- `src/main/core/mcp/services/McpService.ts` - `src/main/core/mcp/utils/` — adapters, catalog, config IO, config paths, conversion - `src/main/core/mcp/controller.ts` - `src/core/primitives/mcp/api/` - `src/core/features/mcp/browser/` (`mcp-view.tsx`, `components/`)

Agent definition

mcp.md

MCP

Main Files

  • `src/main/core/mcp/services/McpService.ts`
  • `src/main/core/mcp/utils/` — adapters, catalog, config IO, config paths, conversion
  • `src/main/core/mcp/controller.ts`
  • `src/core/primitives/mcp/api/`
  • `src/core/features/mcp/browser/` (`mcp-view.tsx`, `components/`)

Current Behavior

  • MCP server configs are read, adapted, merged, and written across supported agent ecosystems
  • provider-specific config formats are handled through adapters in `src/main/core/mcp/utils/`
  • the renderer MCP UI manages installed servers and catalog entries
  • Chat's MCP list reports configured servers, not inferred connection health. Codex's recognized

synthetic startup failures are translated by its ACP enrichment hook and displayed on the composer MCP trigger/popover instead of opening a transcript turn. Startup errors are scoped to the current Session activation and are not retained as configuration. Other provider diagnostics and ordinary failed MCP tool invocations remain unchanged; there is no health polling.

Rules

  • do not assume all providers support the same MCP transport types
  • keep canonical MCP data in shared types and adapt at the edges
  • if you add provider-specific MCP behavior, update both service and UI compatibility handling
Ships withemdash

Emdash is the Open-Source Agentic Development Environment (🧡 YC W26). Run multiple coding agents in parallel. Use any provider.

Get the whole plugin
Stats
5,748
Stars
589
Forks
Active
Maintenance
TypeScript
Language
Apache-2.0
License
1d ago
Last commit
1y ago
Created

Repo: generalaction/emdash

Other agents on emdash.