Skip to main content
Glama
nerdit-ai

Nerdit

Official
by nerdit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Nerdit

No user-submitted related servers found.

    Related Servers

    • agent-deploy-dashbaord

      aparajithn
      A
      license
      Not graded
      quality
      D
      maintenance
      Unified deployment dashboard MCP server for AI agents. 9 tools to manage services across Vercel, Render, Railway, and Fly.io — deploy status, logs, service listing, environment variables, rollback, and health checks from one endpoint. Free tier: 50 requests/IP/day.
      3
      MIT

    • Aaly

      candysiva
      A
      license
      Not graded
      quality
      C
      maintenance
      A remote MCP server that lets a coding agent turn a plain-language idea into a real, shareable product — creating the project and data model, serving live API endpoints, deploying custom endpoints and server-side functions, and reading request and function logs. It handles sign-up, OAuth-backed access, and OpenAPI spec generation so people can open, sign into, and use the app the agent builds.
      MIT

    • awesome-coolify-mcp

      clezcoding
      A
      license
      A
      quality
      A
      maintenance
      One MCP server to manage self-hosted Coolify instances: verify connectivity, discover servers, deploy applications, tail logs, diagnose incidents, and run emergency ops from any MCP client.
      19
      42 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 67 tools

    Disambiguation3/5

    The descriptions work hard to separate tools ('Distinct from deploy...', 'Use this instead of deploy_git when...'), but six deploy-family verbs (deploy, deploy_git, deploy_app, deploy_template, redeploy_service, apply_project) plus paired log/diagnose tools (service_logs vs project_logs, diagnose_service vs diagnose_project) force an agent to read a paragraph to pick correctly. Resource-oriented lists (list_services/list_models/list_databases/list_projects) are cleanly distinct, but the parallel project-scoped vs service-scoped duplicates create real hesitation.

    Naming Consistency3/5

    The dominant pattern is snake_case verb_noun, but it breaks in several places: bare verbs/nouns (deploy, serve, doctor, capabilities), noun-first reads (service_logs, project_logs, system_disk, system_gc), and mismatched creation/deletion verbs across similar entities (create_database vs add_domain vs add_hook; remove_service vs delete_project). Still readable, but not a predictable grammar.

    Tool Count2/5

    67 tools for a single-node PaaS is far past a well-scoped surface; several families (four deploy verbs, four config tools, three file tools, paired project/service variants) exist largely to model the same operations at different scopes. The result is a heavy, hard-to-navigate set where an agent can miss the right tool even though each one is documented.

    Completeness4/5

    Coverage of the domain is genuinely broad: deploys from folder/git/template/workspace, full service lifecycle, models, managed databases with dumps, projects, secrets/variables, AI routing, domains, hooks, config, audit, events, and system/health. Minor gaps are deliberate and documented (no restore tool, no volume-backup tool), though some of the breadth is bloat rather than coverage.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources