Skip to main content
Glama
Sign In
openhoat

aik-mcp

by openhoat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to aik-mcp

No user-submitted related servers found.

    Related Servers

    • knowledge-rag-mcp

      TTANF1
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to connect local knowledge bases, preview and index selected directories, search for traceable snippets with source metadata, and read indexed document versions through MCP tools.
      6
      MIT

    • Wiki MCP

      Dreamernosleep
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create, read, update, delete, search, and explore linked Markdown pages in a self-hosted knowledge base through MCP tools.
      14 npm
      MIT

    • mcp-wiki-server

      AustinAbhari
      F
      license
      A
      quality
      C
      maintenance
      Enables MCP-compatible clients to search and read local markdown documentation, allowing agents to retrieve relevant doc snippets or full files by path.
      2
      -

    • synapse

      anshulyadav1976
      A
      license
      A
      quality
      A
      maintenance
      Provides AI agents with a local, private Markdown-based memory vault and SQLite search. Enables agents to search, read, list, and traverse linked knowledge pages via MCP with zero external runtime dependencies.
      7
      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

    B3.3/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools map to a clean resource+action boundary: content items (list/get/search/write/delete), assets (get_asset), and installation lifecycle (install/list_installed/uninstall/check_updates). The main friction is the reinstall vs update pair — both claim to bring an installed item to the latest version from the knowledge base — and list vs list_installed, which differ only by scope (all content vs project-installed). Descriptions do resolve these, but an agent can plausibly misselect reinstall when update is intended.

    Naming Consistency3/5

    Two conventions coexist: bare verbs for core content operations (list, get, search, write, delete) and verb_noun for the derived operations (get_asset, list_installed, uninstall_all, check_updates). Both are snake_case and readable, but the bare-verb group is inconsistent with the compound group and omits the object noun (get what?). 'layout' is also an outlier — a noun-like name in a set of action verbs.

    Tool Count4/5

    14 tools is well within the well-scoped band for a content knowledge base plus installer, and each tool has a defensible job. There is mild redundancy — uninstall_all is a convenience wrapper over uninstall, and reinstall overlaps update — but nothing that bloats the surface unreasonably.

    Completeness4/5

    Content items have full coverage (list/get/search/write/delete, with write handling update), and the install lifecycle is thorough (install, reinstall, update, check_updates, list_installed, uninstall, uninstall_all, layout). Gaps: assets are read-only (get_asset with no write/delete counterpart), and install/uninstall are scoped only to the 'current project' even though layout documents both project and global scopes, so global installs appear unsupported.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources