@paca-ai/paca-mcp 0.5.3 → 0.6.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/build/package.json +1 -1
- package/build/plugin-loader.js +1 -1
- package/build/types/index.d.ts +1 -1
- package/package.json +1 -1
package/build/package.json
CHANGED
package/build/plugin-loader.js
CHANGED
|
@@ -103,7 +103,7 @@ export async function loadPlugins(config) {
|
|
|
103
103
|
for (const plugin of mcpPlugins) {
|
|
104
104
|
// biome-ignore lint/style/noNonNullAssertion: filtered above
|
|
105
105
|
const url = plugin.manifest.mcp.remoteEntryUrl;
|
|
106
|
-
// Use gatewayURL when set — MCP bundles are served by the gateway (
|
|
106
|
+
// Use gatewayURL when set — MCP bundles are served by the gateway (Caddy),
|
|
107
107
|
// not the API service, so relative URLs must be resolved against the gateway.
|
|
108
108
|
const pluginBaseURL = config.gatewayURL ?? config.baseURL;
|
|
109
109
|
try {
|
package/build/types/index.d.ts
CHANGED
|
@@ -5,7 +5,7 @@ export interface PacaConfig {
|
|
|
5
5
|
* Base URL used to resolve plugin MCP entry URLs (e.g. relative paths like
|
|
6
6
|
* `/plugins-mcp/<id>/mcp.js`). Defaults to `baseURL` when not set.
|
|
7
7
|
*
|
|
8
|
-
* In Docker deployments the MCP bundles are served by the gateway (
|
|
8
|
+
* In Docker deployments the MCP bundles are served by the gateway (Caddy),
|
|
9
9
|
* not by the API service, so this should be set to the gateway's internal
|
|
10
10
|
* URL (e.g. `http://gateway`).
|
|
11
11
|
*/
|