---
outline: deep
---

# DF0051: Instance Has No MCP Endpoint

## Message

> The devframe instance on port `{port}` has no MCP endpoint.

## Cause

The `devframe connect` gateway tool `devframe_connect_call-tool` targeted a live devframe instance that runs without an MCP route — its `__connection.json` advertises no `mcp` entry, so there is no endpoint to proxy the tool call to. The error crosses the MCP boundary as structured JSON, so the calling agent can self-correct.

## Example

```ts
// The instance on 5173 was started without --mcp:
// devframe_connect_call-tool({ port: 5173, tool: 'devframe_state_read' }) → DF0051
```

## Fix

Restart the instance with the `--mcp` flag (or set `cli.mcp: true` on its definition) to expose its tools, then list instances again.

## Source

- [`packages/devframe/src/cli/connect.ts`](https://github.com/devframes/devframe/blob/main/packages/devframe/src/cli/connect.ts) — `call()` throws this when the targeted instance's record carries `mcp: null`.
