Skip to content

Specify transport type on startup #255

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
aaronpowell opened this issue Apr 3, 2025 · 4 comments
Open

Specify transport type on startup #255

aaronpowell opened this issue Apr 3, 2025 · 4 comments
Labels
enhancement New feature or request waiting on submitter Waiting for the submitter to provide more info

Comments

@aaronpowell
Copy link

Is your feature request related to a problem? Please describe.
When you first run the inspector it defaults to stdio as the transport, unless previously specified. So if you run: npx -y @modelcontextprotocol/inspector http://localhost:1234/sse it will default to stdio and upon changing the dropdown, set it to the default of http:''localhost:3001/sse, removing your default value.

Describe the solution you'd like
When running inspector you should be able to specify the transport type to use, or it should be inferred from the server provided (eg: if it's http(s) prefixed, using SSE, otherwise use stdio).

Describe alternatives you've considered
I can't find any way in the code that this can be set.

Additional context
N/A

@aaronpowell aaronpowell added the enhancement New feature or request label Apr 3, 2025
@cliffhall
Copy link
Contributor

When running inspector you should be able to specify the transport type to use, or it should be inferred from the server provided (eg: if it's http(s) prefixed, using SSE, otherwise use stdio).

Hey @aaronpowell. This seems reasonable. Would you like to add a PR?

@cliffhall cliffhall added the waiting on submitter Waiting for the submitter to provide more info label Apr 4, 2025
@aaronpowell
Copy link
Author

I think there would be a level of intersection with #258 - maybe when the config endpoint is called it does some processing of the argument to send back that will determine the transport type, rather than having to add another arg to the CLI

@cliffhall
Copy link
Contributor

Could we not rectify the situation in the client app, so that if you have supplied an http(s) url it switches the type to SSE?

@aaronpowell
Copy link
Author

Since the client app gets its info on what to put in the transport drop down + input fields by calling the /config endpoint on the server, it'd make sense for the server (proxy) to provide that initial info, and then you can change it as desired.

Like I suggested, expanding on the solution in #258

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request waiting on submitter Waiting for the submitter to provide more info
Projects
None yet
Development

No branches or pull requests

2 participants