FrontMCP can dynamically load npm packages at runtime and register their tools, resources, and prompts alongside your local apps. Packages are fetched from a CDN, cached locally (memory + disk), and executed in-process — with optional background polling for automatic updates.Documentation Index
Fetch the complete documentation index at: https://docs.agentfront.dev/llms.txt
Use this file to discover all available pages before exploring further.
Three App Types
FrontMCP supports three ways to compose apps:| Type | Declaration | Execution | Use Case |
|---|---|---|---|
| Local | @App class | In-process | First-party code you own |
| ESM Package | App.esm() | In-process | Community or internal npm packages |
| Remote | App.remote() | HTTP proxy | External MCP servers |
Key Capabilities
- Dynamic Loading — Import npm packages at server startup via
App.esm()without bundling them into your build - Two-Tier Caching — In-memory + disk cache with configurable TTL for fast startup and offline resilience
- Version Polling — Background semver-aware polling with automatic hot-reload when new versions are published
- Private Registries — Token-based authentication for private npm registries and custom CDN endpoints
- Browser Support — Same
App.esm()API works in browser environments with in-memory-only caching
Minimal Example
Next Steps
ESM Packages Reference
Full API reference for App.esm(), caching, auth, and configuration
Publishing ESM Packages
Create and publish npm packages loadable by FrontMCP servers
CLI Reference
Manage ESM packages with
frontmcp package esm-updateESM Errors
Error classes for loading, caching, and authentication failures