Allow specifying which MCP tools are available to custom droids

[fahimanwer]

Feature Request

Currently, custom droids (defined in .factory/droids/) cannot specify which MCP tools they should have access to. This limits the ability to create specialized droids that leverage specific MCP capabilities.

Proposed Solution

Add a tools or mcp_tools field to the droid configuration schema that allows specifying:

1. Which MCP servers the droid can access
2. Which specific tools from those servers are available
3. Optionally, tool aliases or restrictions

Example Configuration

name: product-researcher
description: Researches products using Amazon and Oxylabs
model: claude-sonnet

# Proposed new field
mcp_tools:
  - server: oxylabs
    tools: ["scrape_url", "search_google"]
  - server: amazon-paapi
    tools: ["search_items", "get_items"]

Or alternatively:

allowed_mcp_servers:
  - oxylabs
  - amazon-paapi

Use Case

When building content factories or specialized agents, different droids need different tool access:

• A research droid needs web scraping tools
• A product hunter needs Amazon API tools
• A content creator might not need any MCP tools

This would enable better separation of concerns and more predictable droid behavior.

Current Workaround

None - droids either have access to all MCP tools or the tools available depend on what's loaded in the session, which is unpredictable.

[factory-sam]

Hello @fahimanwer ! This is possible today, and can be configured using the /droids slash command. If you go to 'advanced' tool settings you'll be able to see all tools for connected MCPs.