Skip to main content
Glama
satwikjambula

Forms26 MCP

by satwikjambula
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Forms26 MCP

No user-submitted related servers found.

    Related Servers

    • Oracle Forms MCP

      aoreshkov
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to inspect and query Oracle Forms modules (blocks, triggers, program units, etc.) without Forms Builder, supporting reverse engineering, code review, and modernization.
      8
      Apache 2.0

    • Oracle APEX MCP Server

      silviosotelo
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables integration with Oracle Database and Oracle APEX 20.2, allowing LLMs to execute SQL/PL/SQL, manage database objects, and inspect APEX application metadata. It supports full database CRUD operations, object dependency analysis, and detailed page-level inspection of APEX environments.
      3
      MIT

    • mcp-migration-tools

      simeptk
      A
      license
      A
      quality
      D
      maintenance
      Provides AI-callable tools for modernizing legacy applications, including stack detection, API contract extraction, SQL to Flyway conversion, and migration effort estimation.
      4
      MIT

    • MigrateSafe MCP

      johannschiffer
      A
      license
      B
      quality
      C
      maintenance
      Enables AI coding assistants to analyze DDL migration scripts before execution, flagging table-locking, destructive, and backward-incompatible changes, estimating lock duration and risk, and inspecting schema diffs through MCP tools.
      4
      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.3/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct migration-analysis step: listing forms, analyzing metadata, listing components, reading source, assessing risks, planning APEX mapping, drafting API artifacts, and inspecting DB objects. Overlap between analyze_form and migration_risks is limited because one summarizes complexity while the other surfaces specific risk evidence. An agent can select the right tool from the descriptions.

    Naming Consistency4/5

    Most names follow a clear verb_noun snake_case pattern, e.g. list_forms, analyze_form, get_source, plan_apex, draft_api. The main deviation is migration_risks, which is a noun phrase rather than an action phrase, but it remains readable and consistent in casing.

    Tool Count5/5

    Eight tools is a well-scoped set for an Oracle Forms analysis and migration-planning server. Each tool covers a distinct phase of discovery, inspection, risk assessment, or drafting, with no obvious filler tools.

    Completeness4/5

    The surface covers the main analysis workflow: discovering forms, inspecting components and source, assessing risks, planning APEX mappings, drafting API artifacts, and checking DB objects. The main limitation is that it intentionally stops at drafts and does not create APEX exports or execute SQL, but that appears to be a deliberate scope boundary rather than an accidental gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources