Skip to content

Commit 82ba00b

Browse files
Alan-TheGentlemanAlan-TheGentleman
authored
docs(pi): clarify MCP gateway status
Closes #396
1 parent ad737f4 commit 82ba00b

2 files changed

Lines changed: 11 additions & 10 deletions

File tree

‎docs/AGENT-SETUP.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,8 +49,8 @@ Restart Pi after installation.
4949

5050
The package has two paths:
5151

52-
- **HTTP event capture**: the Pi extension sends prompts, summaries, and passive task learnings to `engram serve`.
53-
- **MCP tools**: `pi-mcp-adapter` exposes `mem_*` tools by launching `engram mcp --tools=agent`.
52+
- **HTTP event capture**: the Pi extension sends prompts, summaries, passive task learnings, and compact Pi-native `mem_*` tool calls to `engram serve`.
53+
- **MCP gateway**: `pi-mcp-adapter` exposes Engram's MCP surface by launching `engram mcp --tools=agent` and is also used by other Pi MCP integrations such as Notion.
5454

5555
Use an existing Engram HTTP server:
5656

‎plugin/pi/README.md‎

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -220,14 +220,15 @@ MCP tool calls still use Engram core's canonical project resolver at call time.
220220

221221
## Troubleshooting
222222

223-
| Symptom | Fix |
224-
| ------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
225-
| `mem_*` tools are missing | Install `pi-mcp-adapter`, run `pi-engram init`, then restart Pi. |
226-
| Pi cannot find `engram` | Set `ENGRAM_BIN=/absolute/path/to/engram`. |
227-
| Session capture should use another server | Set `ENGRAM_URL=http://host:7437`. |
228-
| Existing MCP config was not replaced | Run `pi-engram init --force`. |
229-
| `mem_current_project` reports `/project/current` unsupported | Restart or upgrade the running `engram serve`; check `ENGRAM_URL`/`ENGRAM_BIN`. If `.engram/config.json` exists, Pi uses it as a temporary fallback. |
230-
| `mem_session_summary` cannot detect a project | Ask the user which project should receive the summary, then retry `mem_session_summary` with `project: "name"`. |
223+
| Symptom | Fix |
224+
| ------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
225+
| `mem_*` tools are missing | Install/verify `npm:gentle-engram@0.1.7`, run `pi-engram init`, then restart Pi. Keep `npm:pi-mcp-adapter` installed if you use MCP integrations such as Notion or direct MCP flows. |
226+
| Pi cannot find `engram` | Set `ENGRAM_BIN=/absolute/path/to/engram`. |
227+
| Session capture should use another server | Set `ENGRAM_URL=http://host:7437`. |
228+
| Pi shows `error MCP: 0/N servers` but `mem_*` works | That status is Pi's global MCP gateway, not proof that Engram's Pi-native HTTP tools failed. Check `~/.pi/agent/mcp.json` for stale/unreachable servers such as remote OAuth services, and keep `npm:pi-mcp-adapter` installed if you use MCP integrations like Notion. |
229+
| Existing MCP config was not replaced | Run `pi-engram init --force`. |
230+
| `mem_current_project` reports `/project/current` unsupported | Restart or upgrade the running `engram serve`; check `ENGRAM_URL`/`ENGRAM_BIN`. If `.engram/config.json` exists, Pi uses it as a temporary fallback. |
231+
| `mem_session_summary` cannot detect a project | Ask the user which project should receive the summary, then retry `mem_session_summary` with `project: "name"`. |
231232

232233
## Next steps
233234

0 commit comments

Comments
 (0)