feature: Add tool management to McpServer instance

[chipgpt]

Motivation and Context

Currently the only way to manage a tool from the server is by having a reference to the tool and using methods like tool.disable(). This adds new methods to the server to manage a tool by name server.disableTool('name').

If we like this idea, I can also do the same for resources, resource templates, and prompts.

How Has This Been Tested?

Tests were added to address the existing tool methods and also the new server methods.

Breaking Changes

No breaking changes.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

[chipgpt]

Thinking about this more, would it make sense to do a more generic method like server.getTool('name')? This way you could enable/disable/remove/update tools without having a reference to the tool.

[chipgpt]

Thinking about this more, would it make sense to do a more generic method like server.getTool('name')? This way you could enable/disable/remove/update tools without having a reference to the tool.

I tried this approach and found myself having to do this a lot:

const tool = server.getTool('name');
if (tool) {
  tool.disable();
}
...
const tool = server.getTool('name');
if (tool) {
  tool.enable();
}

I think it would be much nicer to use server.disableTool('name'), server.enableTool('name'), etc. instead