chore: improve ability to use custom tools MCP-295

[gagik]

We already had a toolConstructors parameter which could have already been used for this. So, instead this improves the experience by

1. Renaming toolConstructors option to tools. This makes more sense in constuctor context.
2. Exporting tool-related classes through a mongodb-mcp-server/tools namespace and adding documentation

[Copilot]

Pull Request Overview

This PR improves the developer experience for using custom tools in the MongoDB MCP server by exposing tool-related classes through a new mongodb-mcp-server/tools export namespace. The change adds documentation and renames the parameter from toolConstructors to tools for better clarity.

Key Changes:

• Exported tool classes and types through a new mongodb-mcp-server/tools namespace
• Renamed toolConstructors parameter to tools in ServerOptions for better clarity
• Added comprehensive integration tests demonstrating custom tool usage

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
tests/integration/customTools.test.ts	New integration test demonstrating custom tool registration and execution
tests/integration/build.test.ts	Added verification that CommonJS and ESM exports match for the new tools module
src/transports/base.ts	Updated to accept tools parameter and pass it through to server
src/tools/index.ts	New entry point exporting all tool classes, types, and collections
src/server.ts	Renamed toolConstructors to tools with improved documentation
src/lib.ts	Added exports for StdioRunner, TransportRunnerBase, and Elicitation
package.json	Added ./tools export path supporting both CommonJS and ESM

[coveralls]

Pull Request Test Coverage Report for Build 19431611919

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 11 of 14 (78.57%) changed or added relevant lines in 4 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.4%) to 80.556%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/lib.ts	0	3	0.0%

Files with Coverage Reduction	New Missed Lines	%
src/lib.ts	1	0.0%

Totals
Change from base Build 19375045765:	0.4%
Covered Lines:	6548
Relevant Lines:	8012

---

💛 - Coveralls