pi-mcp-client 0.8.0 → 0.9.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -23,7 +23,9 @@ This server doesn't require credentials. Ask Pi:
23
23
 
24
24
  You configure servers and sign in when needed. The model finds and uses
25
25
  relevant tools and resources—you don't need to select tools before asking a
26
- question.
26
+ question. When a server needs more information during a tool call, Pi asks you
27
+ directly and sends only what you submit. See
28
+ [server requests for input](docs/behavior.md#server-requests-for-input).
27
29
 
28
30
  Use these commands in Pi to manage your connections:
29
31
 
@@ -41,7 +43,9 @@ permissions. Tool activation isn't a per-call approval prompt. See
41
43
  ## ⚙️ Configuration
42
44
 
43
45
  Store server definitions in `~/.pi/agent/mcp.json` or a trusted project's
44
- `.mcp.json`. Project definitions replace same-named global definitions in full.
46
+ `.mcp.json`. Project servers load only after an explicit
47
+ [trust decision](docs/behavior.md#project-trust). Project definitions replace
48
+ same-named global definitions in full.
45
49
  You can edit these files or use `/mcp add` and `/mcp remove`. To reuse a
46
50
  Claude/Cursor JSON or Codex TOML file, run `/mcp import --scope global <path>` and
47
51
  review the selected connections before saving.