@frontmcp/skills 1.9.0 → 1.9.1-rc.1

package/catalog/frontmcp-setup/examples/multi-app-composition/local-apps-with-shared-tools.md

@@ -5,10 +5,10 @@ level: basic
 description: 'Compose multiple local `@App` classes into a server with shared tools available to all apps.'
 tags: [setup, multi-app, local, multi, app, composition]
 features:
-  - 'Multiple `@App` classes with unique `id` fields for tool namespacing (`billing:charge`, `inventory:check_stock`)'
-  - 'Server-level `tools` array for shared tools available to all apps without namespace prefix'
+  - 'Multiple `@App` classes with unique `id` fields, which prefix their tools when two tools share a name (`billing:charge`)'
+  - 'Server-level `tools` array for shared tools every app serves under their own name (`server:<name>` when an app tool has the same name)'
   - 'Each app is self-contained with its own tools array'
-  - 'The `id` field on `@App` controls the namespace prefix for tool names'
+  - 'The `id` field on `@App` is the prefix of its tools when names collide'
 ---
 
 # Local Apps with Shared Tools
@@ -20,6 +20,7 @@ Compose multiple local `@App` classes into a server with shared tools available
 ```typescript
 // src/apps/billing.app.ts
 import { App } from '@frontmcp/sdk';
+
 import { ChargeTool } from '../tools/charge.tool';
 import { RefundTool } from '../tools/refund.tool';
 
@@ -34,6 +35,7 @@ export class BillingApp {}
 ```typescript
 // src/apps/inventory.app.ts
 import { App } from '@frontmcp/sdk';
+
 import { CheckStockTool } from '../tools/check-stock.tool';
 
 @App({
@@ -62,7 +64,9 @@ export default class HealthCheckTool extends ToolContext {
 ```typescript
 // src/main.ts
 import 'reflect-metadata';
+
 import { FrontMcp } from '@frontmcp/sdk';
+
 import { BillingApp } from './apps/billing.app';
 import { InventoryApp } from './apps/inventory.app';
 import HealthCheckTool from './tools/health-check.tool';
@@ -77,10 +81,10 @@ export default class Server {}
 
 ## What This Demonstrates
 
-- Multiple `@App` classes with unique `id` fields for tool namespacing (`billing:charge`, `inventory:check_stock`)
-- Server-level `tools` array for shared tools available to all apps without namespace prefix
+- Multiple `@App` classes with unique `id` fields, which prefix their tools when two tools share a name (`billing:charge`)
+- Server-level `tools` array for shared tools every app serves under their own name (`server:<name>` when an app tool has the same name)
 - Each app is self-contained with its own tools array
-- The `id` field on `@App` controls the namespace prefix for tool names
+- The `id` field on `@App` is the prefix of its tools when names collide
 
 ## Related
 

package/catalog/frontmcp-setup/references/multi-app-composition.md

@@ -193,16 +193,16 @@ The type is: `standalone?: 'includeInParent' | boolean` (defaults to `false`).
 
 ## Tool Namespacing
 
-When multiple apps are composed, tools are automatically namespaced by app id to prevent naming collisions. The format is `appId:toolName`.
+A local app's tool keeps its own name while no other tool in the server shares it. When two tools share a name, each is listed with its owner's id as a prefix: `appId:toolName`.
 
 ```typescript
-@App({ id: 'billing', name: 'Billing', tools: [ChargeTool] })
+@App({ id: 'billing', name: 'Billing', tools: [SearchTool] })
 class BillingApp {}
-// Tool is exposed as: billing:charge_card
+// Listed as: billing:search (another app also has `search`)
 
-@App({ id: 'inventory', name: 'Inventory', tools: [CheckStockTool] })
+@App({ id: 'inventory', name: 'Inventory', tools: [SearchTool, CheckStockTool] })
 class InventoryApp {}
-// Tool is exposed as: inventory:check_stock
+// Listed as: inventory:search and check_stock
 ```
 
 For remote and ESM apps, the `namespace` option controls the prefix:
@@ -217,7 +217,7 @@ app.esm('@acme/tools@^1.0.0', { namespace: 'acme' });
 
 ## Shared Tools
 
-Tools declared directly on `@FrontMcp` (not inside an `@App`) are shared across all apps. They are merged additively with app-specific tools and are available without a namespace prefix.
+Tools declared directly on `@FrontMcp` (not inside an `@App`) are served next to every app's tools, through the same flows: server-level plugin hooks, hooks on the tool class, `authorities`, rate limits, `availableWhen` and the startup checks apply to them as to app tools. They resolve server-level `providers`, not an app's.
 
 ```typescript
 @FrontMcp({
@@ -228,7 +228,13 @@ Tools declared directly on `@FrontMcp` (not inside an `@App`) are shared across
 export default class Server {}
 ```
 
-The same pattern works for shared resources and shared skills:
+- A shared tool keeps its own name. If an app in the same scope has a tool of that name, both are prefixed: `billing:health_check` for the app's and `server:health_check` for the shared one. No app may have the id `server` while `@FrontMcp` declares tools or resources (startup fails with `ReservedAppIdError`).
+- With `splitByApp: true`, and for a `standalone` app, each app's scope serves its own instance of every shared tool and resource.
+- An app's plugin hooks run for a shared tool only when declared with `appliesTo: 'uncovered-apps'`; server-level plugin hooks always run.
+- A shared tool belongs to no app, so `incrementalAuth` asks for no app grant before it runs.
+- `@FrontMcp` does not accept `prompts`; declare them on an `@App`.
+
+The same pattern works for shared resources (and resource templates) and shared skills:
 
 ```typescript
 @FrontMcp({
@@ -383,7 +389,7 @@ export default class Server {}
 ### Runtime
 
 - [ ] All app tools appear in `tools/list` with correct namespace prefixes
-- [ ] Shared tools appear without a namespace prefix
+- [ ] Shared tools appear under their own name, or as `server:<name>` when an app tool has the same name
 - [ ] `standalone: true` apps are isolated and do not appear in parent tool listing
 - [ ] `standalone: 'includeInParent'` apps have isolated scope but visible tools
 - [ ] Per-app auth modes are enforced independently per app

package/catalog/skills-manifest.json

@@ -2914,10 +2914,10 @@
               "level": "basic",
               "tags": ["setup", "multi-app", "local", "multi", "app", "composition"],
               "features": [
-                "Multiple `@App` classes with unique `id` fields for tool namespacing (`billing:charge`, `inventory:check_stock`)",
-                "Server-level `tools` array for shared tools available to all apps without namespace prefix",
+                "Multiple `@App` classes with unique `id` fields, which prefix their tools when two tools share a name (`billing:charge`)",
+                "Server-level `tools` array for shared tools every app serves under their own name (`server:<name>` when an app tool has the same name)",
                 "Each app is self-contained with its own tools array",
-                "The `id` field on `@App` controls the namespace prefix for tool names"
+                "The `id` field on `@App` is the prefix of its tools when names collide"
               ]
             },
             {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@frontmcp/skills",
-  "version": "1.9.0",
+  "version": "1.9.1-rc.1",
   "description": "Curated skills catalog for FrontMCP projects",
   "author": "AgentFront <info@agentfront.dev>",
   "homepage": "https://docs.agentfront.dev",