Agent skill

Frontmcp Guides

by agentfront in agentfront/frontmcp

Tutorials, end-to-end walkthroughs, and complete reference projects for FrontMCP.

Apache-2.0Auto-check passedTesting & QA

Install Frontmcp Guides

skills CLI
$ npx skills add agentfront/frontmcp --skill frontmcp-guides -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install agentfront/frontmcp frontmcp-guides --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/agentfront/frontmcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/libs/skills/catalog/frontmcp-guides .claude/skills/frontmcp-guides && rm -rf skills-src

Use ~/.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/

Facts

Skill name
frontmcp-guides
GitHub stars
146
Token cost
~6.3k tokens
SKILL.md length
1,423 words
Files
13 (incl. references)
Skills in repo
12
Repo updated
First seen
Licence
Apache-2.0

At a glance

Tutorials, end-to-end walkthroughs, and complete reference projects for FrontMCP.

  • Works in 5 steps: What does the server do? → How is it organized? → How is it secured? → …
  • You want a getting-started guide
  • SKILL.md covers When to Use This Skill, Prerequisites, Steps and Planning Checklist, plus 6 more sections
  • Calls npm and jest; needs ANTHROPIC_API_KEY

What it does

Frontmcp Guides is an agent skill from agentfront/frontmcp. Tutorials, end-to-end walkthroughs, and complete reference projects for FrontMCP. Use when you want a getting-started guide, a full worked example, or to learn best practices by following a step-by-step build rather than a single API reference. Includes a beginner weather-API server (tool plus static resource, Zod schemas, E2E tests), an authenticated task manager (CRUD tools, Redis storage, OAuth, Vercel deploy, authenticated E2E tests), and a multi-app knowledge base (vector search, semantic resources, an AI…

Its SKILL.md is about 6.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 17 other files, including reference files (for example `examples/example-knowledge-base/agent-and-plugin.md`, `examples/example-knowledge-base/multi-app-composition.md` and `examples/example-knowledge-base/vector-search-and-resources.md`).

It sits in Testing & QA, covering End-to-end testing, Task management and Forms and validation. It works with Vercel, Redis, Zod and Model Context Protocol. 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

  • You want a getting-started guide
  • A full worked example
  • Learn best practices by following a step-by-step build rather than a single API reference

Example prompts

  • “/frontmcp-guides”

Requirements

  • Node.js

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. What does the server do?
  2. How is it organized?
  3. How is it secured?
  4. Where does it deploy?
  5. How is it tested?

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

    Shell commands in SKILL.md call:

    • npm
    • jest

    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 these keys or tokens, usually read from environment variables:

    • ANTHROPIC_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Frontmcp Guides loads about 6.3k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 175 tokens; SKILL.md has 1,423 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~175
When it runs · the whole SKILL.md, loaded when a task matches
~6.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~17k

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). 1,423 words, ~6,297 tokens.

Download SKILL.mdSave it as .claude/skills/frontmcp-guides/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
frontmcp-guides
description
Tutorials, end-to-end walkthroughs, and complete reference projects for FrontMCP. Use when you want a getting-started guide, a full worked example, or to learn best practices by following a step-by-step build rather than a single API reference. Includes a beginner weather-API server (tool plus static resource, Zod schemas, E2E tests), an authenticated task manager (CRUD tools, Redis storage, OAuth, Vercel deploy, authenticated E2E tests), and a multi-app knowledge base (vector search, semantic resources, an AI research agent, audit logging). Triggers: tutorial, walkthrough, how do I build, getting started, end-to-end example, sample project, learn FrontMCP, full app example.
tags
guides, examples, best-practices, architecture, walkthrough, end-to-end
category
guides
targets
all
bundle
recommended, full
priority
10
visibility
both
license
Apache-2.0
metadata.docs
https://docs.agentfront.dev/frontmcp/guides/your-first-tool

FrontMCP End-to-End Guides

Complete build walkthroughs and best practices for FrontMCP servers. Each example starts from an empty directory and ends with a deployed, tested server. Every pattern references the specific skill that teaches it.

When to Use This Skill

Must Use
  • Starting a new FrontMCP project from scratch and want a complete walkthrough to follow
  • Learning FrontMCP architecture by building progressively complex real examples
  • Need to see how multiple skills work together in a complete application
  • Planning a new project and want to see how similar architectures are structured
  • Onboarding a team member who learns best from complete working examples
  • Reviewing best practices for file organization, naming, and code patterns
