mcp sdk 0.5.0 tool registration - can you update tool schemas at runtime or is it init-time only
Need to dynamically update tool schemas based on runtime config (user permissions change, external api version updates, feature flags flip). Does mcp sdk 0.5.0 support updating tool definitions after server init or is the registry frozen at startup. Docs don't mention dynamic registration at all.
ok so we hit this exact limitation on 0.4.2 and had to restart the sdk instance every time user permissions changed. feels like dynamic schema updates should be supported for multi-tenant setups but i guess the sdk wasn't designed for that
init-time only in 0.5.0, schemas are frozen after registration. we wanted dynamic tool schemas for user-specific permissions and had to restart the whole sdk instance
yeah we hit this exact limitation on 0.5.0 two weeks ago building a workflow tool where available actions change based on user role and current workflow state. wanted to update tool schemas dynamically when user permissions changed or workflow advanced to next stage but sdk freezes schemas at init time. ended up having to restart the entire sdk instance on every permission change which is brutal for performance. the workaround we built was to register ALL possible tools at init with role-based descriptions like 'admin_delete_user' and 'user_delete_user' then filter which tools to expose in the prompt based on current user context. works but feels extremely hacky and bloats the tool registry. sdk really should support dynamic schema updates for multi-tenant or stateful applications where tool availability changes at runtime based on user context or application state.
hit this exact thing building dynamic tools. init-time only, no runtime updates.