Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OPENAI_API_KEYNoYour OpenAI API key, required if using --provider openai (also set MCPFORGE_ENABLE_OPENAI_PROVIDER=1).
ANTHROPIC_API_KEYYesYour Anthropic API key for generation (required for generate, update, plan).
MCPFORGE_WORKSPACENoAbsolute path to the workspace directory for generated servers. If not set, defaults to current directory.
OPENROUTER_API_KEYNoYour OpenRouter API key, required if using --provider openrouter.
MCPFORGE_ENABLE_OPENAI_PROVIDERNoSet to '1' to enable the direct OpenAI provider (used with OPENAI_API_KEY).

Instructions

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.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
generateB

Generate a complete FastMCP 3.x server from a plain-English description.

Returns a dict with keys: path, plan (dict), valid (bool), tests_run (int).

updateB

Apply a natural-language modification request to an existing MCP server.

Returns a dict with keys: path, valid (bool), tests_run (int).

validateB

Validate an existing MCP server. Returns detailed validation results.

planA

Extract the structured server plan without generating code.

Returns a dict with keys: name, slug, description, tools (list), transport.

inspectC

Inspect a generated server without executing it.

doctorB

Check local mcpforge prerequisites and provider readiness.

list_generated_serversB

List generated mcpforge servers in a workspace.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 7 tools

Disambiguation4/5

Most tools target distinct actions: generate, update, validate, plan, inspect, doctor, and list are generally clear. However, plan and generate overlap somewhat since generate also produces a plan, and inspect vs. validate could be confused without closer reading.

Naming Consistency4/5

Tool names are mostly simple imperative verbs like generate, update, validate, and inspect, which creates a readable pattern. The one outlier is list_generated_servers, but it is still understandable and not disruptive.

Tool Count5/5

Seven tools is well within the ideal range for a code-generation focused server. Each tool contributes a meaningful step in the workflow without unnecessary redundancy.

Completeness4/5

The toolset covers the core creation, update, validation, and inspection lifecycle for generated servers. The main gap is the lack of a delete or remove tool for cleaning up generated servers.

Maintenance

ActivityActive
ResponsivenessNo issues