You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why not replace the authorization field with headers? This makes the test more flexible.
Reacted by Charles Robertson, Cristi Pufu, Adrián Hidalgo, AD, Blackbaud-JamesZhang, Nico Jahn, Danny Roosevelt, Dylan Young, Ray Liu, Dominik Lysiak and 30 more
@pulkitsharma07 I agree with @yuedong111 . Instead of a Bearer Token field, a user should be allowed more flexibility in which headers gets included in the http request.
For example, what if the MCP server is not using a Bearer Token for authentication but is rather using an API Key which requires the Ocp-Apim-Subscription-Key header?
A generic text field (or something similar to Postman) would allow for this flexibility. This design would still allow for Bearer tokens by specifying Authorization: Bearer <token>
+1 on this. It could just be an optional section for additional HTTP headers. The existing bearer token input is easier to use and I think it would be nice if it stayed.
Reacted by Tony Herr, Ola Hungerford, Cristi Pufu, Blackbaud-JamesZhang, Safwan Zullash, anandwilbert, Jedr Blaszyk, Cliff Hall, Bohdan, Dahai Peng and 9 more
what about this? we're converting a lot of restful api to mcp servers via an mcp-gateway service. it'll be helpful if inspector could support custom headers instead of forcing jwt auth. if this sounds broadly useful, i'm happy to submit a pr.
Reacted by Charles Robertson, Ola Hungerford, Cristi Pufu, Luiz Fellipe Machi Pereira, Blackbaud-JamesZhang, Nico Jahn, Dylan Young, Marc Nuri, Jorge Dias Fernandes, Alek Shnayder and 14 more
+1, I need to send more headers in addition to auth like x-tenant-name etc
Reacted by Jorge Dias Fernandes, cardgeny, Diego Asensio Romero de Ávila, Dominik Lysiak, Juan Abia, José Martins, René Larch, Sinisa Milojevic, Dalton Wallace, David Cook and 2 more
@Gabswim I believe these headers are only sent during the connection request. There are MCPs which expects MCP during the tool call as well. Is there a possibility of sending these headers along with each tool call as well?
Activity
pulkitsharma07 commentedon Apr 2, 2025
Can you explain our use case ?
ericlabouve-sn commentedon Apr 8, 2025
@pulkitsharma07 I agree with @yuedong111 . Instead of a Bearer Token field, a user should be allowed more flexibility in which headers gets included in the http request.
For example, what if the MCP server is not using a Bearer Token for authentication but is rather using an API Key which requires the Ocp-Apim-Subscription-Key header?
A generic text field (or something similar to Postman) would allow for this flexibility. This design would still allow for Bearer tokens by specifying
Authorization: Bearer <token>Here is where the Bearer Header is currently being set. We should make this generic so the user can set any arbitrary header.
anthonychu commentedon Apr 10, 2025
+1 on this. It could just be an optional section for additional HTTP headers. The existing bearer token input is easier to use and I think it would be nice if it stayed.
charlesr1971 commentedon Apr 14, 2025
+1 on this. I need to pass three custom headers, that are vital for my application working
iFurySt commentedon Apr 17, 2025
what about this? we're converting a lot of restful api to mcp servers via an mcp-gateway service. it'll be helpful if inspector could support custom headers instead of forcing jwt auth. if this sounds broadly useful, i'm happy to submit a pr.
charlesr1971 commentedon Apr 17, 2025
@iFurySt Yes. This sounds great!😊
cristipufu commentedon Apr 22, 2025
@iFurySt looking forward to your PR 😄
Blackbaud-JamesZhang commentedon May 13, 2025
@iFurySt looking forward to this addition, any update on this? 😁
anandwilbert commentedon May 15, 2025
@iFurySt +1 on this. I will be helpful to have this feature
[-]Inspector should add a header support[/-][+]Support adding arbitrary headers[/+]ashubham commentedon Jun 2, 2025
+1, I need to send more headers in addition to auth like
x-tenant-nameetcSteffanDefinely commentedon Jun 6, 2025
+1
dahaipeng commentedon Jun 13, 2025
+++++1 this would be MORE flexible for developers who wanna suport customized headers to connect to mcp servers; looking forward to your updates!!!
bozhlab commentedon Jun 17, 2025
Need for a custom header to pass some user information when initialize the connection.
14 remaining items
AyatKhraisat commentedon Aug 30, 2025
+1
josephkalayci commentedon Sep 1, 2025
+1
Gabswim commentedon Sep 3, 2025
+1
Gabswim commentedon Sep 3, 2025
Note: While the PR is pending #549, you can test the changes by running:
palash1611 commentedon Sep 4, 2025
@Gabswim I believe these headers are only sent during the connection request. There are MCPs which expects MCP during the tool call as well. Is there a possibility of sending these headers along with each tool call as well?
Gabswim commentedon Sep 4, 2025
@palash1611 Yes, this is what it does from what I tested, because we have that exact use case where we are sending the organization id as a header
daltonwallace commentedon Sep 8, 2025
+1
michaelshewbread commentedon Sep 8, 2025
+1
rishid commentedon Sep 8, 2025
There is a PR here: #751
ryanmadsenn commentedon Sep 9, 2025
+1
craigmwright commentedon Sep 9, 2025
+1
ZacharyBaker commentedon Sep 9, 2025
+1
Devinbeth commentedon Sep 9, 2025
+1
dvalsagna89 commentedon Sep 9, 2025
+1