MCP Servers
Wingman supports Model Context Protocol (MCP) servers via stdio or sse transports.
Global MCP config
Per-agent MCP config
Transport types
- stdio: spawn a local subprocess and communicate over stdio.
- sse: connect to a remote HTTP/SSE endpoint.
Keep MCP servers scoped to the minimum data and permissions required for each agent.
Resource discovery tools
When an agent has MCP configured, Wingman also injects two MCP resource helper tools:
mcp_list_resources: list resources for all configured MCP servers (optionally include templates)mcp_read_resource: read a specific resource URI from a specific MCP server
These tools are additive and do not change the behavior of existing MCP tool calls (including FAL and finance servers).
Finnhub finance MCP server
Use the bundled finance MCP server to power market-data agents (like stock-trader) with quotes, candles, fundamentals, news, and option chains.
1) Provide a Finnhub API key
The finance MCP server requires FINNHUB_API_KEY. You can set it globally in your shell or inline per server config.
2) Register the server (stdio example)
If you are working from the Wingman repo directly, the server file is located at:
3) Enable MCP for your agent
Set mcpUseGlobal: true in agent.json/agent.md or add a per-agent mcp block.
Optional environment variables
Use these to fine-tune rate limits and candle data behavior:
The finance MCP tools are intended for research and education only. They do not provide financial advice or execute trades.
FAL AI MCP server
Use the bundled FAL AI MCP server for queue-backed multimodal generation (image, image edit, audio/music, and video from image).
1) Provide a FAL API key
Set FAL_API_KEY (or FAL_KEY) in your shell or inline in the MCP server config.
2) Register the server (stdio example)
If you are working from the Wingman repo directly, the server file is located at:
3) Use it from agents
generate_image_or_texturegenerate_image_editgenerate_audio_or_musicgenerate_video_from_imagefal_generation_status
Default local paths:
If FAL_MCP_REVIEW_MODE=hil, completed jobs are staged under <workdir>/.wingman/fal-ai/pending/<jobId>/ until fal_generation_status is called with action=accept or action=deny.
Assistant message images are also materialized to disk from session history under:
