Skip to main content
Glama
Touseef-ahmad

nestjs-langgraph-mcp

by Touseef-ahmad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to nestjs-langgraph-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Coding Agents

      kadreio
      A
      license
      Not graded
      quality
      D
      maintenance
      A transport-agnostic MCP server that integrates multiple AI coding agents (Claude Code, Gemini, and Codex) with built-in tools for command execution, calculations, and streaming capabilities. Supports both STDIO and HTTP transports for flexible deployment.
      2 npm
      1
      MIT

    • MCP-TS-DEMO

      pjqdyd
      A
      license
      D
      quality
      D
      maintenance
      A TypeScript MCP server demo supporting local Stdio and remote Streamable HTTP, demonstrating tool invocation for AI agents.
      2
      MIT

    • MCP Server App

      ovokpus
      F
      license
      B
      quality
      D
      maintenance
      An MCP server with LangGraph agent integration that enables AI agents to use custom tools and external APIs for dice rolling, web search, social content creation, and GitHub access via STDIO transport.
      10
      3
      -

    • mcp-coding

      cdemeo92
      A
      license
      Not graded
      quality
      D
      maintenance
      Experimental MCP server for local LLM orchestration with filesystem tools (read, write, list, delete files) and a CLI agent that communicates via Ollama.
      2 npm
      ISC

    • nestjs-mcp-controller

      jaenster
      A
      license
      Not graded
      quality
      D
      maintenance
      Build MCP servers inside NestJS applications using ordinary controllers with decorators for tools, resources, and prompts, supporting authentication and authorization.
      40 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 4 tools

    Disambiguation3/5

    Health and list_agents are clear, but main_agent and run_agent overlap: both execute agents, with main_agent claiming to handle any request and run_agent offering provider/model selection. This could cause confusion about which to use.

    Naming Consistency2/5

    Tool names mix conventions: 'health' is a noun, 'list_agents' and 'run_agent' are verb_noun, 'main_agent' is adjective_noun. Verbs are not consistently used, leading to an incoherent pattern.

    Tool Count3/5

    With only 4 tools, the server feels thin for the advertised capabilities (employee data, analytics, reporting, approval). The count is borderline but not extremely low for an agent-centric design.

    Completeness2/5

    The server lists numerous capabilities (e.g., list employees, engagement scores) but lacks dedicated tools for them—all are funneled through main_agent. This creates a gap where agents cannot directly perform specific operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources