Are tools and toolsets supported when running in http mode? #2191
-
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 9 replies
-
|
This looks like a real boundary issue rather than just a docs misunderstanding. If the server advertises or accepts tools outside the configured allowlist in http mode, then tool scoping is not actually enforceable at the transport boundary, which defeats a big part of the safety story. |
Beta Was this translation helpful? Give feedback.
-
|
Should |
Beta Was this translation helpful? Give feedback.
-
|
@SamMorrowDrums , what do you think about this ⬆️ |
Beta Was this translation helpful? Give feedback.
-
|
Ran it by the team. I expect limiting available tools to a preset max via static config is something that admins will like to specify, and then individual users could still select toolsets etc. within the bounds of what's actually available, so if static configuration allows three toolsets, end users could use headers to access any combination of those three, but no others... Seems reasonable, I will hopefully have gathered thoughts from colleagues soon. |
Beta Was this translation helpful? Give feedback.
-
|
Awesome! Thanks @SamMorrowDrums I hope this can be implemented and released soon. If this becomes an enhancment will a ticket be added to this conversation for tracking? |
Beta Was this translation helpful? Give feedback.
-
|
This was indeed shipped. Closing. |
Beta Was this translation helpful? Give feedback.
-
|
@dahera you need to use the header configuration (mentioned in the remote server documentation). In http mode the server respects configuration per user that connects, not a global configuration for the whole server like STDIO. Add headers like |
Beta Was this translation helpful? Give feedback.
-
|
@SamMorrowDrums the use case I need to support is having a remote http server which allows multiple users connect with their own authorization and utlize tools from a limited predefined set (just like the Atlassian MCP Server) |
Beta Was this translation helpful? Give feedback.
-
|
@dahera your best bet is to use this repo as a library and do that yourself. All the components are there. Alternatively put some http forwarder/reverse proxy in front and force set all the headers that control available tools. I am not saying I'm against the possibility of a constrained http option, but at GitHub we use this repo as library for remote server deployment repo and the works really well for us, and I personally think it's a better pattern for self hosting, especially with customisation. Let me know if you have any success. Can consider constraining remote server at startup also. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
@dahera you need to use the header configuration (mentioned in the remote server documentation). In http mode the server respects configuration per user that connects, not a global configuration for the whole server like STDIO.
Add headers like
x-mcp-toolsetsor add /x/issues to the route. The behaviour should be consistent with the remote server behaviour.