mcp-patchbay 0.0.0-stage → 0.1.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/CHANGELOG.md +103 -0
- package/LICENSE +201 -0
- package/NOTICE +8 -0
- package/README.md +376 -2
- package/SECURITY-MODEL.md +229 -0
- package/SECURITY.md +26 -0
- package/examples/servers.json +54 -0
- package/package.json +47 -4
- package/src/children.js +521 -0
- package/src/cli.js +155 -0
- package/src/config.js +465 -0
- package/src/doctor.js +124 -0
- package/src/fsutil.js +55 -0
- package/src/import.js +168 -0
- package/src/instructions.js +88 -0
- package/src/log.js +22 -0
- package/src/naming.js +96 -0
- package/src/permissions.js +72 -0
- package/src/process.js +367 -0
- package/src/redact.js +132 -0
- package/src/rename-permissions.js +158 -0
- package/src/server.js +864 -0
- package/src/version.js +4 -0
package/CHANGELOG.md
ADDED
|
@@ -0,0 +1,103 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
All notable changes to this project are documented here. The format follows
|
|
4
|
+
[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project uses
|
|
5
|
+
[Semantic Versioning](https://semver.org/).
|
|
6
|
+
|
|
7
|
+
## 0.1.0 - 2026-11-14
|
|
8
|
+
|
|
9
|
+
### Added
|
|
10
|
+
|
|
11
|
+
- An MCP server over stdio that hosts configured MCP servers as child processes, with the tools
|
|
12
|
+
`servers`, `enable`, `disable`, `restart` and `info`. Each carries
|
|
13
|
+
`_meta: {"anthropic/alwaysLoad": true}`.
|
|
14
|
+
- Policies `allow`, `confirm` and `deny`. `confirm` asks a person through a form-mode
|
|
15
|
+
elicitation, and fails closed when the client has no elicitation support.
|
|
16
|
+
- Live tool publishing with `notifications/tools/list_changed`. `enable` waits up to 2 s for the
|
|
17
|
+
client's re-list.
|
|
18
|
+
- Proxying:
|
|
19
|
+
- pass-through tool definitions and results, with `outputSchema` not enforced;
|
|
20
|
+
- cancellation and progress (original progress tokens);
|
|
21
|
+
- `roots/list` and elicitation forwarding, and roots `list_changed` fan-out;
|
|
22
|
+
- sampling refused;
|
|
23
|
+
- merging of children's own `list_changed`;
|
|
24
|
+
- a per-server `timeoutMs`.
|
|
25
|
+
- Children:
|
|
26
|
+
- full env inheritance with per-entry `env`;
|
|
27
|
+
- a process group per child on POSIX;
|
|
28
|
+
- tolerance of non-JSON stdout;
|
|
29
|
+
- redacted stderr ring buffers;
|
|
30
|
+
- crash isolation;
|
|
31
|
+
- pidfiles, and reaping of leftovers after a crash.
|
|
32
|
+
- Remote servers through mcp-remote 0.15.2:
|
|
33
|
+
- header values kept out of argv;
|
|
34
|
+
- `MCP_REMOTE_CONFIG_DIR` at 0700;
|
|
35
|
+
- sign-in detection with a URL-mode elicitation (or a form fallback);
|
|
36
|
+
- the state `waiting-for-sign-in`.
|
|
37
|
+
- Autostart per project (`CLAUDE_PROJECT_DIR`), and instructions folded into the patchbay's own,
|
|
38
|
+
capped at 4,096 characters.
|
|
39
|
+
- Redaction of tokens, URL query strings, and entries' own env, args and headers in everything
|
|
40
|
+
the patchbay emits.
|
|
41
|
+
- CLI: `import` (from a Claude Code config), `doctor`, and `rename-permissions`.
|
|
42
|
+
- The `examples/write-gate` PreToolUse hook example, with tests.
|
|
43
|
+
- `confirmVia`, a top-level config setting: `"elicitation"` (the default, unchanged behaviour) or
|
|
44
|
+
`"host"`. With `"host"`, `enable` and `restart` refuse to start a `confirm` server and point to
|
|
45
|
+
a new tool, `enable_confirm {name}`. The host's own permission prompt for that tool is the
|
|
46
|
+
person's approval. This makes `confirm` servers usable in clients that do not show form
|
|
47
|
+
elicitation to the person, such as the Claude Code VS Code extension, which answers it
|
|
48
|
+
`decline`. `enable_confirm` refuses `allow` and `deny` servers and is listed only in host mode.
|
|
49
|
+
- `import` writes `confirmVia: "host"`.
|
|
50
|
+
- `doctor` prints `confirmVia` and warns about Claude Code allow rules that would approve
|
|
51
|
+
`enable_confirm` without asking (the exact name, `mcp__patchbay__*`, `mcp__patchbay`, `*` and
|
|
52
|
+
other wildcards) and about `defaultMode: "bypassPermissions"`, in the user's settings and, with
|
|
53
|
+
`--project <dir>`, the project's. In host mode a warning exits 1. `--no-start` skips starting
|
|
54
|
+
servers.
|
|
55
|
+
- `rename-permissions` never writes a rule that matches `enable_confirm`.
|
|
56
|
+
|
|
57
|
+
### Fixed
|
|
58
|
+
|
|
59
|
+
- Shutdown no longer orphans children that ignore SIGTERM. A detached helper sends SIGKILL to the
|
|
60
|
+
remaining process groups after 500 ms, without delaying the patchbay's exit. Pidfiles are kept
|
|
61
|
+
until a child's exit is observed, and the startup reaper now escalates to SIGKILL. After a
|
|
62
|
+
crash, the leftover group members also get a SIGKILL follow-up.
|
|
63
|
+
- A remote server's `url` is now treated as a secret. The whole url, each path segment, each
|
|
64
|
+
query value and any userinfo (6+ characters) are redacted from `info`, `lastError` and logs.
|
|
65
|
+
mcp-remote logs the url to stderr, and many endpoints carry their key in the path. The url
|
|
66
|
+
is still on mcp-remote's argv (mcp-remote has no other way to take it), which is now
|
|
67
|
+
documented.
|
|
68
|
+
- Only mcp-remote children (`url` entries, an `mcp-remote` command, or `npx mcp-remote`) can
|
|
69
|
+
trigger the sign-in prompt, and only while they are starting. The prompt is always labelled
|
|
70
|
+
`[<server>] `. A re-auth request while a server is on is logged instead of prompting. The
|
|
71
|
+
sign-in URL is no longer written to the log, not even in redacted form.
|
|
72
|
+
- `rename-permissions` without `--config` now loads the default config (`$MCP_PATCHBAY_CONFIG`
|
|
73
|
+
or `~/.config/mcp-patchbay/servers.json`) and applies server prefixes. Before, deny rules for
|
|
74
|
+
prefixed servers silently stopped matching. Without a config file, it warns that names were
|
|
75
|
+
mapped as they are.
|
|
76
|
+
- A `restart` racing a `disable` no longer turns a `confirm` server back on: the disable cancels
|
|
77
|
+
the restart. An `enable` in that window joins the restart instead of showing a prompt whose
|
|
78
|
+
answer was ignored. A crash marks the server `failed` at once (it used to wait 20 ms), so a
|
|
79
|
+
restart right after a crash asks a person again.
|
|
80
|
+
- Autostart names that are inherited object keys (`constructor`, `toString`, `__proto__`) are
|
|
81
|
+
now rejected as unknown servers at load time (exit 78); before, they crashed `initialize`.
|
|
82
|
+
The same `hasOwn` check now covers `import --project` and `rename-permissions`' prefix lookup.
|
|
83
|
+
An env key named `__proto__` is now kept as a key instead of being dropped.
|
|
84
|
+
- A JSON syntax error in the config, in `import --from <claude.json>`, or in the
|
|
85
|
+
`rename-permissions` settings file is reported as the file path plus line and column. Node's
|
|
86
|
+
parser message quoted the surrounding text, which could include a token.
|
|
87
|
+
- Kills can no longer hit an unrelated process through a reused pid. Post-exit cleanup and the
|
|
88
|
+
startup reaper never fall back to signalling a bare pid. Pidfiles now record the process start
|
|
89
|
+
time (Linux, `v: 2`), and the reaper requires it to match and requires the pid to still lead
|
|
90
|
+
its own process group. A pidfile without a start time is not trusted on Linux.
|
|
91
|
+
- The config permission check is now complete (POSIX). The file is opened once, `fstat`ed and
|
|
92
|
+
read through that descriptor (no check-then-read race). A group- or world-writable (or
|
|
93
|
+
foreign-owned) parent directory is refused. A symlinked config is accepted only if its target
|
|
94
|
+
and the target's directory pass the same checks. A FIFO is refused without blocking.
|
|
95
|
+
|
|
96
|
+
### Documentation
|
|
97
|
+
|
|
98
|
+
- SECURITY-MODEL.md, SPEC.md and README now say exactly what happens to tool results: they are
|
|
99
|
+
parsed with `CallToolResultSchema`, which drops unknown keys inside content blocks and
|
|
100
|
+
rejects unknown content types. The docs no longer claim "unchanged".
|
|
101
|
+
- The redaction guarantee now states its 6-character minimum and covers the url. The sign-in
|
|
102
|
+
URL text matches the code.
|
|
103
|
+
- README: `npm test` takes about 20 s, not 40 s.
|
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/NOTICE
ADDED
|
@@ -0,0 +1,8 @@
|
|
|
1
|
+
mcp-patchbay
|
|
2
|
+
Copyright 2026 Distronode Corporation
|
|
3
|
+
|
|
4
|
+
This product includes software developed by Distronode Corporation, licensed
|
|
5
|
+
under the Apache License, Version 2.0. The full licence text is in LICENSE.
|
|
6
|
+
|
|
7
|
+
mcp-patchbay is original work, not a fork, and no third-party source code is
|
|
8
|
+
vendored into this repository.
|