MCP Agent Toolkit
Related Servers
Alternatives to MCP Agent Toolkit
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables secure, stateful AI agents and LLM tools to access enterprise databases, knowledge bases, live system metrics, and sandboxed code execution through the Model Context Protocol, with authentication, rate limiting, and safety guards.-
- AlicenseBqualityDmaintenanceA security-focused Model Context Protocol server that enables controlled local tool execution through strict network firewalls, filesystem protections, and rate-limiting policies. It features a plugin-based architecture for progressive tool discovery and includes reference implementations for web searching and bug tracking.15MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to access multiple upstream Model Context Protocol servers through a single endpoint with API-key authentication, scoped access, rate limiting, guardrails, and audit logging. Tools are namespaced by upstream so clients can discover and call them via one tools/list and tools/call surface.46 npmMIT
- FlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that advertises tools with JSON schemas and executes tool calls safely, enabling AI agents to perform actions on real systems.-
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to discover and invoke enterprise tools like web search, document parsing, meeting scheduling, and email through a unified Model Context Protocol server that aggregates and routes across multiple backends.1-
- AlicenseNot gradedqualityCmaintenanceExposes database and external API tools via the Model Context Protocol, enabling LLMs to query SQLite and call public APIs with validated inputs and error handling.MIT
TDQS
Scored across 4 tools
Each tool targets a clearly different resource and action: web retrieval, SQL query, file read, file write. There is no plausible way to confuse web_search with db_query or read_file with write_file.
Two tools follow noun_action (web_search, db_query) while two follow verb_noun (read_file, write_file), so the set splits evenly between conventions. Names are still readable and unambiguous, but the pattern is not uniform.
Four tools is slightly thin for a general 'agent toolkit', but each one covers a distinct capability (external search, structured data, file I/O) with no redundancy. Nothing feels padded or missing at the count level.
File read/write, web search, and read-only DB query cover the core loop of gather-and-persist, and the read-only DB constraint is explicit rather than an oversight. Minor gaps remain: no way to list workspace files or discover paths, and no append/delete file operations, so agents must guess file names.