ForgePilot MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXA_API_KEY | No | API key for Exa live research. Optional; the app starts without it in demo mode. | |
| OPENROUTER_API_KEY | No | API key for OpenRouter model-backed chat. Optional; the app starts without it in demo mode. | |
| FORGEPILOT_MCP_TOKEN | No | Token required for non-loopback HTTP server mode (remote MCP). Not required for the default loopback/local stdio mode. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| forgepilot_healthB | Return the local ForgePilot runtime status. Read-only. |
| forgepilot_searchB | Search the web with Exa and return compact, untrusted highlights with source URLs. |
| forgepilot_chatC | Answer an integration question using optional Exa evidence through OpenRouter. Read-only. |
| forgepilot_generate_configB | Generate portable MCP client configuration snippets. Read-only. |
| forgepilot_create_artifactB | Create a timestamped, read-only integration run bundle with evidence, response, report, and SHA-256 manifest. |
| forgepilot_start_device_flowC | Create a consent-scoped Aitherium device-flow handoff for local inference, MCP, workspace, and LAN capabilities. No token is returned. |
| forgepilot_local_acceleration_planB | Inspect local aw* command/package presence and return the Bonsai model activation plan for Codex and Claude Code. Read-only. |
| forgepilot_create_shareable_packC | Scaffold a portable MCP + WebMCP + PWA agent tool pack with awnboard/awiam/awbac/awdit metadata. |
| forgepilot_create_connector_artifactB | Generate runnable Claude Code and Codex MCP configs plus bootstrap scripts for the current local checkout. |
| forgepilot_backend_switch_planB | Show the safe adk/awsettings plan for switching Claude Code to a provider such as DeepSeek Flash. Read-only. |
| forgepilot_community_bridge_planB | Show the safe ARC, awgym, awrelay, Relay, Forums, Spaces, and AwDesk connection plan. Read-only. |
| forgepilot_create_community_bridge_packC | Create a no-secrets community bridge artifact for ARC, awgym, awrelay, Relay, Spaces, and AwDesk. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Several tools generate configs or artifacts (generate_config, create_connector_artifact, create_artifact, create_shareable_pack, create_community_bridge_pack) with overlapping 'create' verbs, and chat/search both use Exa, so misselection is possible despite descriptive text.
All tools use the forgepilot_ snake_case prefix, but four tools are noun-phrase plans (local_acceleration_plan, backend_switch_plan, community_bridge_plan) while the rest use verb or verb_noun patterns, a minor deviation.
12 tools is well within the ideal 3-15 range and each tool maps to a distinct ForgePilot integration task (health, search, config, artifacts, plans), so the count is appropriate.
The surface covers many one-way generation/planning tasks but lacks lifecycle operations: no list, get, update, or delete for artifacts/packs, and device flow has only a start tool with no completion/poll tool.