Basic Usage
Signature
Configuration Options
Required Properties
| Property | Type | Description |
|---|---|---|
name | string | Unique application name |
Optional Properties
| Property | Type | Description |
|---|---|---|
id | string | Stable identifier for tracking |
description | string | Human-readable description |
Components
| Property | Type | Description |
|---|---|---|
tools | ToolType[] | Tools defined by this app |
resources | ResourceType[] | Resources defined by this app |
prompts | PromptType[] | Prompts defined by this app |
agents | AgentType[] | Agents defined by this app |
skills | SkillType[] | Skills defined by this app |
Extension Points
| Property | Type | Description |
|---|---|---|
providers | ProviderType[] | App-scoped dependency providers |
plugins | PluginType[] | App-specific plugins |
authProviders | AuthProviderType[] | Authentication providers |
adapters | AdapterType[] | Framework adapters |
Configuration
| Property | Type | Description |
|---|---|---|
config | Record<string, unknown> | App-specific configuration |
Multi-App Architecture
FrontMCP supports organizing functionality across multiple apps:App Isolation
Each app maintains its own:- Tool namespace (tools are prefixed with app name on conflict)
- Provider scope (providers are isolated per app)
- Auth context (apps can have different auth providers)
Provider Inheritance
Apps can access providers from the parent server:Standalone vs Gateway Apps
Standalone App
A standalone app runs independently:Gateway App
Apps withoutstandalone: true are combined in a gateway scope:
Related
@FrontMcp
Server configuration
@Tool
Define tools
@Plugin
Create plugins
Scope
Registry access