agentic-mcp-server
Related Servers
Alternatives to agentic-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides a production-ready Model Context Protocol server with dual STDIO and Streamable HTTP transports, enabling file operations, memory, database queries, RAG, web search, GitHub integration, background tasks, and prompt-based workflows.MIT
- AlicenseNot gradedqualityCmaintenanceEnables creating minimal Model Context Protocol servers with tools, resources, and prompts over stdio or streamable HTTP using only Python's standard library.MIT
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that standardizes tool discovery, execution, and context management for AI applications.MIT
- FlicenseNot gradedqualityBmaintenanceModel Context Protocol server for MCPGRAM that enables MCP clients to interact with connectors like GitHub, Slack, and Notion through stdio or Streamable HTTP transports.-
- AlicenseNot gradedqualityDmaintenanceA minimal, general-purpose implementation of the Model Context Protocol (MCP) for Node.js and Bare runtime, enabling creation of AI-interactive servers with tools, resources, and multiple transport options.5 npm2MIT
- FlicenseNot gradedqualityAmaintenanceA minimal Model Context Protocol server exposing arithmetic, time, and note-taking tools over streamable HTTP, with in-memory state and Docker support.-
TDQS
Scored across 4 tools
Each tool targets a distinct operation: search returns matches, get retrieves a full document by slug, add creates a new document, and sys.time provides system time. There is no overlap in purpose or return type.
The knowledge base tools follow a consistent kb.<verb> pattern (search, get, add), and the system tool uses sys.time. Prefix-based namespaces make the convention predictable and easy to reason about.
Four tools is a compact but reasonable set for a focused knowledge base server with a system utility. It is not overly thin, though a couple more operations could strengthen the scope.
The surface covers search, retrieval, and creation of knowledge base documents, but lacks update, delete, and list-all operations. This leaves notable CRUD gaps that agents cannot work around directly.