Skip to main content
Glama
Sign In
nimbus

nimbus

by nimbus-agent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to nimbus

No user-submitted related servers found.

    Related Servers

    • mcp-me

      paladini
      A
      license
      A
      quality
      C
      maintenance
      Digital identity layer for AI — your bio, career, skills, interests, and projects always available to every AI tool. Auto-generates profile from 342+ public APIs, 13 real-time plugins, YAML-based profiles with privacy-first local storage.
      2
      124 npm
      21
      MIT

    • memroam

      apurv101
      A
      license
      Not graded
      quality
      B
      maintenance
      Portable AI memory that roams with you across models and harnesses — one shared memory for Claude Code, Codex, Cursor, Gemini CLI and more, stored as plain markdown files you own. Per-project spaces plus a shared layer, vault-wide search; runs locally over stdio/HTTP or hosted with OAuth 2.1 backed by your own GitHub repo.
      33 npm
      MIT

    • infernoflow

      ronmiz
      A
      license
      B
      quality
      B
      maintenance
      Git-native memory for coding agents, so every session starts warm. Gotchas, decisions, dead ends and bookmarks are saved as plain JSONL in your repo; Claude Code, Cursor and Copilot read them, and teammates get them through git.
      9
      1,052 npm
      8
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.8/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct primary purpose: general search, connector status, recent PRs, deployments, DORA metrics, and incidents. There is some conceptual overlap between searchIndex and the getRecent* helpers, but the descriptions clarify ranked search vs. time-ordered lists.

    Naming Consistency4/5

    Tools consistently use camelCase with a 'get' prefix for most queries, and the getRecent* grouping is a strong pattern. The one deviation is searchIndex, which lacks a 'get' prefix but still follows a readable verb_noun structure.

    Tool Count5/5

    Six tools is well within the ideal 3-15 range for a focused read-only data access server. Each tool covers a distinct, useful capability without bloat.

    Completeness4/5

    The surface covers the core read operations for the index: search, connector health, recent item lists, and DORA metrics. Minor gaps like item detail retrieval or additional item types are mitigated by the generic searchIndex tool, which can access any indexed entity.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled

    Resources