Hey @Jourin Enwurk I’ve added support for this locally (will released soon), but I ran into a UX-security dilemma. And I’d love to hear your input.
UX: we can choose between sync the headers across devices, or making it locally only.
If locally only, it can be quite annoying to setup again on other devices.
If sync across devices, I would need to implement e2ee which will take quite a lot of time and effort, also harder to maintain.
Are you ok with option 1 for now?
Jourin Enwurk
•
Apr 27
I am happy with option 1, because I would also think most people that still need HTTP header MCPs are similar to my scenario that their work setups things like the litellm or some kind of gateway for them, or they self-host on some server that is only reachable from local networkI think we have also discussed about end-to-end encryption in another thread, and in the end I installed 2 boltAI in 2 user profiles and only keep my personal profile in sync, and the work one is kept locally on my work laptop based on the security requirement from my work. Anyways, thank you a lot for your help.
Daniel Nguyen
Team•
Apr 24
Hey @Jourin Enwurk. I’ll add support for custom header soon. But most of the first-party MCP servers now support OAuth. You should use it instead of manually setting API Key.
In BoltAI, you can edit the server and change the Auth Type to Oauth, then you can proceed to authenticate with your context7 account (screenshot below)
https://mcp.context7.com/mcp/oauth
Jourin Enwurk
•
Apr 26
Thanks, I agree that most of the modern MCPs use OAuth, unfortunately for me I use a lot of MCPs that was served from my work in the intranet, and they are still using the legacy HTTP header, for authenticating. Without this, I can hardly use this client for my work. Glad to see that this will be addressed in a future release.
Daniel Nguyen
Team•
Apr 26
Understood. I’ll add this soon.
Maximilian Christl
•
Apr 24
Improvemnts on MCP Servers are requested and ignored for Months, unfortunately. Making Bolt AI more and more unusable for productive usage.
Daniel Nguyen
Team•
Apr 24
@Maximilian Christl I understand your frustration and I’m sorry for that. Like I shared in the my other comments, I’ve been working on security and other more critical bugs and wasn’t able to put more focus on MCP integrations. I will focus on that next.
BoltAI has a lot of features and it can be challenging to prioritize. When someone can’t use the app at all because of a bug, or a crash, I would prioritize that more.
With that said, I agree that I haven’t put much attention to MCP integration lately and will fix it soon!
Log in to comment and vote
Comments8
Apr 28
PinnedI’ve added this in v2.11. LMK what you think
Daniel Nguyen
Apr 27
Hey @Jourin Enwurk I’ve added support for this locally (will released soon), but I ran into a UX-security dilemma. And I’d love to hear your input.
UX: we can choose between sync the headers across devices, or making it locally only.
If locally only, it can be quite annoying to setup again on other devices.
If sync across devices, I would need to implement e2ee which will take quite a lot of time and effort, also harder to maintain.
Are you ok with option 1 for now?
Jourin Enwurk
Apr 27
I am happy with option 1, because I would also think most people that still need HTTP header MCPs are similar to my scenario that their work setups things like the litellm or some kind of gateway for them, or they self-host on some server that is only reachable from local networkI think we have also discussed about end-to-end encryption in another thread, and in the end I installed 2 boltAI in 2 user profiles and only keep my personal profile in sync, and the work one is kept locally on my work laptop based on the security requirement from my work. Anyways, thank you a lot for your help.
Daniel Nguyen
Apr 24
Hey @Jourin Enwurk. I’ll add support for custom header soon. But most of the first-party MCP servers now support OAuth. You should use it instead of manually setting API Key.
In BoltAI, you can edit the server and change the Auth Type to Oauth, then you can proceed to authenticate with your context7 account (screenshot below)
https://mcp.context7.com/mcp/oauthJourin Enwurk
Apr 26
Thanks, I agree that most of the modern MCPs use OAuth, unfortunately for me I use a lot of MCPs that was served from my work in the intranet, and they are still using the legacy HTTP header, for authenticating. Without this, I can hardly use this client for my work. Glad to see that this will be addressed in a future release.
Daniel Nguyen
Apr 26
Understood. I’ll add this soon.
Maximilian Christl
Apr 24
Improvemnts on MCP Servers are requested and ignored for Months, unfortunately. Making Bolt AI more and more unusable for productive usage.
Daniel Nguyen
Apr 24
@Maximilian Christl I understand your frustration and I’m sorry for that. Like I shared in the my other comments, I’ve been working on security and other more critical bugs and wasn’t able to put more focus on MCP integrations. I will focus on that next.
BoltAI has a lot of features and it can be challenging to prioritize. When someone can’t use the app at all because of a bug, or a crash, I would prioritize that more.
With that said, I agree that I haven’t put much attention to MCP integration lately and will fix it soon!
https://feedback.boltai.com/p/issues-with-mcp-servers/comment/69eaff1ee977bf8b4de56434