Connect Builder.io to the Route5 MCP server

Overview⁠

This integration connects Builder.io with Route5 via MCP, allowing users to fetch and interact with their assigned issues directly within the Builder environment. It streamlines workflows by letting users request issue context from Route5 and take action on open issues without switching tools, helping them move faster and stay focused.

How it works⁠

The Builder.io integration with Route5 uses the MCP server framework to connect Builder directly to Route5’s issue management system. Through this connection, Builder can securely access structured data such as open issues, assignments, and statuses within a no-code interface. Once the MCP server is connected, Builder AI agents can query Route5 for key information like open issues or those specifically assigned to the user, bringing that context into any Builder project.

This setup allows users to interact with Route5 data directly from Builder’s Fusion environment. They can ask to see their open issues, request additional context on an issue, or start resolving an issue without switching tools. The MCP server manages authentication and ensures secure access to the data, while Builder AI provides intelligent support within the workspace by tying together task information and development context.

By unifying task data and visual development in one place, the integration helps streamline workflows across teams. Users save time by reducing context switching, speeding up decision-making, and closing issues more efficiently. With scoped and secure access to systems like Route5, teams can focus on building and shipping faster while staying aligned on priorities.

Configure⁠

To configure the Route5 MCP integration in Builder.io, the user must first ensure that Route5 is set up as an active MCP server in their Builder account. This can be done by navigating to the MCP Servers section in the Builder settings and verifying that Route5 appears on the list. If it’s not already enabled, it can be added using the MCP server URL provided by Route5.

The person setting up the integration must have admin permissions in both Builder and the connected Route5 workspace. This is required to authenticate the connection, approve scopes, and allow Builder to access task data securely. Once connected, the system can begin fetching and interacting with structured task data through the Builder UI and AI agent.

No additional coding is required to activate the integration. After setup, users can begin using prompts within Builder’s Fusion environment to query ticket data, request context, and resolve issues directly. It’s recommended to test the integration with a specific Builder project to confirm that the correct Route5 issues are being returned and that access is scoped as expected.