Skip to main content
Glama
597,057 tools. Updated 2026-09-21 12:34

"Understanding Frontend and Backend Development" matching MCP tools:

  • Combine a static frontend and HTTP service backend from any generators into one fullstack repo with a deployment contract and docker-compose.
    MIT
  • Retrieve the dependency graph mapping frontend routes to backend API routes. Specify a route to filter or omit for the full graph.
    Apache 2.0
  • Create TypeScript clients for frontend applications to interact with backend API endpoints, simplifying API integration and type-safe communication.
    MIT
  • Provides a development reference for Flarum 2.0 extensions, covering scaffolding, architecture, backend, frontend, scaling, testing, and porting. Consult it when building or reviewing extension code.
    MIT

Matching MCP Servers

Matching MCP Connectors

  • Cloudflare Workers MCP server: form-backend

  • Deterministic pre-trade risk checks for autonomous AI trading agents.

  • Generate a ready-made prompt describing your app's backend, ready to paste into frontend generators like v0, Bolt, or Lovable. Scaffold a frontend directly from your backend.
    MIT
  • Detect missing fields and desynchronized enums between Prisma schema, backend DTOs, and frontend types. Run after schema or DTO changes to maintain coherence.
    MIT
  • Generate a Mermaid or Graphviz diagram for a code graph slice to visualize component hierarchy or frontend-to-backend flow.
    MIT
  • Apply a proposed fix to resolve a specific backend issue without modifying frontend files.
    MIT
  • Retrieve the overall architecture of a LaunchFrame project, including services, backend modules, key patterns, frontend structure, and infrastructure details.
    MIT
  • Monitor Tauri IPC calls between frontend and Rust backend. Start or stop capturing invoke() calls and responses to debug communication in Tauri applications.
    MIT
  • Analyze frontend API calls and backend routes to detect mismatches, dead endpoints, and phantom calls before deployment.
    MIT
  • Analyzes the project structure to identify test frameworks, backend/frontend, and environment, then provides hints for generating tests.
    MIT
  • Audit backend code, database queries, network waterfalls, and frontend rendering to identify performance bottlenecks, N+1 queries, IDOR security risks, and slow pagination.
    MIT
  • Identify performance bottlenecks, N+1 queries, IDOR vulnerabilities, and slow pagination in backend code, database queries, network, and frontend rendering to optimize system performance.
    MIT
  • Trace the full chain from frontend component or route to backend handler function. Accepts component names, routes, or endpoint paths to map frontend elements to their backend counterparts.
    MIT
  • Suggest or finalize a tech stack (frontend, backend, database, hosting) with rationale, based on project scope and user experience level.
    MIT
  • Retrieve Akın Coşkun's technology stack. Optionally filter by category such as frontend, backend, database, or DevOps.
    MIT