|
| 1 | +--- |
| 2 | +title: Use Insomnia MCP clients to test aggregated MCP tools |
| 3 | +content_type: how_to |
| 4 | +description: Learn how to use Insomnia 12.1 MCP clients to test MCP tools exposed by AI MCP Proxy in listener mode after they have been aggregated from multiple upstream APIs. |
| 5 | + |
| 6 | +products: |
| 7 | + - insomnia |
| 8 | + - ai-gateway |
| 9 | + |
| 10 | +related_resources: |
| 11 | + - text: Aggregate MCP tools from multiple AI MCP Proxy plugins |
| 12 | + url: /mcp/aggregate-mcp-tools/ |
| 13 | + - text: MCP clients in Insomnia |
| 14 | + url: /insomnia/mcp/ |
| 15 | + |
| 16 | +min_version: |
| 17 | + insomnia: "12.0" |
| 18 | + gateway: "3.12" |
| 19 | + |
| 20 | +tags: |
| 21 | + - ai |
| 22 | + - mcp |
| 23 | + |
| 24 | +tools: |
| 25 | + - deck |
| 26 | + |
| 27 | +prereqs: |
| 28 | + inline: |
| 29 | + - title: Aggregated MCP server |
| 30 | + content: | |
| 31 | + Before testing with Insomnia, complete the [Aggregate MCP tools from multiple AI MCP Proxy plugins](/mcp/aggregate-mcp-tools/) guide. |
| 32 | + That guide produces: |
| 33 | +
|
| 34 | + - Multiple conversion-only AI MCP Proxy plugin instances that each expose MCP tools |
| 35 | + - One listener-mode AI MCP Proxy plugin aggregating those tools by tag |
| 36 | + - A public listener endpoint: |
| 37 | + ``` |
| 38 | + http://localhost:8000/mcp-listener |
| 39 | + ``` |
| 40 | + icon_url: /assets/icons/mcp.svg |
| 41 | + |
| 42 | + - title: Network access |
| 43 | + content: | |
| 44 | + Ensure your local machine can reach the listener endpoint produced during aggregation. |
| 45 | +
|
| 46 | + Test connectivity: |
| 47 | + ``` |
| 48 | + curl http://localhost:8000/mcp-listener |
| 49 | + ``` |
| 50 | +tldr: |
| 51 | + q: How do I test aggregated MCP tools using Insomnia? |
| 52 | + a: | |
| 53 | + Connect an Insomnia MCP client to the listener-mode AI MCP Proxy endpoint that the aggregation setup creates. Then test each tool and validate behaviour using Insomnia’s Params, Headers, Events, and Console panels. |
| 54 | +--- |
| 55 | + |
| 56 | +Use Insomnia to connect to an MCP server exposed through the AI MCP Proxy plugin in listener mode. |
| 57 | + |
| 58 | +This listener server aggregates MCP tools from multiple upstream APIs, enabling you to validate end-to-end behaviour using Insomnia’s Params, Headers, Events, and Console panels. |
| 59 | + |
| 60 | +After completing the aggregation workflow described in **[Aggregate MCP tools from multiple AI MCP Proxy plugins](/mcp/aggregate-mcp-tools/)** and exposing an autogenerated or aggregated MCP server, follow this guide to test and validate its MCP tools using Insomnia’s MCP Clients. |
| 61 | + |
| 62 | +## Create an MCP client |
| 63 | + |
| 64 | +1. Open **Insomnia**. |
| 65 | +2. In the sidebar, click **MCP Clients**. |
| 66 | +3. Click **New MCP Client**. |
| 67 | +4. In the **Name** field, enter a name: **Aggregated MCP Tools** |
| 68 | +5. In the **MCP Server URL** field, enter your listener URL: `http://localhost:8000/mcp-listener` |
| 69 | +6. Click **Connect**. |
| 70 | + |
| 71 | +Insomnia connects to the MCP server and discovers all of the aggregated tools. |
| 72 | + |
| 73 | +## Validate tools |
| 74 | + |
| 75 | +1. In the sidebar, locate the **Tools** drop-down section. |
| 76 | +2. Review the list of available tools. |
| 77 | + |
| 78 | +{:.info} |
| 79 | +> If any tools are missing: |
| 80 | +- Confirm that all conversion-only plugins use the same `tags[]` value. |
| 81 | +- Confirm that the listener-mode plugin’s `server.tag` matches that value. |
| 82 | +- Confirm that the listener Route is active and reachable. |
| 83 | + |
| 84 | +## Test tools |
| 85 | + |
| 86 | +Use Insomnia’s testing panels to validate MCP tool behaviour: |
| 87 | + |
| 88 | +1. In **Tools**, click any tool. |
| 89 | +2. In the request pane, click the **Params** tab. |
| 90 | +3. Enter the required parameter value. |
| 91 | +4. Click **Call Tool**. |
| 92 | +5. In the response pane, click the **Console** tab. |
| 93 | + |
| 94 | +A successful response confirms that your aggregated MCP configuration is working correctly. |
0 commit comments