Skip to main content
Glama
janaraj

TNL

by janaraj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to TNL

No user-submitted related servers found.

    Related Servers

    • openai-mcp

      iflow-mcp
      F
      license
      Not graded
      quality
      D
      maintenance
      A versatile MCP server that enables natural language software development tasks using multiple LLM providers (OpenAI, Anthropic) with real-time visualization, cost management, and a comprehensive tool suite.
      -

    • uacos

      caotiensinh
      A
      license
      Not graded
      quality
      B
      maintenance
      Local-first code intelligence and safety layer for AI coding agents. MCP server exposes dependency graph, impact analysis, and AST-compressed repo context, backed by typed local memory, patch-scope safety gates, and git-independent transaction rollback.
      1
      MIT
    • JSON Contracts by json-contracts

      JSON Contractsofficial

      json-contracts
      A
      license
      A
      quality
      C
      maintenance
      JSON Contracts is a local MCP server for transforming natural language into Git-controlled JSON contracts, JSON Schema validation, and structured LLM/agent outputs.
      8
      25 npm
      1
      Apache 2.0

    • claude-bridge-mcp

      millanrp25-dot
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets ChatGPT or any MCP client securely delegate coding tasks to a local Claude Code instance, with git checkpointing, approval gates, and structured results. Supports code review, test running, and rollback via simple tool calls.
      5 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

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: proposal staging, approval, impact analysis, retrieval, tracing, and verification. No overlap.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case, making them predictable and easy to understand.

    Tool Count5/5

    With six tools, the server covers the core workflow for TNL management without being too sparse or overburdened.

    Completeness4/5

    The set covers proposing, approving, retrieving, verifying, and tracing. Missing a list or delete operation, but the core lifecycle is well-represented.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources