Skip to main content
Glama
AlicanAkyol

Nativekeel

by AlicanAkyol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Nativekeel

No user-submitted related servers found.

    Related Servers

    • store-review-check

      Rocketech-Software-Development
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding assistants to scan an iOS, Android, Flutter, React Native or Expo project for App Store and Google Play rejection risks, returning deterministic findings that cite the guideline section, link to the official Apple or Google page and explain how to fix each problem. Nothing leaves the machine and no AI is used in the checks.
      MIT

    • rn-devtools-mcp

      Ehab-Aqili
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to inspect React Native app performance including memory, rendering, frames, and network requests, providing plain-language summaries and shareable reports.
      2 npm
      MIT

    • ReleaseGuard Deploy Check

      NEK-Studios
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables running deterministic package.json checks for Next.js, Expo, and Convex projects via a read-only stdio tool, returning JSON findings usable by CI and coding agents.
      -

    • Expo MCP Server

      Rukafuu
      F
      license
      Not graded
      quality
      C
      maintenance
      A secure local MCP server that allows AI assistants to inspect and diagnose Expo-based React Native projects, offering read-only tools for project summary, doctor checks, dependency validation, and public config retrieval.
      2
      -
    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

    A4/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools target distinct activities (library lookup, error explanation, bundle measurement, change verification), and the descriptions are unusually detailed. However, scan_project and security_audit both surface security findings, and improve_app and upgrade_plan both transform scan findings into a prioritized plan, so the boundaries between those pairs are somewhat blurry.

    Naming Consistency5/5

    All eight tools use consistent snake_case with a verb_noun pattern (check_library, explain_error, measure_bundle, scan_project, upgrade_plan, verify_upgrade). Only security_audit is a noun phrase rather than verb_noun, a trivial deviation that remains perfectly readable.

    Tool Count5/5

    Eight tools is well within the ideal 3-15 range and each maps to a recognizable part of the React Native/Expo project-health workflow. No tool feels redundant filler or conspicuously absent.

    Completeness4/5

    The surface covers the main lifecycle: library compatibility, error diagnosis, project scanning, security review, bundle analysis, upgrade planning, and change verification. The intentionally read-only design means no apply/fix tool exists, which is a minor gap agents can work around by following the returned plans.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources