Skip to main content
Glama
Sanjit-K

FTC Toolchain

by Sanjit-K
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to FTC Toolchain

No user-submitted related servers found.

    Related Servers

    • ftc-mcp

      jackulau
      A
      license
      A
      quality
      D
      maintenance
      MCP server that injects verified FTC documentation and code examples into AI assistants, enabling teams to write correct, competition-ready Java robot code through natural language.
      3
      6 npm
      2
      MIT

    • mcdev-mcp

      use-ai-for-mc
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that empowers AI coding agents to work effectively with Minecraft mod development, providing static analysis of decompiled source code and runtime interaction with a running Minecraft instance.
      31
      25 npm
      16
      MIT

    • Agentic Terminal

      mohamedmahmoud8801
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that gives AI agents terminal execution, Python scripting, file management, and code search tools so they can carry out real development tasks. It exposes bash, Python, glob, grep, and file/folder operations over MCP for coding assistants and codebase exploration.
      1
      MIT

    • mcp-stm32cubeide-server

      Helistana
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets AI coding agents drive the full STM32 development loop—code generation, build, flash, debug, serial monitoring, and fault diagnosis—end to end via CubeIDE, CubeMX, CubeProgrammer, OpenOCD, and GDB.
      1
      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

    A3.8/5.0

    Scored across 35 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, from ADB operations to project scaffolding, building, deployment, and documentation. Overlapping areas like deployment are handled by separate tools with specific workflows (e.g., build_and_deploy vs. wifi_deploy_start), avoiding ambiguity.

    Naming Consistency5/5

    All tool names consistently use snake_case with a verb_noun pattern (e.g., create_opmode, list_subsystems, deploy_robot). There are no mixed conventions or vague verbs, making the naming predictable and easy to navigate.

    Tool Count2/5

    35 tools is excessive for the typical MCP server scope, far exceeding the recommended 3-15 range. While many tools are specialized for FTC development, the count is high enough to overwhelm an agent, indicating poor scoping.

    Completeness4/5

    The tool surface covers the full FTC development lifecycle: setup, coding, building, deployment, debugging, and documentation. Minor gaps exist, such as lack of dedicated tools for sensor configuration or simulation, but core workflows are well-supported.

    Resources