Schema | mcp-forge

mcp-forge

Describes the environment variables required to run the server.

Name	Required	Description	Default
`NODE_ENV`	No	Environment	development
`LOG_LEVEL`	No	pino log level	info
`PROMPTS_DIR`	No	Override the prompts directory location	.claude/commands (relative to binary)

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
list_stepsA	List all rewrite steps (0–14) in order. Optionally filter by projectType to see which steps apply or are skipped.
get_stepA	Get the full prompt content for a specific step (0–14). For step 8 (Entrypoint Layer), you must provide projectType.
get_entrypointB	Get the entrypoint-specific instructions (Step 8) for a given project type (http-api, library, cli, worker, mcp-server).
get_master_promptA	Get the complete master prompt for single-pass rewrites of small projects (< 2000 lines). Handles all project types automatically.
validate_manifestA	Validate an AUDIT_MANIFEST JSON string against the expected schema (produced by Step 0). Returns a list of validation errors, or confirms the manifest is valid.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Flagler-County-BoCC/mcp-forge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server