Your progress is only saved in this browser. to protect it and pick up on any device.

Connect a Postman API key to check your work

You do each step in Postman, then LiftOff uses your key to look at your workspace and confirm it's done. Connect once and it works for every module. Your key is saved in this browser and is only used to check your work in Postman.

0 of 4 steps0%

With the model and Fraud API now routed through Fabric, connect the Banking and Support MCP servers. You will add and test each service independently, expose both through one MCP route, and then replace the agent's large initial catalogue of 104 tools with a governed Tool Search experience. Tool Search exposes three discovery tools that progressively disclose and execute the Banking and Support tools the agent actually needs.

The upstream MCP servers are already deployed. You do not need to build or run them locally.

1

Connect and Test Banking MCP

Create the Banking MCP connection, credential, and route

  1. In Fabric's sidebar, click MCP servers. Confirm that Connections is selected, then click Create connection.

    The updated MCP servers page showing the Connections tab and Create connection action

  2. On Create MCP connection, leave Provider set to Custom server.

  3. Under Connection, enter:

    • Connection name: banking-mcp

    • Target URL:

      https://intergalacticbanking-mcp-production.up.railway.app/mcp
    • Access: Open

  4. Under Upstream auth, configure the shared credential that Fabric will send to the Banking MCP server:

    • Auth type: API key

    • Header: x-api-key

    • Credential: Shared

    • API key:

      banking-mcp-demo-key
  5. Turn on Create gateway route, then configure the route:

    • Route name: banking-mcp-route
    • Path: confirm that the generated URL ends in /mcp/banking-mcp
    • Gateway auth: No gateway auth

    No gateway auth keeps this workshop route public, so callers do not need to send a gateway credential.

    The updated Create MCP connection screen configured with the Banking MCP target, shared upstream API key, and gateway route

  6. Click Create connection. Fabric creates the MCP connection and route together, and stores the upstream API key in its managed vault.

Test the Banking route

  1. Open MCP servers → Routes. From the banking-mcp-route route, copy its complete DP URL, including /mcp/banking-mcp.
  2. In Postman, select the Fabric Gateway environment, set bankingMCPBaseUrl to the copied URL, and save the environment.
  3. Open the forked MCP collection, select Banking API MCP, and connect to the server. Under Tools, select 1. List owned accounts, then select Run.
  4. Confirm that the tool call succeeds and returns the customer's owned accounts. Because the route uses No gateway auth, the request does not require X-Gateway-Key.

The Banking API MCP connected in Postman with the List owned accounts tool and a successful account response

Expected outcome: Banking MCP works through its public /mcp/banking-mcp Fabric route, while its upstream API key remains stored in Fabric's vault.

Validation: Enter the complete public Banking MCP DP URL below. LiftOff opens a real MCP session through Fabric and runs the read-only List owned accounts tool. No gateway key is required.
2

Connect and Test Support MCP

This follows the same connection → public route → vaulted credential → Postman test workflow you completed for Banking MCP. Repeat those steps using the Support-specific values below.

SettingSupport MCP value
Connection namesupport-mcp
Upstream authToggle on; Bearer; Org/tenant
Route namesupport-mcp
Route path/support
Route servicesupport-mcp
Gateway authNo gateway auth
Credential typeService credential
Credential display nameSupport MCP Key
Postman variablesupportMCPBaseUrl

Target URL

https://intergalacticsupport-mcp-production.up.railway.app/mcp

Credential token

support-mcp-demo-key
  1. Under Gateway → MCP servers, create the support-mcp resource with the target URL and Bearer requirement above, then select Add Resource.
  2. Under MCP servers → Routes, expose that service at /support with No gateway auth, then select Create route.
  3. Under Administration → Credentials, create the Support service credential using the credential token above. Fabric stores this upstream token in its managed vault.
  4. Copy the route's full DP URL, including /support, into supportMCPBaseUrl in Postman's Fabric Gateway environment.
  5. Open MCP → Support API MCP, connect to the server, and run Search support cases.
  6. Confirm that the search succeeds through Fabric and returns support-case results. Because this route is public, the request does not require X-Gateway-Key.

The Support API MCP connected in Postman with Search support cases selected and a successful structured response

Expected outcome: Support MCP works through its public /support Fabric route, and its upstream credential is held in Fabric's vault.

Validation: Enter the complete public Support MCP DP URL below. LiftOff opens a real MCP session through Fabric and runs the read-only Search support cases tool. No gateway key is required.
3

Expose Both MCP Servers Through One Route

The support agent should not need to manage separate Banking and Support MCP connections. Fabric can expose both services through one client-facing MCP route.

  1. In Fabric's sidebar, click MCP servers. Click the Routes tab, then click Create route.
  2. Configure the combined route:
    • Name: banking-support-mcp
    • Protocol: confirm that Fabric sets this to MCP
    • Connections: select both banking-mcp and support-mcp; the field should show 2 connections selected
    • Path: /mcp/all
    • Require gateway auth: leave this unchecked
  3. Click Create route. Leaving Require gateway auth unchecked makes the combined route public, so callers do not need a gateway credential.

The updated Create route screen configured with both MCP connections, the combined path, and no gateway authentication

  1. Open the combined route's ellipsis menu and select Copy DP URL. Keep the complete URL, including /mcp/all.

  2. In Postman's Fabric Gateway environment, confirm that allMCPBaseUrl contains this URL and save the environment.

  3. In the cloned support-agent project's .env, paste the same URL as FABRIC_MCP_URL:

    FABRIC_MCP_URL=YOUR_COMBINED_MCP_DP_URL
  4. In Postman's MCP collection, open Banking Support MCP ALL and start a new session.

  5. Send List all tools. Before Tool Search is enabled, the route should expose tools from both upstream services—50 Banking tools and 53 Support tools.

Note: Because this route combines multiple MCP services, Fabric namespaces each tool to show where it came from and avoid name collisions. The tool name begins with a prefix derived from its source route, followed by two underscores and the original tool name: <route-prefix>__<tool_name>. For example, the screenshot below shows dbs__support_list_cases.
  1. Select any tool you would like to try, provide its required inputs, and run it. Confirm that the tool returns a successful response through the combined route.

Run any Banking or Support tool through the Banking Support MCP ALL request

  1. Return to the terminal for the cloned support-agent project. Stop the development server if it is still running, then restart it so it loads your latest .env values:

    npm run dev
  2. Open http://127.0.0.1:4173, choose any supplied query, and select Run comparison.

  3. Compare the initial tool count for both lanes. At this point, Direct and Fabric Gateway should each show 104 tools: 50 Banking tools, 53 Support tools, and one Fraud function.

The combined Fabric route is working, but it still sends the same large tool catalogue to the model as the Direct route. That consumes unnecessary context on every model turn. In the next step, you will improve this by enabling Tool Search.

Expected outcome: One Fabric MCP URL exposes all 103 Banking and Support tools and can successfully call either upstream service. The local comparison runs through both lanes, with each initially exposing 104 tools.

If you are stuck: Start a new MCP session after changing a route or environment value. MCP clients cache their initialized session and tool catalogue.

Validation: Enter the complete combined MCP DP URL below. LiftOff confirms that the route exposes all 103 Banking and Support tools, then invokes a read-only Banking tool through the combined route. No gateway key is required.