Skip When
  • You need to learn one specific component type (use the specific reference, e.g., create-tool under frontmcp-development/references/)
  • Looking for the right reference for a task (use domain routers: frontmcp-development, frontmcp-deployment, etc.)
  • You need CLI/install instructions for the skills system (see frontmcp-skills-usage)

Decision: Use this skill when you want to see how everything fits together. Open individual references under each router's references/ directory when you need focused instruction.

Prerequisites

  • Node.js 24+ and npm/yarn installed
  • Familiarity with TypeScript and decorators
  • frontmcp CLI available globally (npm install -g frontmcp)

Steps

  1. Choose an example that matches your project's complexity level (Beginner, Intermediate, Advanced)
  2. Work through the Planning Checklist to define your project's scope
  3. Follow the example code and architecture, referencing individual skills for deeper guidance
  4. Verify your implementation using the Verification Checklist at the end of this skill

Planning Checklist

Before writing any code, answer these questions:

1. What does the server do?
  • What tools does it expose? (actions AI clients can call)
  • What resources does it expose? (data AI clients can read)
  • What prompts does it expose? (conversation templates)
2. How is it organized?
  • Single app or multiple apps? (see multi-app-composition)
  • Standalone project or Nx monorepo? (see project-structure-standalone, project-structure-nx)
3. How is it secured?
  • Public (no auth), transparent (passthrough), local (self-contained), or remote (OAuth)? (see configure-auth)
  • What session storage? Memory (dev), Redis (prod), Vercel KV (serverless)? (see configure-session)
4. Where does it deploy?
  • Node, Vercel, Lambda, Cloudflare, CLI, browser, or SDK? (see frontmcp-deployment)
  • What transport? stdio (local), SSE (streaming), Streamable HTTP (stateless)? (see configure-transport)
5. How is it tested?
  • Unit tests for each component (see setup-testing)
  • E2E tests for protocol-level flows
  • Coverage target: 95%+

Example 1: Weather API (Beginner)

Skills used: setup-project, create-tool, create-resource, setup-testing, deploy-to-node

A simple MCP server that exposes a weather lookup tool and a resource for supported cities.

Architecture
text
weather-api/
├── src/
│   ├── main.ts              # @FrontMcp server (deploy-to-node)
│   ├── weather.app.ts       # @App with tools and resources
│   ├── tools/
│   │   └── get-weather.tool.ts    # @Tool: fetch weather by city (create-tool)
│   └── resources/
│       └── cities.resource.ts     # @Resource: list supported cities (create-resource)
├── test/
│   ├── get-weather.tool.spec.ts   # Unit tests (setup-testing)
│   └── weather.e2e.spec.ts        # E2E protocol test (setup-testing)
└── package.json
Key Code

Server entry point (setup-project):

typescript
import { FrontMcp } from '@frontmcp/sdk';

import { WeatherApp } from './weather.app';

@FrontMcp({
  info: { name: 'weather-api', version: '1.0.0' },
  apps: [WeatherApp],
})
export default class WeatherServer {}

Tool (create-tool):

typescript
import { Tool, ToolContext, z } from '@frontmcp/sdk';

@Tool({
  name: 'get_weather',
  description: 'Get current weather for a city',
  inputSchema: {
    city: z.string().min(1).describe('City name'),
  },
  outputSchema: {
    temperature: z.number(),
    condition: z.string(),
    humidity: z.number(),
  },
})
export class GetWeatherTool extends ToolContext {
  async execute(input: { city: string }) {
    const city = encodeURIComponent(input.city);
    const data = await this.fetch(`https://api.weather.example.com/v1?city=${city}`);
    const json = await data.json();
    return { temperature: json.temp, condition: json.condition, humidity: json.humidity };
  }
}

Resource (create-resource):

typescript
import { ReadResourceResult, Resource, ResourceContext } from '@frontmcp/sdk';

@Resource({
  uri: 'weather://cities',
  name: 'Supported Cities',
  description: 'List of cities with weather data',
  mimeType: 'application/json',
})
export class CitiesResource extends ResourceContext {
  async execute(uri: string): Promise<ReadResourceResult> {
    return {
      contents: [
        {
          uri,
          mimeType: 'application/json',
          text: JSON.stringify(['London', 'Tokyo', 'New York', 'Paris', 'Sydney']),
        },
      ],
    };
  }
}

Full working code: See references/example-weather-api.md


Example 2: Task Manager (Intermediate)

