Skip to main content
Glama
gorillanobakaa-dot

Fieldkit

by gorillanobakaa-dot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Fieldkit

No user-submitted related servers found.

    Related Servers

    • Strata Coder

      huyinghuan
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables a primary coding agent to delegate bounded implementation and repair tasks to a local OpenAI-compatible model that edits a copy of the project, runs configured checks, and returns artifacts for review. Exposes stdio tools for capability discovery, task submission, progress polling, artifact reading, and cancellation.
      MIT

    • collab-charter

      LucasDevKid9
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes 14 tools that let an agent query charter clauses, route and execute an 8-stage collaboration pipeline, arbitrate conflicts with cited clause IDs, enforce safety gates, run receipt self-checks, deposit and recall memory, solve symbolic anchoring constraints, and mine a 330-entry knowledge base plus semantic-field analysis. It also diagnoses image-generation prompts against a formal feature-cluster grammar, all over a zero-dependency stdio JSON-RPC interface.
      1
      MIT

    • a0

      Joe-Simo
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to open, edit, check, run, emit, and save source programs through structured, revision-checked tools over stdio, confining paths to the launch root and returning diagnostics with fixes for rejected edits.
      4 npm
      1
      Apache 2.0

    • Enlace

      Caelos-Palacio
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes four stdio tools that let an agent research an application's documented interface, produce a validated single-use plan, and execute read-only operations against public HTTP JSON APIs, static HTML/JSON/text sources, and host-configured CLIs. Runs in-process with no listening port, accounts, or model dependency, returning bounded results while keeping inputs and outputs inside a host-enforced research-plan-execute lifecycle.
      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/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: run/discover/describe/undo handle tool execution and inspection, while build_harness_* tools cover the build workflow. The main overlap is between 'next' for pipelines and 'build_harness_next' for the build harness, but the descriptions make their scopes separable.

    Naming Consistency3/5

    Naming is mixed: four tools share a clear 'build_harness_' prefix, but the rest are bare verbs or nouns ('run', 'discover', 'describe', 'undo', 'next', 'readiness'). There is no single verb_noun convention across the set, though the names remain readable.

    Tool Count5/5

    Ten tools is well-scoped for a build-harness and tool-running server. Each tool covers a distinct area of the workflow, with no obvious redundancy or thin surface.

    Completeness4/5

    The surface covers core lifecycle actions: inspecting tool readiness, discovering/describing/running tools, undoing changes, and managing build harness status, next steps, submissions, and briefs. A minor gap is that the agent cannot record brief answers by design, leaving that action to a human terminal.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources