Use the MCP Inspector
The MCP Inspector, available through the Model Context Protocol (MCP)
For more information about the MCP Inspector, see the MCP Inspector documentation
To connect your gateway to the inspector
-
Open a terminal and run
npx @modelcontextprotocol/inspectorto do the following:-
Install the inspector
-
Start the inspector on localhost.
-
Generate a session token for authentication.
-
Open your browser to the inspector interfacee.
-
-
In the inspector interface, configure the following fields:
-
Transport Type – Select Streamable HTTP
-
URL – Enter the gateway endpoint URL returned when you created your gateway.
-
Expand Authentication. The Custom Headers section should be pre-populated with one key-value pair.
-
The key's name should be
Authorization. -
Replace the value with your gateway's inbound authorization credentials.
-
-
-
Choose Connect. You will be connected to your gateway. You can use the MCP Inspector as a tool to examine and test your gateway before integrating it with your agent.
For more information about how you can inspect the MCP server that your gateway is connected to, see Feature overview in the Feature overview
Important
The MCP Inspector is a development tool and should not be used in production environments. Always secure your access tokens and gateway credentials.
Troubleshooting
If you encounter issues when using the MCP Inspector with your gateway, check the following:
-
Connection issues: Ensure that your gateway URL is correct and accessible from your network
-
Authentication issues: Verify that your access token is valid and has not expired
-
Tool invocation errors: Check the error messages in the response and ensure that your input parameters match the tool's schema
-
Proxy errors: If you see errors related to the proxy connection, try restarting the MCP Inspector