Skills used: setup-project, create-tool, create-provider, configure-auth, configure-session, setup-redis, setup-testing, deploy-to-vercel

An authenticated task management server with CRUD tools, Redis storage, and OAuth.

Architecture
text
task-manager/
├── src/
│   ├── main.ts                    # @FrontMcp with auth: { mode: 'remote' }
│   ├── tasks.app.ts               # @App with CRUD tools + provider
│   ├── providers/
│   │   └── task-store.provider.ts # @Provider: Redis-backed task storage (create-provider)
│   ├── tools/
│   │   ├── create-task.tool.ts    # @Tool: create a task (create-tool)
│   │   ├── list-tasks.tool.ts     # @Tool: list tasks (create-tool)
│   │   ├── update-task.tool.ts    # @Tool: update task status (create-tool)
│   │   └── delete-task.tool.ts    # @Tool: delete a task (create-tool)
│   └── types/
│       └── task.ts                # Shared task interface
├── test/
│   ├── *.spec.ts                  # Unit tests per tool
│   └── tasks.e2e.spec.ts          # E2E with auth flow
├── vercel.json                    # Vercel config (deploy-to-vercel)
└── package.json
Key Code

Server with auth (configure-auth, configure-session, setup-redis):

typescript
@FrontMcp({
  info: { name: 'task-manager', version: '1.0.0' },
  apps: [TasksApp],
  auth: { mode: 'remote', provider: 'https://auth.example.com', clientId: 'my-client-id' },
  redis: { provider: 'redis', host: process.env.REDIS_URL ?? 'localhost' },
})
export default class TaskManagerServer {}

Provider for shared storage (create-provider):

typescript
import { Provider, ProviderScope } from '@frontmcp/sdk';

@Provider({ name: 'task-store', scope: ProviderScope.GLOBAL })
export class TaskStoreProvider {
  async create(task: Task): Promise<Task> {
    /* Redis-backed implementation */
  }
  async list(userId: string): Promise<Task[]> {
    /* ... */
  }
  async update(id: string, data: Partial<Task>): Promise<Task> {
    /* ... */
  }
  async delete(id: string): Promise<void> {
    /* ... */
  }
}

Use the class itself as the DI token (this.get(TaskStoreProvider)). For factory-built singletons (e.g. when you need async setup before the class is constructed), use AsyncProvider({ provide, name, scope, useFactory }) instead.

Tool with DI (create-tool + create-provider):

typescript
import { Tool, ToolContext, UnauthorizedError, z } from '@frontmcp/sdk';

@Tool({
  name: 'create_task',
  description: 'Create a new task',
  inputSchema: {
    title: z.string().min(1).describe('Task title'),
    priority: z.enum(['low', 'medium', 'high']).default('medium'),
  },
  outputSchema: { id: z.string(), title: z.string(), priority: z.string(), status: z.string() },
})
export class CreateTaskTool extends ToolContext {
  async execute(input: { title: string; priority: string }) {
    const store = this.get(TaskStoreProvider);
    const userId = this.auth?.user.sub;
    if (!userId) this.fail(new UnauthorizedError('Authentication required'));
    return store.create({ title: input.title, priority: input.priority, status: 'pending', userId });
  }
}

Full working code: See references/example-task-manager.md


Example 3: Knowledge Base (Advanced)

Skills used: setup-project, multi-app-composition, create-tool, create-resource, create-agent, create-skill-with-tools, create-plugin, official-plugins, configure-auth, deploy-to-vercel

A multi-app knowledge base with AI-powered search, document ingestion, and an autonomous research agent.

Architecture
text
knowledge-base/
├── src/
│   ├── main.ts                          # @FrontMcp composing 3 apps
│   ├── ingestion/
│   │   ├── ingestion.app.ts             # @App: document ingestion
│   │   ├── tools/ingest-document.tool.ts
│   │   └── providers/vector-store.provider.ts
│   ├── search/
│   │   ├── search.app.ts               # @App: search and retrieval
│   │   ├── tools/search-docs.tool.ts
│   │   └── resources/doc.resource.ts
│   ├── research/
│   │   ├── research.app.ts             # @App: AI research agent
│   │   └── agents/researcher.agent.ts  # @Agent: autonomous research loop
│   └── plugins/
│       └── audit-log.plugin.ts         # @Plugin: audit logging
├── test/
│   └── *.spec.ts
├── vercel.json
└── package.json
Key Code

Multi-app composition (multi-app-composition):

