mcp-loader
Related Servers
Alternatives to mcp-loader
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceEnables building MCP servers in TypeScript where tool schemas, descriptions, and validation are automatically generated from class methods, their TypeScript types, and JSDoc comments at compile time.1-
- FlicenseNot gradedqualityDmaintenanceAggregates tools from multiple MCP servers, generates TypeScript definitions, and executes custom TypeScript scripts to orchestrate cross-server tool calls.-
- FlicenseNot gradedqualityCmaintenanceProvides a TypeScript scaffolding that auto-loads drop-in tools, resources, and prompts, and serves them to MCP-compatible clients over stdio or streamable HTTP.-
- AlicenseNot gradedqualityDmaintenanceA hot-reloadable MCP proxy server that enables users to create and manage custom Python tools through dynamic module loading. Users can build their own utilities, wrap APIs, and extend functionality by simply adding Python files to designated folders.7Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables building and running an MCP server with automatically discovered tools, prompts, and resources over HTTP or STDIO, using TypeScript and Zod schemas.-
- FlicenseNot gradedqualityBmaintenanceEnables users to extend its toolset by adding Python scripts under a configurable tools path, with recursive discovery and MCP tool exposure. Supports separate commands to load scripts and start the server.-
TDQS
Scored across 16 tools
Several tools overlap in purpose, especially the generic verification tools 'test', 'demo', 'test_hotReloadTest', and 'test_liveTest', which an agent could easily confuse. The context/system information tools also blur together: 'system', 'session_info', and 'context-test_contextInfo' all report similar environment/context details.
Tool naming is mixed: math_, session_, and test_ prefixes are used, but there are bare names like 'demo', 'system', and 'test' alongside hyphens and camelCase in 'context-test_contextInfo' and 'test_hotReloadTest'. The overall pattern is readable but inconsistent.
At 16 tools, the set is borderline heavy for what appears to be a loader/test utility server. Many of the test/demo/verification tools could likely be consolidated without losing functionality.
The set covers math, session, context, echo, time, and reload-testing scenarios, but it feels like a grab bag rather than a complete domain surface. Notable gaps include no math subtraction, no negative/error-case testing tools, and redundant generic test tools that do not clearly advance the loader-testing purpose.