Skip to main content
Glama
758,555 tools. Updated 2026-11-08 02:09

"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
  • Detects undeclared or hallucinated imports, undocumented environment variables, and frontend/backend route mismatches so repository contracts stay consistent.
    Apache 2.0

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    MCP server for multimodal understanding and object grounding (bounding boxes) across images, videos, and documents, with support for multiple AI providers (Zhipu GLM-V, OpenAI GPT-4o, Anthropic Claude, or any OpenAI-compatible endpoint).
    1
    MIT

Matching MCP Connectors

  • 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
  • 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
  • Tail Guaardvark's log files under logs/—backend, Celery, frontend, plugin logs—to diagnose errors and crashes. Credentials are masked automatically.
    MIT
  • [Tauri Apps Only] Monitor Tauri IPC calls between frontend and Rust backend. Requires active driver_session. Captures invoke() calls made through window.__TAURI__.core.
    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
  • 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
  • Generate development tickets by analyzing gaps, required changes, and dependencies from project context, exporting a JSON draft with estimates, labels, and technical checklists.
    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