typescript
@FrontMcp({
  info: { name: 'knowledge-base', version: '1.0.0' },
  apps: [IngestionApp, SearchApp, ResearchApp],
  plugins: [AuditLogPlugin],
  auth: { mode: 'remote', provider: 'https://auth.example.com', clientId: 'my-client-id' },
  redis: { provider: 'redis', host: process.env.REDIS_URL ?? 'localhost' },
})
export default class KnowledgeBaseServer {}

AI Research Agent (create-agent):

typescript
@Agent({
  name: 'research_topic',
  description: 'Research a topic across the knowledge base and synthesize findings',
  inputSchema: {
    topic: z.string().describe('Research topic'),
    depth: z.enum(['shallow', 'deep']).default('shallow'),
  },
  llm: {
    provider: 'anthropic',
    model: 'claude-sonnet-4-6',
    apiKey: { env: 'ANTHROPIC_API_KEY' },
    maxTokens: 4096,
  }, // provider and model are client-configurable
  execution: { maxIterations: 5 },
  systemInstructions:
    'Search for relevant documents using search_docs, synthesize findings, and produce a structured summary with source attribution.',
  tools: [SearchDocsTool, IngestDocumentTool],
})
export class ResearcherAgent extends AgentContext {}

The framework drives the LLM tool-use loop via the agents:call-agent flow — you don't override execute(). Configure iteration limits and other runtime knobs through the @Agent({ execution: { maxIterations } }) block.

Full working code: See references/example-knowledge-base.md


Best Practices

Planning
PracticeWhyReference
Start with the @App boundaries, not individual toolsApps define module boundaries; tools are implementation detailsmulti-app-composition
Choose auth mode and storage before writing toolsAuth affects session handling, which affects storage requirementsconfigure-auth, configure-session
Pick your deployment target earlyTarget determines transport, storage, and build constraintsfrontmcp-deployment
Organizing Code
PracticeWhyReference
One class per file with <name>.<type>.ts namingConsistency, generator compatibility, clear importsproject-structure-standalone
Group by feature, not by type, for 10+ componentsFeature folders scale better than flat tools/ directoriesproject-structure-standalone
Extract shared logic into @Provider classesTestable, lifecycle-managed, injected via DIcreate-provider
Writing Code
PracticeWhyReference
Always define outputSchema on toolsPrevents data leaks, enables CodeCall chainingcreate-tool
Use this.fail() with MCP error classesProper error codes in protocol responsescreate-tool
Use this.get(TOKEN) not this.tryGet(TOKEN)!Clear error on missing dependency vs silent nullcreate-provider
Use Zod raw shapes, not z.object()Framework wraps internally; double-wrapping breaks validationcreate-tool

Common Patterns

PatternCorrectIncorrectWhy
Project startPlan apps and auth first, then build toolsJump straight into writing toolsArchitecture decisions are expensive to change later
Code organizationFeature folders with <name>.<type>.tsFlat directory with generic namesScales to large projects and matches generator output
Shared state@Provider with DI tokenModule-level singleton or global variableDI is testable, lifecycle-managed, and scoped per request
Error handlingthis.fail(new ResourceNotFoundError(...))throw new Error('not found')MCP error codes enable proper client error handling
TestingUnit tests per component + E2E for protocolOnly E2E tests or only unit testsBoth layers catch different types of bugs

Verification Checklist

Show full SKILL.md (572 more words)Show less
Architecture
  • Apps define clear module boundaries with no circular imports
  • Shared logic extracted into providers, not duplicated across tools
  • Auth mode and storage chosen before writing tools
Code Quality
  • All tools have outputSchema defined
  • All files follow <name>.<type>.ts naming convention
  • All test files use .spec.ts extension
  • Coverage at 95%+ across all metrics
Production Readiness
  • Secrets stored in environment variables, not source code
  • Session storage uses Redis/KV in production (not memory)
  • Rate limiting configured for public-facing tools
  • E2E tests exercise the full protocol flow

Troubleshooting

ProblemCauseSolution
Unsure where to startNo project planRun through the Planning Checklist above before writing code
Architecture feels wrongWrong app boundaries or component typesReview the Scenario Routing Table in frontmcp-development
Feature works locally but fails deployedEnvironment-specific config (storage, auth, transport)Check the Target Comparison in frontmcp-deployment
Tests pass but coverage below 95%Missing error path or branch testsRun jest --coverage and add tests for uncovered lines
Provider state leaking between requestsUsing module-level state instead of DIMove state into a @Provider scoped per request

