Factory Droid — MCP Configs
- File format
- JSON
- Discovery path
-
.factory/mcp.json - Syllago install method
- JSON merge
- Symlink support
- No
- Config file
-
.factory/mcp.json - Transports
-
stdio,http
Features
How each feature converts to syllago's canonical format. See format conversion for what these statuses mean.
Other features
Behaviors, conventions, and capabilities that aren't tied to a single named field — things like path-based activation, discovery rules, and lifecycle behavior.
| Feature | Conversion | Summary |
|---|---|---|
env_var_expansion | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | stdio server add command accepts --env KEY=VALUE flags; env field documented in configuration schema for stdio servers |
marketplace | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | Quick Start: Add from Registry via /mcp command — 40+ pre-configured servers (Figma, Linear, Sentry, Notion, Supabase, Stripe, Vercel, Playwright, HubSpot, MongoDB) organized into categories |
oauth_support | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | OAuth authentication supported for HTTP servers; tokens stored globally in system keyring rather than per-project; managed via /mcp interactive manager |
tool_filtering | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | per-server tool disable via disabledTools field in Configuration Schema |
transport_types | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | two transports documented: http (remote cloud endpoints, droid mcp add <name> <url> --type http) and stdio (local processes, droid mcp add <name> '<command>' [--env KEY=VALUE...]) |
| Categorized Server Registry | Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more → | Pre-configured servers organized into categories (Development & Testing, Project Management & Documentation, Payments & Commerce, Design & Media, Infrastructure & DevOps) for discovery via Quick Start: Add from Registry in the /mcp manager. |
| Dedicated MCP Configuration Files | Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more → | MCP configurations are stored in dedicated files: ~/.factory/mcp.json (user-level, takes priority) and .factory/mcp.json (project-level, committed to repo). User config wins when both define the same server. OAuth tokens always store globally in the system keyring. |
| Factory as MCP Server | Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more → | The Factory CLI can itself run as an MCP server, exposing its capabilities to other tools that speak the MCP client protocol. |
| Interactive MCP Manager (/mcp) | Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more → | Interactive Manager invoked via /mcp slash command for browsing servers, viewing tools, enabling/disabling connections, authenticating via OAuth, and managing configurations without manual JSON editing. |
| MCP CLI Management Commands | Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more → | Servers are managed via droid mcp add <name> <url> --type http [--header 'KEY: VALUE'...] for HTTP servers and droid mcp add <name> '<command>' [--env KEY=VALUE...] for stdio servers; removed via droid mcp remove <name>. |
Sources
| Source |
|---|
| https://docs.factory.ai/cli/configuration/mcp |