OpenAPI to MCP Server
mcp-use/mcp-use
Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.
A skill your agent uses when building any FrontMCP server component other than a tool (for tools, use create-tool).
Install Frontmcp Development
$ npx skills add agentfront/frontmcp --skill frontmcp-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install agentfront/frontmcp frontmcp-development --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/agentfront/frontmcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/libs/skills/catalog/frontmcp-development .claude/skills/frontmcp-development && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "frontmcp-development" agent skill from https://github.com/agentfront/frontmcp/tree/main/libs/skills/catalog/frontmcp-development into .claude/skills/frontmcp-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontmcp-development", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/agentfront/frontmcp/tree/main/libs/skills/catalog/frontmcp-developmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add agentfront/frontmcp --skill frontmcp-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install agentfront/frontmcp frontmcp-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentfront/frontmcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/libs/skills/catalog/frontmcp-development .agents/skills/frontmcp-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "frontmcp-development" agent skill from https://github.com/agentfront/frontmcp/tree/main/libs/skills/catalog/frontmcp-development into .agents/skills/frontmcp-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontmcp-development", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add agentfront/frontmcp --skill frontmcp-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install agentfront/frontmcp frontmcp-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentfront/frontmcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/libs/skills/catalog/frontmcp-development .cursor/skills/frontmcp-development && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "frontmcp-development" agent skill from https://github.com/agentfront/frontmcp/tree/main/libs/skills/catalog/frontmcp-development into .cursor/skills/frontmcp-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontmcp-development", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/agentfront/frontmcp.git --path libs/skills/catalog/frontmcp-development--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add agentfront/frontmcp --skill frontmcp-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install agentfront/frontmcp frontmcp-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentfront/frontmcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/libs/skills/catalog/frontmcp-development .gemini/skills/frontmcp-development && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "frontmcp-development" agent skill from https://github.com/agentfront/frontmcp/tree/main/libs/skills/catalog/frontmcp-development into .gemini/skills/frontmcp-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontmcp-development", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install agentfront/frontmcp frontmcp-developmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add agentfront/frontmcp --skill frontmcp-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/agentfront/frontmcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/libs/skills/catalog/frontmcp-development .github/skills/frontmcp-development && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "frontmcp-development" agent skill from https://github.com/agentfront/frontmcp/tree/main/libs/skills/catalog/frontmcp-development into .github/skills/frontmcp-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontmcp-development", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add agentfront/frontmcp --skill frontmcp-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install agentfront/frontmcp frontmcp-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentfront/frontmcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/libs/skills/catalog/frontmcp-development .opencode/skills/frontmcp-development && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "frontmcp-development" agent skill from https://github.com/agentfront/frontmcp/tree/main/libs/skills/catalog/frontmcp-development into .opencode/skills/frontmcp-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontmcp-development", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
frontmcp-development- GitHub stars
- 146
- Token cost
- ~11k tokens
- SKILL.md length
- 2,185 words
- Files
- 72 (incl. references)
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when building any FrontMCP server component other than a tool (for tools, use create-tool).
- Works in 4 steps: Identify the component type using the… → Open the matching reference (e.g.… → Compose, if needed: most non-trivial… → …
- Building any FrontMCP server component other than a tool (for tools
- SKILL.md covers When to Use This Skill, Prerequisites, Steps and Scenario Routing Table, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Frontmcp Development is an agent skill from agentfront/frontmcp. Use when building any FrontMCP server component other than a tool (for tools, use create-tool). Covers @Resource static resources and parameterized URI templates; @Prompt reusable prompts (RAG, multi-turn); @Provider singleton dependency-injection providers (database pools, API clients); @Agent autonomous LLM agents (Anthropic, OpenAI) and swarms; @Job background jobs (retry, progress, permissions) and @Workflow DAG pipelines; framework adapters and the OpenAPI adapter (turn OpenAPI 3.x specs into MCP tools with…
Its SKILL.md is about 11k tokens, which your agent loads only when the skill is triggered. The skill folder holds 77 other files, including reference files (for example `examples/create-adapter/basic-api-adapter.md`, `examples/create-adapter/namespaced-adapter.md` and `examples/create-agent-llm-config/anthropic-config.md`).
It sits in Backend & APIs, covering OpenAPI specifications, MCP servers and Design patterns. It works with OpenAPI, OpenAI, Model Context Protocol and TypeScript. The repository describes itself as: TypeScript-first framework for the Model Context Protocol (MCP). You write clean, typed code; FrontMCP handles the protocol, transport, DI, session/auth, and execution flow. The licence is Apache-2.0.
When your agent uses it
- Building any FrontMCP server component other than a tool (for tools
- Use create-tool)
Example prompts
- “/frontmcp-development”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Identify the component type using the Scenario Routing Table below.
- Open the matching reference (e.g. references/create-tool.md, references/create-resource.md) and follow its Steps section.
- Compose, if needed: most non-trivial features need two or more components (e.g. tool + provider, resource + adapter). Read each reference…
- Test before integration (frontmcp-testing) — every component type has a unit-test recipe.
What it can do on your machine
Read from SKILL.md and the folder at commit 8f59ba8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.agentfront.dev
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Frontmcp Development loads about 11k tokens when it runs, and up to ~126k if it reads all its reference files. Until then it costs about 229 tokens; SKILL.md has 2,185 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from agentfront/frontmcp at commit 8f59ba8, republished under its Apache-2.0 licence (© agentfront). 2,185 words, ~10,509 tokens.
Download SKILL.mdSave it as
.claude/skills/frontmcp-development/SKILL.md (or your agent's skills folder). This skill also uses 71 other files; get the full folder from GitHub.- name
- frontmcp-development
- description
- Use when building any FrontMCP server component other than a tool (for tools, use create-tool). Covers @Resource static resources and parameterized URI templates; @Prompt reusable prompts (RAG, multi-turn); @Provider singleton dependency-injection providers (database pools, API clients); @Agent autonomous LLM agents (Anthropic, OpenAI) and swarms; @Job background jobs (retry, progress, permissions) and @Workflow DAG pipelines; framework adapters and the OpenAPI adapter (turn OpenAPI 3.x specs into MCP tools with auth, polling, transforms); plugins, plugin lifecycle hooks (before / after / around / stage), and the official plugins; instruction-only skills and skills that reference tools; and the hierarchical decorator system from @FrontMcp down to @App. Triggers: create a resource, build a prompt, write a provider, add an agent, job, workflow, plugin, adapter, or OpenAPI integration.
- when_to_use
- Trigger when creating or editing a non-tool FrontMCP component: a *.resource.ts, *.prompt.ts, *.provider.ts, *.agent.ts, *.job.ts, *.workflow.ts, *.plugin.ts…
- paths
- **/*.resource.ts, **/*.prompt.ts, **/*.provider.ts, **/*.agent.ts, **/*.job.ts, **/*.workflow.ts, **/*.plugin.ts, **/*.skill.ts
- tags
- router, development, tools, resources, prompts, agents, skills, guide
- category
- development
- targets
- all
- bundle
- recommended, minimal, full
- priority
- 10
- visibility
- both
- license
- Apache-2.0
- metadata.docs
- https://docs.agentfront.dev/frontmcp/fundamentals/overview
FrontMCP Development Router
Entry point for building MCP server components. This skill helps you find the right development reference based on what you want to build. It does not teach implementation details itself — it routes you to the specific reference (under references/) that does.
When to Use This Skill
Must Use
- Starting a FrontMCP development task and unsure which component type to build (tool vs resource vs prompt vs agent)
- Onboarding to the FrontMCP development model and need an overview of all building blocks
- Planning a feature that may require multiple component types working together
Recommended
- Looking up the canonical name of a development reference to install or search
- Comparing component types to decide which fits your use case
- Understanding how tools, resources, prompts, agents, and skills relate to each other
Skip When
- You already know which component to build (go directly to
create-tool,create-resource, etc.) - You need to configure server settings, not build components (see
frontmcp-config) - You need to deploy or build, not develop (see
frontmcp-deployment)
Decision: Use this skill when you need to figure out WHAT to build. Open the matching reference under
references/directly when you already know.
Prerequisites
- A scaffolded FrontMCP project (see
frontmcp-setupif you don't have one). - Familiarity with TypeScript decorators and Zod schemas — every component is decorator-driven and validates I/O via Zod.
- Decide whether you're adding to an existing
@Appor composing a new one (multi-app projects: seemulti-app-composition).
Steps
This is a router skill. The "steps" here are how to choose the right reference (a markdown file under references/), not how to implement a component.
- Identify the component type using the Scenario Routing Table below.
- Open the matching reference (e.g.
references/create-tool.md,references/create-resource.md) and follow its Steps section. - Compose, if needed: most non-trivial features need two or more components (e.g. tool + provider, resource + adapter). Read each reference independently before wiring them together.
- Test before integration (
frontmcp-testing) — every component type has a unit-test recipe.
Scenario Routing Table
| Scenario | Reference | Description |
|---|---|---|
| Expose an executable action that AI clients can call (full surface: schemas, DI, errors, throttling, auth, availability, elicitation, UI widgets, annotations, examples metadata, registration) | create-tool (top-level skill) | Single source of truth for everything inside @Tool({...}). Subsumes the former create-tool, create-tool-annotations, create-tool-output-schema-types, and create-tool-ui references. |
| Expose read-only data via a URI | create-resource | Static resources or URI template resources for dynamic data |
| Create a reusable conversation template or system prompt | create-prompt | Prompt entries with arguments and multi-turn message sequences |
| Build an autonomous AI loop that orchestrates tools | create-agent | Agent entries with LLM config, inner tools, and swarm handoff |
| Register shared services or configuration via DI | create-provider | Dependency injection tokens, lifecycle hooks, factory providers |
| Run a background task with progress and retries | create-job | Job entries with attempt tracking, retry config, and progress |
| Chain multiple jobs into a sequential pipeline | create-workflow | Workflow entries that compose jobs with data passing |
| Write instruction-only AI guidance (no code execution) | create-skill | Skill entries with markdown instructions from files, strings, or URLs |
| Write AI guidance that also orchestrates tools | create-skill-with-tools | Skill entries that combine instructions with registered tools |
| Look up any decorator signature or option | decorators-guide | Complete reference for @Tool, @Resource, @Prompt, @Agent, @App, @FrontMcp, and more |
| Overview of all official adapters | official-adapters | Router to all adapter types; adapter vs plugin comparison |
| Integrate an external API via OpenAPI spec | openapi-adapter | OpenapiAdapter with auth, polling, filtering, transforms, format resolution, $ref security |
| Use official plugins (caching, remember, feature flags) | official-plugins | Built-in plugins for caching, session memory, approval, and feature flags (dashboard is beta) |
| Connect to an external data source via a custom adapter | create-adapter | Create custom adapters for external data sources |
| Configure LLM settings for an agent component | create-agent-llm-config | Configure LLM settings for agent components |
| Add will/did/around lifecycle hooks to a plugin | create-plugin-hooks | Add lifecycle hooks to plugins (will/did/around) |
Recommended Reading Order
decorators-guide— Start here to understand the full decorator landscapecreate-tool— The most common building block (top-level skill — covers schemas, DI, errors, throttling, auth, UI widgets, annotations); learn tools firstcreate-resource— Expose data alongside toolscreate-prompt— Add reusable conversation templatescreate-provider— Share services across tools and resources via DIcreate-agent— Build autonomous AI loops (advanced)create-job/create-workflow— Background processing (advanced)create-skill/create-skill-with-tools— Author your own skills (meta)official-adapters/openapi-adapter— Integrate external APIs via OpenAPI specsofficial-plugins— Add caching, session memory, feature flags, and more
Cross-Cutting Patterns
| Pattern | Applies To | Rule |
|---|---|---|
| Naming convention | Tools | Use snake_case for tool names (get_weather, not getWeather) |
| Naming convention | Skills, resources | Use kebab-case for skill and resource names |
| File naming | All components | Use <name>.<type>.ts pattern (e.g., fetch-weather.tool.ts) |
| DI access | Tools, resources, prompts, agents | Use this.get(TOKEN) (throws) or this.tryGet(TOKEN) (returns undefined) |
| Error handling | All components | Use this.fail(err) with MCP error classes, not raw throw |
| Input validation | Tools | Always use Zod raw shapes (not z.object()) for inputSchema |
| Output validation | Tools | Always define outputSchema to prevent data leaks |
| Registration | All components | Best practice: register components in their owning @App. @FrontMcp also accepts entity arrays at the top level (tools, resources, skills, providers, plugins, jobs, channels, authorities) for simple single-app servers, but @App provides modularity, per-app auth, and lifecycle hooks. |
| Test files | All components | Use .spec.ts extension, never .test.ts |
Common Patterns
| Pattern | Correct | Incorrect | Why |
|---|---|---|---|
| Choosing component type | Tool for actions, Resource for data, Prompt for templates | Using a tool to return static data | Each type has protocol-level semantics; misuse confuses AI clients |
| Component registration | Register in @App arrays, compose apps in @FrontMcp | Register tools directly in @FrontMcp without an @App | Apps provide modularity; direct registration bypasses app-level hooks |
| Shared logic | Extract to a @Provider and inject via DI | Duplicate code across multiple tools | Providers are testable, lifecycle-managed, and scoped |
| Complex orchestration | Use @Agent with inner tools | Chain tool calls manually in a single tool | Agents handle LLM loops, retries, and tool selection automatically |
| Background work | Use @Job with retry config | Run long tasks inside a tool's execute() | Jobs have progress tracking, attempt awareness, and timeout handling |
Verification Checklist
Architecture
- Each component type matches its semantic purpose (action=tool, data=resource, template=prompt)
- Shared services use
@Providerwith DI tokens, not module-level singletons - Components are registered in
@Apparrays, apps composed in@FrontMcp
Development Workflow
- Files follow
<name>.<type>.tsnaming convention - Each component has a corresponding
.spec.tstest file -
decorators-guideconsulted for unfamiliar decorator options
Troubleshooting
| Problem | Cause | Solution |
|---|---|---|
| Unsure which component type to use | Requirements are ambiguous | Check the Scenario Routing Table above; if the action modifies state, use a tool; if it returns data by URI, use a resource |
| Component not discovered at runtime | Not registered in @App or @FrontMcp arrays | Add to the appropriate array (tools, resources, prompts, etc.) |
| DI token not resolving | Provider not registered in scope | Register the provider in the providers array of the same @App |
| Need both AI guidance and tool execution | Used create-skill but need tools too | Switch to create-skill-with-tools which combines instructions with registered tools |
Examples
Each reference has matching examples under examples/<reference>/:
create-adapter
| Example | Level | Description |
|---|---|---|
basic-api-adapter | Basic | A minimal adapter that fetches operation definitions from an external API and generates MCP tools. |
namespaced-adapter | Intermediate | An adapter that namespaces generated tools to avoid collisions and includes proper error handling for startup failures. |
create-agent-llm-config
| Example | Level | Description |
|---|---|---|
anthropic-config | Basic | Configuring an agent with the Anthropic provider and common model options. |
openai-config | Basic | Configuring an agent with the OpenAI provider and different model options. |
create-agent
| Example | Level | Description |
|---|---|---|
basic-agent-with-tools | Basic | An autonomous agent that uses inner tools to review GitHub pull requests. |
custom-multi-pass-agent | Intermediate | An agent that overrides execute() to perform multi-pass LLM reasoning with this.completion(). |
nested-agents-with-swarm | Advanced | Composing specialized sub-agents and configuring swarm-based handoff between agents. |
create-job
| Example | Level | Description |
|---|---|---|
basic-report-job | Basic | A minimal job that generates a report with progress tracking and structured output. |
job-with-permissions | Advanced | A data export job with declarative permission controls, plus a function-style job for simple tasks. |
job-with-retry | Intermediate | A job that syncs data from an external API with automatic retry, exponential backoff, and batch progress tracking. |
Show full SKILL.md (868 more words)Show less
create-plugin-hooks
| Example | Level | Description |
|---|---|---|
basic-logging-plugin | Basic | Demonstrates a plugin that logs tool execution using @Will and @Did hook decorators from the pre-built ToolHook export. |
caching-with-around | Intermediate | Demonstrates wrapping tool execution with an @Around hook to implement result caching with TTL-based expiry. |
tool-level-hooks-and-stage-short-circuit | Advanced | Demonstrates two advanced patterns: adding @Will/@Did hooks directly on a @Tool class (scoped to that tool only), and ending the flow from a plugin @Stage hook with ctx.respond() to mock one tool. |
create-plugin
| Example | Level | Description |
|---|---|---|
basic-plugin-with-provider | Basic | A minimal plugin that contributes an injectable service via the providers and exports arrays. |
configurable-dynamic-plugin | Advanced | A plugin that accepts runtime configuration via DynamicPlugin and extends decorator metadata with custom fields. |
plugin-with-context-extension | Intermediate | A plugin that adds a this.auditLog property to all execution contexts using context extensions and module augmentation. |
create-prompt
| Example | Level | Description |
|---|---|---|
basic-prompt | Basic | A simple prompt that generates a structured code review message from user-provided arguments. |
dynamic-rag-prompt | Advanced | A prompt that queries a knowledge base via DI to build context-aware messages at runtime. |
multi-turn-debug-session | Intermediate | A prompt that uses alternating user/assistant messages to guide a structured debugging conversation. |
create-provider
| Example | Level | Description |
|---|---|---|
basic-database-provider | Basic | A provider that manages a database connection pool with onInit() and onDestroy() lifecycle hooks. |
config-and-api-providers | Intermediate | A configuration provider with readonly environment settings and an HTTP API client provider. |
create-resource
| Example | Level | Description |
|---|---|---|
basic-static-resource | Basic | A static resource that exposes application configuration at a fixed URI. |
binary-and-multi-content | Advanced | A resource serving binary blob data and a resource returning multiple content items. |
parameterized-template | Intermediate | A resource template with typed URI parameters and argument autocompletion. |
create-skill-with-tools
| Example | Level | Description |
|---|---|---|
basic-tool-orchestration | Basic | A skill that guides an AI client through a deploy workflow using referenced MCP tools. |
directory-skill-with-tools | Advanced | A directory-based skill loaded with skillDir(), plus a class-based skill using Agent Skills spec metadata fields. |
incident-response-skill | Intermediate | A skill that uses object-style tool references with purpose descriptions and required flags, plus strict validation. |
create-skill
| Example | Level | Description |
|---|---|---|
basic-inline-skill | Basic | A minimal instruction-only skill with inline content and the function builder alternative. |
directory-based-skill | Advanced | A skill loaded from a directory structure with SKILL.md frontmatter, plus file-based and URL-based instruction sources. |
parameterized-skill | Intermediate | A skill with customizable parameters, usage examples for AI guidance, and controlled visibility. |
create-tool (migrated to top-level skill)
The full @Tool({...}) surface — including the former create-tool-annotations, create-tool-output-schema-types, and create-tool-ui references — now lives in the top-level create-tool skill. See its examples/ directory for 25 combination examples covering schemas, DI, errors, throttling, auth, availability, elicitation, UI widgets, annotations, examples metadata, and job hand-off.
create-workflow
| Example | Level | Description |
|---|---|---|
basic-deploy-pipeline | Basic | A linear workflow that builds, tests, and deploys a service with step dependencies and dynamic input. |
parallel-validation-pipeline | Intermediate | A workflow that validates multiple datasets in parallel, then conditionally merges results or notifies on failure. |
webhook-triggered-workflow | Advanced | A CI/CD workflow triggered by a webhook, featuring continueOnError, per-step conditions, and the workflow() function builder. |
decorators-guide
| Example | Level | Description |
|---|---|---|
agent-skill-job-workflow | Advanced | Demonstrates the advanced decorator types: @Agent for autonomous AI agents, @Skill for knowledge packages, @Job for background tasks, and @Workflow for multi-step orchestration. |
basic-server-with-app-and-tools | Basic | Demonstrates the minimal decorator hierarchy to create a working FrontMCP server with one app containing a tool and a resource. |
multi-app-with-plugins-and-providers | Intermediate | Demonstrates a server with multiple @App modules, a @Provider for dependency injection, and a @Plugin for cross-cutting concerns. |
openapi-adapter
| Example | Level | Description |
|---|---|---|
basic-openapi-adapter | Basic | Demonstrates converting an OpenAPI specification into MCP tools automatically using OpenapiAdapter with minimal configuration. |
authenticated-adapter-with-polling | Intermediate | Demonstrates configuring authentication (API key and bearer token) and automatic spec polling for OpenAPI adapters. |
format-resolution-and-custom-resolvers | Intermediate | Demonstrates using built-in and custom format resolvers to enrich tool input schemas with concrete constraints from OpenAPI format values. |
ref-security-and-filtering | Intermediate | Demonstrates configuring $ref / spec-URL resolution security to prevent SSRF attacks (GHSA-65h7-9wrw-629c) and filtering which API operations become MCP tools. |
multi-api-hub-with-inline-spec | Advanced | Demonstrates registering multiple OpenAPI adapters from different APIs in a single app, including one with an inline spec definition instead of a remote URL. |
official-plugins
| Example | Level | Description |
|---|---|---|
cache-and-feature-flags | Intermediate | Demonstrates combining the Cache plugin for tool result caching with the Feature Flags plugin for gating tools behind flags. |
production-multi-plugin-setup | Advanced | Demonstrates a production-ready server configuration combining CodeCall, Remember, Approval, Cache, and Feature Flags plugins with Redis storage and external flag services. |
remember-plugin-session-memory | Basic | Demonstrates installing the Remember plugin and using this.remember in tools to store and retrieve session memory. |
Accessing This Skill
Skills are distributed as plain SKILL.md files plus a sibling references/
and examples/ tree, so consumers can pick whichever access mode fits:
| Mode | How it works |
|---|---|
| Filesystem | Read libs/skills/catalog/frontmcp-development/ directly from a clone of the catalog repo, or from a published @frontmcp/skills install. SKILL.md is the entry point. |
frontmcp CLI | frontmcp skills list, frontmcp skills read frontmcp-development, frontmcp skills read frontmcp-development:references/<file>.md, frontmcp skills install frontmcp-development — no server required. |
MCP skill:// | When a developer mounts this skill into their own FrontMCP server (@FrontMcp({ skills: [...] })), the SDK exposes it via SEP-2640 resources: skill://frontmcp-development/SKILL.md, skill://frontmcp-development/references/{file}.md, etc. The server’s skill://index.json returns the SEP-2640 discovery document for everything mounted on it. |
The catalog itself is not an MCP server. The skill:// URIs only resolve
when a server has been configured to host this skill.
Reference
- FrontMCP Overview
- Related skills:
create-tool(top-level),create-resource,create-prompt,create-agent,create-provider,create-job,create-workflow,create-skill,create-skill-with-tools,decorators-guide,official-adapters,openapi-adapter,official-plugins
© agentfront, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 71 other files (references) in libs/skills/catalog/frontmcp-development of agentfront/frontmcp.
- SKILL.md
- examples/create-adapter/basic-api-adapter.md
- examples/create-adapter/namespaced-adapter.md
- examples/create-agent-llm-config/anthropic-config.md
- examples/create-agent-llm-config/openai-config.md
- examples/create-agent/basic-agent-with-tools.md
- examples/create-agent/custom-multi-pass-agent.md
- examples/create-agent/nested-agents-with-swarm.md
- examples/create-job/basic-report-job.md
- examples/create-job/job-with-permissions.md
- examples/create-job/job-with-retry.md
- examples/create-plugin-hooks/basic-logging-plugin.md
- examples/create-plugin-hooks/caching-with-around.md
- examples/create-plugin-hooks/tool-level-hooks-and-stage-short-circuit.md
- examples/create-plugin
- … and 57 more
Open the folder on GitHubat commit 8f59ba8
Compare with similar skills
Frontmcp Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Frontmcp Development this skillagentfront/frontmcp | 146 | — | ~11k | Automated safety check: Pass | Apache-2.0 | |
| OpenAPI to MCP Servermcp-use/mcp-use | 11k | — | ~5.2k | Automated safety check: Pass | Apache-2.0 | |
| PR Reviewconfluentinc/mcp-confluent | 167 | — | ~4.6k | Automated safety check: Notes | MIT | |
| MCP Server Builderalirezarezvani/claude-skills | 28k | — | ~985 | Automated safety check: Pass | MIT | |
| MCP Server Builderborghei/Claude-Skills | 874 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Generate MCP Servertrycompai/comp | 2k | — | ~2.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
PR Review
confluentinc/mcp-confluent
Reviews pull requests for the Confluent MCP server. An agent skill from confluentinc/mcp-confluent.
MCP Server Builder
alirezarezvani/claude-skills
Design and ship production-ready MCP (Model Context Protocol) servers from OpenAPI contracts instead of hand-written tool wrappers.
MCP Server Builder
borghei/Claude-Skills
Build MCP (Model Context Protocol) servers with tool definitions, resource providers, prompt templates, and transports.
Generate MCP Server
trycompai/comp
A skill your agent uses when generating an MCP server from an OpenAPI spec with Speakeasy.
API Endpoint Contract
trycompai/comp
The contract every new or modified API endpoint must follow so it is correct for the public OpenAPI spec, the MCP server (npm @trycompai/mcp-server), the ValidationPipe, and the docs.
More from agentfront/frontmcp
All 12 skills in this repoFrontmcp Auth UI
agentfront/frontmcp
A skill your agent uses when customizing, branding, or replacing the built-in FrontMCP OAuth pages (the login, consent, federated-select, incremental-authorization, and error pages) with your own…
Frontmcp Channels
agentfront/frontmcp
A skill your agent uses when pushing real-time notifications or events into Claude Code (or another MCP client) sessions, or building two-way chat bridges.
Frontmcp Extensibility
agentfront/frontmcp
A skill your agent uses when extending FrontMCP beyond the core SDK by integrating external npm packages, libraries, or third-party services into providers and tools.
Frontmcp Observability
agentfront/frontmcp
A skill your agent uses when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server.
Frontmcp Authorities
agentfront/frontmcp
A skill your agent uses when implementing authorization and access control for FrontMCP tools, resources, prompts, or skills, deciding who may invoke what.
Frontmcp Config
agentfront/frontmcp
A skill your agent uses when configuring a FrontMCP server through frontmcp.config or the @FrontMcp options.
Related
Categories
Questions about Frontmcp Development
What does Frontmcp Development do?
A skill your agent uses when building any FrontMCP server component other than a tool (for tools, use create-tool). Frontmcp Development is an agent skill from agentfront/frontmcp. Use when building any FrontMCP server component other than a tool (for tools, use create-tool).
When should I use Frontmcp Development?
Frontmcp Development fits situations like: building any FrontMCP server component other than a tool (for tools; use create-tool).
How do I install Frontmcp Development in Claude Code?
Run `npx skills add agentfront/frontmcp --skill frontmcp-development -a claude-code`. Or copy the skill folder (libs/skills/catalog/frontmcp-development in agentfront/frontmcp) into .claude/skills/frontmcp-development in your project. Claude Code loads it when a task matches its description.
How do I install Frontmcp Development in Codex?
Run `npx skills add agentfront/frontmcp --skill frontmcp-development -a codex`. Or copy the skill folder (libs/skills/catalog/frontmcp-development in agentfront/frontmcp) into .agents/skills/frontmcp-development in your project. Codex loads it when a task matches its description.
Can I use Frontmcp Development in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add agentfront/frontmcp --skill frontmcp-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frontmcp-development, .gemini/skills/frontmcp-development, .github/skills/frontmcp-development and .opencode/skills/frontmcp-development in your project.
What does Frontmcp Development need to run?
SKILL.md names no scripts, command-line tools or credentials: Frontmcp Development is instructions for the agent only.
Does Frontmcp Development access the network?
SKILL.md names 1 domain. As links in the text: docs.agentfront.dev. This is read from the text; nothing was executed.
Is Frontmcp Development safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Frontmcp Development use?
Frontmcp Development is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Frontmcp Development use?
About 11k tokens (SKILL.md is roughly 42k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 115k tokens, read only when the agent opens those files.
What are the alternatives to Frontmcp Development?
Skills that share tags, products or a category with Frontmcp Development: OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars), PR Review (confluentinc/mcp-confluent, 167 stars), MCP Server Builder (alirezarezvani/claude-skills, 28k stars) and MCP Server Builder (borghei/Claude-Skills, 874 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Frontmcp Development?
agentfront (a GitHub organization) maintains it in agentfront/frontmcp, which has 146 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 7, 2026.
Source: agentfront/frontmcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.