Examples

Each reference has matching examples under examples/<reference>/:

example-knowledge-base
ExampleLevelDescription
agent-and-pluginAdvancedShows an autonomous research agent with inner tools and configurable depth, and a plugin that hooks into tool execution for audit logging.
multi-app-compositionBasicShows how to compose multiple apps (Ingestion, Search, Research) into a single server with shared providers, plugins, and agent registration.
vector-search-and-resourcesIntermediateShows a semantic search tool with embedding generation and a resource template for retrieving documents by ID using URI parameters.
example-task-manager
ExampleLevelDescription
auth-and-crud-toolsBasicShows how to create CRUD tools with authentication, using this.context.session for user isolation and this.get() for dependency injection.
authenticated-e2e-testsAdvancedShows how to write E2E tests with authentication using TestTokenFactory, and unit tests for tools that require session context.
redis-provider-with-diIntermediateShows how to create a Redis-backed provider with a DI token, lifecycle hooks (onInit/onDestroy), and how tools inject it.
example-weather-api
ExampleLevelDescription
server-and-app-setupBasicShows the server entry point, app registration, and static resource for a beginner FrontMCP weather API server.
unit-and-e2e-testsIntermediateShows how to write unit tests for tools by mocking context methods, and E2E tests using McpTestClient and TestServer.
weather-tool-with-schemasBasicShows how to create a tool with Zod input and output schemas, use this.fetch() for HTTP calls, and handle errors with this.fail().

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:

