From 037cbf9288795699606c952d04547c12e418d3bd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Padez?= Date: Sat, 29 Aug 2026 18:53:12 +0100 Subject: [PATCH] declare the MCP path, so the agent gets OpenSEO's own tools MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A path, resolved against this Officer, so the agent reaches /api/openseo/mcp through the same gate as everything else and never the instance directly. Not wrapped as Officer-native tools: the vocabulary moves upstream, a copy would go stale, and it fails silently — a tool exists that Officer cannot see. --- manifest.ts | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/manifest.ts b/manifest.ts index 5c20d97..67a08d3 100644 --- a/manifest.ts +++ b/manifest.ts @@ -51,6 +51,18 @@ export const manifest: PluginManifest = { icon: 'TrendingUp', color: '#22c55e', + /* + OpenSEO's own MCP server, handed to the agent as-is. + + A PATH, resolved against this Officer — so the agent reaches `/api/openseo/mcp`, through the same + gate as everything else, and never the instance directly. Which matters more here than elsewhere: + upstream self-hosts unauthenticated by design, so the proxy is the authentication. + + Not wrapped as Officer-native tools, deliberately. The vocabulary moves upstream; a copy would go + stale and fail silently, with a tool existing that Officer cannot see. + */ + mcp: { path: '/mcp' }, + permissions: [ { key: 'openseo',