diff options
| author | Igor Soarez <igor@soarez.org> | 2026-09-25 16:42:26 +0300 |
|---|---|---|
| committer | Igor Soarez <igor@soarez.org> | 2026-09-25 16:42:26 +0300 |
| commit | 66dcc84d51bed88cbfb608b9dc6800a8edd32b3c (patch) | |
| tree | f4a49b8182c7160ec8d850bd39e595fdcf59afd7 /mcp/LICENSE | |
| parent | fd06303bec47430f4644896d587f8f677245c9ac (diff) | |
ship the pi side we actually run, not a different arrangement
The README told pi users to install pi-chrome directly and run /chrome
authorize every session. That is not how this is used: pi reaches the same MCP
server through pi-mcp-adapter, with pi's own pi-chrome switched off, which is
why nobody types /chrome authorize.
pi/browser-gate.ts is that setup's missing piece, generalised from the one in
use: it answers pi-mcp-adapter's approval broker for one server, asking once per
session instead of once per call (the adapter's own grant only covers identical
arguments, so for a browser it asks nearly every time). /browser authorize,
/browser revoke, and PI_BROWSER_AUTHORIZE for headless runs. approveTools stays
on in mcp.json as the backstop if the gate does not load.
The README now leads with that: install the adapter, register the server in
mcp.json, copy the gate. Installing pi-chrome in pi is kept as the alternative,
with what it costs - two definitions of the browser, /chrome authorize per
session, and the trap of loading the extension twice.
Tested on an isolated pi config against a stand-in browser: with
PI_BROWSER_AUTHORIZE the call reaches the browser, without it the gate denies it.
Diffstat (limited to 'mcp/LICENSE')
| -rw-r--r-- | mcp/LICENSE | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/mcp/LICENSE b/mcp/LICENSE new file mode 100644 index 0000000..eea1273 --- /dev/null +++ b/mcp/LICENSE @@ -0,0 +1,28 @@ +MIT License + +Copyright (c) 2026 Igor Soarez + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. + +--- + +This server loads its browser tools from pi-chrome +(https://github.com/tianrendong/pi-chrome), MIT licensed, Copyright (c) +Earendil Inc. pi-chrome is a dependency, not a copy: no part of it is included +in this repository. |