ModeHow it works
FilesystemRead libs/skills/catalog/frontmcp-guides/ directly from a clone of the catalog repo, or from a published @frontmcp/skills install. SKILL.md is the entry point.
frontmcp CLIfrontmcp skills list, frontmcp skills read frontmcp-guides, frontmcp skills read frontmcp-guides:references/<file>.md, frontmcp skills install frontmcp-guides — 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-guides/SKILL.md, skill://frontmcp-guides/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

  • Your First Tool
  • Domain routers: frontmcp-development, frontmcp-deployment, frontmcp-testing, frontmcp-config
  • Core references: setup-project, create-tool, create-resource, create-provider, create-agent, configure-auth, setup-testing (each lives under its parent router's references/ directory, e.g. frontmcp-development/references/create-tool.md)
  • Mandatory boundaries: import MCP protocol types and McpError from @frontmcp/protocol (never directly from @modelcontextprotocol/sdk); use @frontmcp/utils for crypto and file-system operations.

© 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 12 other files (references) in libs/skills/catalog/frontmcp-guides of agentfront/frontmcp.

  • SKILL.md
  • examples/example-knowledge-base/agent-and-plugin.md
  • examples/example-knowledge-base/multi-app-composition.md
  • examples/example-knowledge-base/vector-search-and-resources.md
  • examples/example-task-manager/auth-and-crud-tools.md
  • examples/example-task-manager/authenticated-e2e-tests.md
  • examples/example-task-manager/redis-provider-with-di.md
  • examples/example-weather-api/server-and-app-setup.md
  • examples/example-weather-api/unit-and-e2e-tests.md
  • examples/example-weather-api/weather-tool-with-schemas.md
  • references/example-knowledge-base.md
  • references/example-task-manager.md
  • references/example-weather-api.md

Open the folder on GitHubat commit 8f59ba8

Compare with similar skills

Frontmcp Guides 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.

Frontmcp Guides compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Frontmcp Guides this skillagentfront/frontmcp146—~6.3kAutomated safety check: PassApache-2.0
Common Tasksidavidov13/agentic-playwright223—~2.5kAutomated safety check: PassMIT
MCP Server Patternsaffaan-m/ECC275k1 repos~551Automated safety check: PassMIT
MCP Server Patternsmajiayu000/claude-skill-registry6666 repos~1kAutomated safety check: PassMIT
API Testingfugazi/test-automation-skills-agents247—~1.5kAutomated safety check: PassMIT
Bug HuntUse-Tusk/drift-node-sdk173—~3.6kAutomated safety check: PassApache-2.0

Similar skills

  • Common Tasks

    idavidov13/agentic-playwright

    Copy-paste AI prompt templates for common Playwright scaffold development tasks — adding page objects, functional/E2E/API tests, Zod schemas, factories, fixtures, and components.

    223 GitHub stars~2.5k tokensUpdated 7 days ago
    Testing & QAAuto-check passed
  • 使用Node/TypeScript SDK构建MCP服务器——工具、资源、提示、Zod验证、stdio与可流式HTTP对比。使用Context7或官方MCP文档获取最新API信息。

    275k GitHub starsUsed in 1 repo~551 tokens
    Agent WorkflowsAuto-check passed
  • MCP Server Patterns

    majiayu000/claude-skill-registry

    Build MCP servers with Node/TypeScript SDK — tools, resources, prompts, Zod validation, stdio vs Streamable HTTP.

    666 GitHub starsUsed in 6 repos~1k tokens
    Agent WorkflowsAuto-check passed
  • API Testing

    fugazi/test-automation-skills-agents

    Test REST and GraphQL endpoint contracts using Playwright request fixture (TypeScript) or REST Assured (Java).

    247 GitHub stars~1.5k tokensUpdated 4 days ago
    Testing & QAAuto-check passed
  • Bug Hunt

    Use-Tusk/drift-node-sdk

    Hunt for instrumentation bugs by analyzing code gaps and running e2e tests through DISABLED/RECORD/REPLAY cycle

    173 GitHub stars~3.6k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed
  • Data Strategy

    idavidov13/agentic-playwright

    Test data strategy for the Playwright scaffold — Faker + Zod factories for dynamic happy-path data, static TS files (.ts with as const exports — never .json) for domain-specific curated invalid…

    223 GitHub stars~3.4k tokensUpdated 7 days ago
    Testing & QAAuto-check passed

More from agentfront/frontmcp

All 12 skills in this repo
  • Frontmcp 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…

    146 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • 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.

    146 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • 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.

    146 GitHub stars~3.2k tokensUpdated yesterday
    Auto-check passed
  • Frontmcp Observability

    agentfront/frontmcp

    A skill your agent uses when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server.

    146 GitHub stars~4.6k tokensUpdated yesterday
    Auto-check passed
  • 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.

    146 GitHub stars~7.1k tokensUpdated yesterday
    Auto-check passed
  • Frontmcp Config

    agentfront/frontmcp

    A skill your agent uses when configuring a FrontMCP server through frontmcp.config or the @FrontMcp options.

    146 GitHub stars~7k tokensUpdated yesterday
    Auto-check passed

Questions about Frontmcp Guides

What does Frontmcp Guides do?

Tutorials, end-to-end walkthroughs, and complete reference projects for FrontMCP. Frontmcp Guides is an agent skill from agentfront/frontmcp. Tutorials, end-to-end walkthroughs, and complete reference projects for FrontMCP.

When should I use Frontmcp Guides?

Frontmcp Guides fits situations like: you want a getting-started guide; A full worked example; learn best practices by following a step-by-step build rather than a single API reference.

How do I install Frontmcp Guides in Claude Code?

Run `npx skills add agentfront/frontmcp --skill frontmcp-guides -a claude-code`. Or copy the skill folder (libs/skills/catalog/frontmcp-guides in agentfront/frontmcp) into .claude/skills/frontmcp-guides in your project. Claude Code loads it when a task matches its description.

How do I install Frontmcp Guides in Codex?

Run `npx skills add agentfront/frontmcp --skill frontmcp-guides -a codex`. Or copy the skill folder (libs/skills/catalog/frontmcp-guides in agentfront/frontmcp) into .agents/skills/frontmcp-guides in your project. Codex loads it when a task matches its description.

Can I use Frontmcp Guides 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-guides -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-guides, .gemini/skills/frontmcp-guides, .github/skills/frontmcp-guides and .opencode/skills/frontmcp-guides in your project.

What does Frontmcp Guides need to run?

Going by SKILL.md and its folder, Frontmcp Guides needs the command-line tools its instructions call (npm and jest) and credentials named ANTHROPIC_API_KEY. Our summary lists: Node.js.

Does Frontmcp Guides 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 Guides 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 Guides use?

Frontmcp Guides 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 Guides use?

About 6.3k tokens (SKILL.md is roughly 25k 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 11k tokens, read only when the agent opens those files.

What are the alternatives to Frontmcp Guides?

Skills that share tags, products or a category with Frontmcp Guides: Common Tasks (idavidov13/agentic-playwright, 223 stars), MCP Server Patterns (affaan-m/ECC, 275k stars), MCP Server Patterns (majiayu000/claude-skill-registry, 666 stars) and API Testing (fugazi/test-automation-skills-agents, 247 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Frontmcp Guides?

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.