Context:
The current Firecrawl n8n integration only includes a standard node and does not yet support the Tool Node format. Adding a Tool Node would make Firecrawl directly usable by n8n’s AI Agent system and easier to discover within the platform. Since Firecrawl already supports MCP (https://docs.firecrawl.dev/mcp-server), extending our existing node to also function as a Tool Node would bridge both capabilities and improve the integration experience. Repo: https://github.com/firecrawl/n8n-nodes-firecrawl

Task:

• Implement support for Firecrawl as a Tool Node in n8n
• Ensure the Tool Node works with n8n’s AI Agent system while maintaining current functionality
• Verify that Firecrawl endpoints (scrape, extract, search, etc.) remain accessible and compatible with both normal and tool node configurations

Acceptance Criteria:

• Firecrawl n8n node supports both normal and Tool Node usage
• Tool Node integration works seamlessly with n8n’s AI Agent system
• Code is reviewed and approved by the engineering team

Why it matters:
This will make Firecrawl easier to use for AI Agent workflows, improving discoverability and reducing setup complexity. Users will be able to add Firecrawl as a one-click Tool Node within n8n, similar to other integrations on the platform, without needing to manually configure the MCP connection.

Rules:

• Issues labeled "bounty" with USD amount in title are eligible for rewards
• Multiple contributors may attempt any bounty - highest quality PR that gets merged wins
• Payment sent via PayPal within 5 business days of merge (PayPal account required)
• Once a PR is merged for a bounty, that bounty is closed - no duplicate rewards
• You must fill out this form and sign our CLA to participate

Communication Guidelines:

• To claim you're attempting a bounty: Comment on the issue with "I'm attempting this bounty" - this lets others know you're working on it
• To ask questions: Comment directly on the issue - maintainers will respond there
• To submit your solution: Open a PR referencing the issue number (e.g., "Fixes Unable to run python sdk sample code from README #123 - [bounty title]")
• Progress updates: If you're stuck or need more time, comment on the issue to keep maintainers informed
• Abandoning attempt: If you decide not to continue, please comment "I'm no longer working on this" so others know the bounty is available

Important Notes:

• Claiming an attempt does NOT reserve the bounty exclusively for you - it remains open competition
• Quality matters more than speed - the best solution that meets requirements wins
• Maintainers may provide feedback on PRs - be prepared to make revisions
• Check existing comments before starting to see if others have asked relevant questions
• Together with the PR, send us your PayPal account, otherwise we won’t be able to proceed with the payment.