Skip to main content
Glama
821,890 tools. Updated 2026-11-22 19:45

"Laravel" matching MCP tools:

  • Authoritative 'what fired and when' stream — wraps the `alert_history` table (one row per incident, both legacy and modern) and `alert_outlet_log` (per-dispatch ledger keyed by history_id). Default mode: lists incidents newest-first. Each row is one incident with opened_at / last_event_at / resolved_at framing the lifecycle, plus aggregated outlet_types[], dispatch_count, and failed_count. `status` is computed from resolved_at: 'open' if null, 'resolved' otherwise. Drill-down mode: pass `incident_id` (the `alert_history.id`, NOT `alert_id`) to switch the call to /api/alert-history/{id}/log and return the per-outlet dispatch ledger for that one incident. Use this for 'did the email actually go' / 'what did the webhook payload look like' / 'which outlets failed' follow-ups. Filters (default mode, all client-side, AND-combined): status (open|resolved|all, default all), severity (int or array — scheme is 1-5, lower=worse), device_id, source (legacy|modern|all), hours (1-168, default 24, applied against last_event_at), search (substring on alert_label/subject). Important caps: the upstream endpoint returns at most 500 rows ordered by last_event_at DESC. We can't reach older rows than that. `meta.upstream_cap` reports this so the LLM can warn the user when results may be truncated. `severity_label` is added server-side so the LLM doesn't memorize the scale. Pagination is over the post-filter result. Tag-scope is enforced by Laravel — tag-restricted users see only incidents for devices in their slug set. Permission: alerts. Examples: alerts_history({status: 'open', severity: [1,2], hours: 1}) alerts_history({device_id: 42, hours: 24}) alerts_history({incident_id: 9182}) // dispatch ledger
    ConnectorNo auth
  • Recent WAN speedtest results — answers 'is the internet healthy?'. Wraps GET /api/getSpeedTestHistory. Returns rows ordered by timestamp desc. Each row carries the upstream's SpeedtestLog shape — typically {id, timestamp, download_mbps, upload_mbps, latency_ms, jitter_ms, server, ...}, but any new columns added on the Laravel side flow through automatically. The tool doesn't reshape the row contents — just filters by time window and limits the return. Lower priority than ping/traceroute/netflow for general 'internet slow' investigations, but the right tool when the user specifically asks about WAN throughput trends or recent speedtest runs. Filters (client-side): hours (1-720, default 168 = 7d), limit (1-100, default 25). The upstream endpoint returns the full history with no server-side cap — narrow with hours rather than fetching unbounded. Permission: tools. Example: speedtest_history({hours: 24})
    ConnectorNo auth
  • Open an interactive ER diagram of a database schema on erddocs.com. Use it when the user wants to see, understand, review or document their database structure, or asks for an ER diagram. Pass the schema text exactly as it is in the project. It reads SQL dumps and DDL (PostgreSQL, MySQL, SQL Server, SQLite), Prisma schema.prisma, DBML, Mermaid erDiagram, PlantUML, Django models.py, SQLAlchemy models, Sequelize models, TypeORM entities and a folder of Laravel migrations (concatenate the files). For SQL, the structure is enough: no INSERT data. Returns a link. The user opens it in a browser and gets the diagram with every table and relation laid out, relations without declared foreign keys found by column name and drawn dashed, and a data dictionary. Nothing is stored on the server: the schema travels inside the link and is parsed in the user's browser. A link holds a schema of a few dozen tables (about 100–200 characters of link per table, depending on comments); for a larger one the tool says so and the user pastes it on erddocs.com instead.
    ConnectorNo auth
  • Tells whether a language, runtime, framework, database or operating-system version is still supported and when it reaches end of life. Covers about 480 products (Python, Node.js, PHP, Java, Ruby, Go, Rust, Django, Laravel, Rails, React, Angular, PostgreSQL, MySQL, Ubuntu, Debian, Kubernetes and more). With product and version it returns that version's status (supported / security_only / end_of_life / upcoming), its release, active-support and end-of-life dates, days remaining or elapsed, and the cycles that are still supported; with only product it returns every release cycle; with neither it lists the product identifiers. Read-only and requires no authentication. Status is computed on every call from today's date; the dates come from endoflife.date and are refreshed every 12 hours. Use it before choosing a runtime or base image, when writing a Dockerfile or CI matrix, or when auditing an old version. It concerns the language, runtime or platform itself; for a library's own versions use package_status.
    ConnectorNo auth
  • Run a site's own command line tool as the site's owner, in the site's folder: bin/console for Shopware 6 and PrestaShop, artisan for Laravel, drush for Drupal, cli/joomla.php for Joomla, ghost (ghost-cli) for Ghost (list_sites shows each site's console; Magento 2 has the magento tool and WordPress the wp tool). Pass the command and its options as args, like ["cache:clear"] or ["plugin:list", "--json"]. For a site in a Docker container it runs inside the container. Listing and status commands run straight away; uninstalling or deleting, anything that drops or resets the database, generating new keys, an admin login link and commands that run arbitrary PHP (tinker, php:eval) need approval. Symfony's console and artisan are run with --no-interaction; drush asks nothing only when you pass -y. Set background true for slow commands.
    Connector
    Destructive
    OAuth
  • List all registered websites and mobile apps in the workspace with active subscriber counts, current credit balance, and optional framework SDK installation snippets (when include_sdk_framework is set). Use this tool first as a prerequisite to obtain a valid app_id before calling send_push_notification, schedule_push_notification, update_app_branding, delete_app, configure_inapp_banner, or configure_rss_autopush; do not use it to inspect individual subscriber devices (use list_subscribers instead). Read-only operation requiring PUSHNOTIF_API_KEY with 0 credit cost; when include_sdk_framework is passed ('html', 'nextjs', 'laravel', 'wordpress', 'flutter'), each app entry also includes ready-to-paste SDK setup code. Returns JSON { tenant_name, credits_balance, total_apps, apps: [{ id, site_name, site_url, active_subscribers, sdk_guide }] }.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI assistants to inspect a Laravel project's database schema, Eloquent models, routes, logs, migrations, and app info, plus run SELECT-only SQL, without exposing secrets or writing data.
    MIT

Matching MCP Connectors

  • Manage Laravel Forge servers, sites, and deployments from your AI assistant.

  • Let your AI assistant build a runnable Symfony 8, Laravel 13 or plain PHP 8.5 project and hand you a shareable link. The code runs in the browser with WebAssembly: no install, no account, nothing stored server-side (the code travels inside the link). Tools: get_starter (starting project, editable paths, Composer packages), create_sandbox (builds the link), read_sandbox (reads the code behind a link). Great for demos, answering questions with runnable code, or turning a bug from your project into

  • Legt für das Hostingpaket (hauptdomain = die Domain des Pakets) eine Subdomain oder eine Weiterleitung von einer Domain bei einem anderen Anbieter an. Drei Arten (art): "alias" = Weiterleitung einer Domain, die der Kunde bei einem ANDEREN Anbieter registriert hat (z. B. IONOS oder Strato): sie leitet dauerhaft (301) auf die Hauptdomain des Pakets weiter; das SSL-Zertifikat wird nach dem Anlegen ausgestellt, sobald alle autoritativen Nameserver der jeweiligen Domain den Namen liefern (bei einer Subdomain die der Hauptdomain, bei einem Alias die der Domain selbst, nicht die des Pakets). Meldet die Antwort zertifikat_folgt (oder nicht ausdrücklich, dass das Zertifikat ausgestellt ist), ist es noch nicht da: es wird automatisch nachgeholt (Wiederholung alle paar Minuten bis 48 Stunden nach dem Anlegen), und aktion "pruefen" auf den angelegten Namen stellt auch ein noch offenes Zertifikat aus (im Panel: Knopf "Zertifikat ausstellen"; das gilt auch für Subdomains). Die Weiterleitung wird erst aktiviert, wenn die A-/AAAA-Einträge für @ und www auf den Server des Pakets zeigen: bis dahin ist der Zustand "wartet_dns", und die Antwort nennt die Einträge, die der Kunde beim DNS-Anbieter setzen muss (und AAAA-Einträge, die er entfernen muss). Es gibt keinen Hintergrundjob für wartende Domains: Hat der Kunde das DNS geändert, muss mit aktion "pruefen" erneut aufgerufen werden, erst dann wird die Weiterleitung angelegt und das Zertifikat ausgestellt. Wartende Domains verfallen nach 30 Tagen (der Eintrag wird entfernt, die Domain lässt sich danach neu hinzufügen); "pruefen" verlängert die Frist nicht. Zeigt die neue Domain richtig, ein anderer Alias des Pakets aber nicht, nennt die Antwort diesen Alias: der Zustand bleibt "wartet_dns", bis der Kunde ihn in Ordnung bringt oder entfernt. "sub_website" = Subdomain mit eigener Website: ihre Dateien liegen im Ordner <fqdn> neben httpdocs (der Ordner heißt immer wie die Subdomain und lässt sich nicht frei wählen); bis zum Hochladen steht dort eine Platzhalterseite, der Zugriff läuft über FTP/SFTP/SSH des Hauptzugangs. Nur wenn die App einen eigenen Ordner ausliefert (z. B. public bei Laravel/Symfony oder dist bei Vite), gibt es den optionalen Parameter unterordner (relativ unter <fqdn>, z. B. public); aktion "pfad" ändert ihn später (der alte Ordner bleibt bestehen). Das Zertifikat der Subdomain folgt automatisch, sobald sie überall im DNS angekommen ist (meist innerhalb von 15 Minuten). "sub_weiterleitung" = Subdomain, die per 301 auf eine URL (ziel) weiterleitet. Domains, die dem Kunden bei turbopress gehören, legt dieses Werkzeug nicht an: für sie gibt es im Panel unter "Weiterleitungen" → "Weiterleitung anlegen" den Weg "Eine deiner turbopress-Domains" (im Chat: redirect_domain; Domains ohne eigenes Paket werden dabei dem Paket zugeordnet); die Hauptdomain eines anderen Pakets desselben Kunden wird mit dz_eigenes_paket abgelehnt; Domains anderer werden abgelehnt. Im Panel-Chat braucht jeder Aufruf den Bestätigungsklick des Kunden (dann wurde noch nichts ausgeführt). Höchstens 10 Hinzufügungen pro Tag. Die Antwort (Zustand, DNS-Einträge, Zugang) wörtlich weitergeben; nur dann Erfolg melden, wenn sie ihn meldet. Entfernen: remove_added_domain.
    ConnectorOAuth
  • List configured alert definitions across both axes of the rule engine. Modern alerts (table `alerts`, class-scoped: syslog_log / event_log / eve_log / device_down / storage) and legacy alerts (per-device tracker thresholds, surfaced via the `_hell` view) are fetched, normalized, merged, filtered, and paginated. Wraps GET /api/alerts (modern) and POST /api/getAlerts (legacy). Both endpoints return their full catalog; this tool applies the filters and pagination client-side, so the LLM doesn't need to know which axis a filter applies to. Output rows carry a `source` discriminator and a synthetic `id` string (e.g. "modern:42" / "legacy:17") so dedup is unambiguous; the original numeric id is on `raw_id`. Modern rows carry `class`, `severity`, and last-evaluated stats. Legacy rows carry `type` (tracker kind), `device_id`, and `tracker_name`. Modern rows carry NO throttle / renotify fields, on purpose: since 21.93 no modern class consults them (log-stream classes are one-fire and edge-triggered per event key; device_down and storage are stateful and diff open incidents), so they explain nothing about when a modern alert re-fires. Do not claim a modern alert is flap-damped or on a renotify timer — it isn't. Legacy trackers DO still renotify on a timer, but that config lives on the trigger and is not returned here either. `last_result_count` is NOT the same measure across classes. For syslog_log / event_log / eve_log it is the raw match count from the last evaluation BEFORE edge-trigger dedup — a steady nonzero means the pattern keeps matching, NOT that anything was notified (repeat matches of an already-seen occurrence are suppressed). For device_down it is a level: devices currently down and in scope, so nonzero means an outage is open right now. For storage it is likewise a level: volumes currently low (or held open because their reading is unreadable/stale) and in scope. Never sum or compare the two. `last_evaluated_at` is the last scheduler tick that touched the alert; legacy rows have no equivalent. For what actually fired and was delivered, use alerts_history. Filters (all optional, AND-combined): scope (modern|legacy|all, default all), class (modern only — silently ignored on legacy rows), severity (int or array), enabled (bool), device_id (legacy only — modern alerts are class-wide), search (case-insensitive substring on label). Pagination: per_page defaults to 50 (max 200), page is 1-indexed. `meta.total` is the post-filter count; `meta.has_more` flags more pages. tag-scoped server-side at the legacy axis (legacy rows for devices outside the user's slug set are filtered by Laravel before this tool sees them). Permission: alerts. Example: alerts_list({severity: 1, enabled: true, search: "router", per_page: 20})
    ConnectorNo auth
  • Generates framework-aware code fixes (Laravel Blade, Next.js App/Pages Router, HTML, PHP, Astro, Svelte) for missing titles, meta descriptions, canonical URLs, JSON-LD schemas, and WebMCP discovery links with unified diff preview. USAGE GUIDELINES: - Use after audit tools detect specific SEO, schema, or WebMCP issues in a source file. - Do NOT use for general code refactoring unrelated to metadata, schema, or SEO tags. - Always run 'seo_validate_code_fix' immediately after applying changes to verify syntax and prevent duplicate tags. BEHAVIORAL TRANSPARENCY: - Non-destructive by default: Returns unified diff preview without modifying files. - Modifies disk ONLY when 'applyDirectly' is explicitly set to true.
    ConnectorNo auth
  • Returns what happened in software after a given date, so an agent can patch the gap between its training data and today: packages among the most popular on npm, PyPI, crates.io and Packagist that shipped a NEW MAJOR VERSION after the date (with the version that existed at that date, the new majors and their first release dates, the latest version, and an upgrade-guide link when one exists), runtimes, frameworks and platforms released or ended since (Python, Node.js, PHP, Java, Django, Laravel, Ubuntu, PostgreSQL and about 35 more), runtimes ending within 180 days, and AI models released since by the main providers with their prices. Read-only and requires no authentication. Results are computed from registry publication dates and cached for an hour. Coverage is the most popular packages (not every package), 0.x-to-0.y changes and calendar-versioned packages are not reported as major versions, and deprecations that happened before Vigia started tracking are not listed. Use it once at the start of a coding session, passing the month your training data ends, or when you suspect a library you know has changed a lot. To dig into one package use upgrade_impact (npm) or package_status; for one runtime use eol_status.
    ConnectorNo auth
  • Read one current English manual page for a PHP symbol or a WordPress function, hook, or class. Returns the official page URL, the version line, the signature, the description, and the first official example. php.net pages are the live English HTML manual. WordPress pages are the live developer.wordpress.org reference. This is not an archive of older manuals and it does not search Laravel, Symfony, or Markdown docs. The first 5 successful pages each UTC day from one network address are free and need no API key. A not_found or fetch_failed does not use a free page. After the 5, send header X-API-Key. A key call costs 0.04 credit only when a page is returned. Pass the symbol, for example str_contains or wp_insert_post. Set source to php or wordpress, or omit it and a wp_ name uses WordPress. Set version, for example 8.3 or 6.7, to learn whether that release is covered by the page version line. version_applies is null when version is omitted or the page has no version line. User comments are not included. Key: https://firm.bestsmartgoods.com/signup
    ConnectorNo auth
  • List tag definitions. The slug is the stable identifier used everywhere device-tag scoping is enforced (e.g. alert_routing_rules.tag_filters, device_list({tag: ...})). The display name is for humans. Wraps GET /api/tags. Returns every tag the caller has visibility to (Laravel does not tag-restrict the catalog itself — operators see all tags and use the slugs that match their visible devices). Tag rows are typically O(10s) per install. Optional `type` filter: 'device' tags decorate devices and are the most common (these are what device_list({tag: ...}) matches against). 'status' tags are reserved for system-derived states. 'other' is a catch-all. Default 'all' returns every type. Permission: devices. Example flow: a user says 'check our routers' → call tags_list({type: 'device', search: 'router'}) → pick a slug → call device_list({tag: 'router', status: 'down'}).
    ConnectorNo auth
  • Read a log by name for a time window, with repeated messages counted once: how many different errors there are, how often each happened, when first and last, a sample of each (with the top of its stack trace) and the latest lines. Suited to finding what went wrong in a long log. log is one of: web-error (nginx and Apache error logs, each site's own included), php (PHP and PHP-FPM, and error_log files next to the code), site (the site's own application log, whatever kind it is: Shopware and PrestaShop var/log, Laravel storage/logs, Joomla and OpenCart logs), magento (exception.log and system.log of the site, plus how many error pages visitors saw), wordpress (wp-content/debug.log), database (MySQL/MariaDB error log), system (warnings and errors in the journal), mail, auth (logins). Or give path for any other log file. match keeps only entries holding that text. Log lines can hold personal data such as addresses and order references: report the pattern and the counts, not the personal data itself.
    ConnectorOAuth
  • Get everything needed to install an Aura UI component or block into a Laravel project: the `php artisan aura:add` command, the resolved transitive dependency tree, the file list, and (optionally) the Blade source of each file. Call this when you are ready to install a component you found via list/search/get.
    ConnectorNo auth
  • Resolve an HTTP route by path + optional method to endpoint + handler (filePath + line bounds). Use instead of grep/locate for URL paths: follows framework router metadata (Express, Fastify, Hono, Laravel, FastAPI, etc.) and resolves dynamic segments, prefix groups, and middleware-mounted routers text search misses.
    ConnectorNo auth
  • Discovers website architecture, detected web frameworks (Laravel Blade, Next.js App/Pages Router, Nuxt, Astro, PHP, static HTML), routing structure, existing sitemap/robots configurations, and page inventory. USAGE GUIDELINES: - Use when starting an audit of a local codebase to detect framework patterns and file routes. - Do NOT use for remote websites or live URLs; use 'seo_crawl_and_extract' or 'seo_audit_sitemap_multipage' instead. BEHAVIORAL TRANSPARENCY: - Safe, read-only local filesystem scan. Makes no network calls and modifies no files.
    ConnectorNo auth
  • Read one of Sendora's documents whole, as Markdown: a guide (sendora://docs/…), an API operation (sendora://reference/…), the error codes (sendora://errors) or an SDK's README and rules for agents (sendora://sdk/readme and sendora://sdk/skill for TypeScript, sendora://sdk/python/readme and sendora://sdk/python/skill for Python, sendora://sdk/php/readme and sendora://sdk/php/skill for PHP, sendora://sdk/laravel/readme for Laravel, and sendora://sdk/java/readme and sendora://sdk/java/skill for Java). sendora://index lists every document; search_docs finds the right one.
    ConnectorNo auth
  • Combine .gitignore templates (based on github/gitignore) for languages, frameworks, tools, editors and operating systems into one deduplicated file, optionally test paths against it. Template ids: node, python, django, jupyter, java, maven, gradle, kotlin, android, go, rust, ruby, rails, php, laravel, dotnet, c, cpp, swift, flutter, elixir, scala, r, nextjs, terraform, unity, docker, secrets, vscode, jetbrains, visualstudio, eclipse, vim, emacs, sublime, macos, windows, linux. Returns: JSON { content (.gitignore text), unknownTemplates[], duplicatesRemoved, tests[{ path, ignored, rule{pattern,line,negate}, via }] }. Example input: {"templates":["node","macos","vscode"],"testPaths":[".env","node_modules/x.js",".vscode/settings.json"]}
    ConnectorNo auth
  • Creates a shareable link to a playground that runs the given code in the browser (PHP in WebAssembly), with no account and nothing to install. Give only the files you change or add: the others stay as in the starting project (see get_starter). Nothing is stored: the code travels inside the link, after the "#". The page asks the visitor before running code received by a link.
    ConnectorNo auth
  • Creates a shareable link to a playground that runs the given code in the browser (PHP in WebAssembly), with no account and nothing to install. Give only the files you change or add: the others stay as in the starting project (see get_starter). Nothing is stored: the code travels inside the link, after the "#". The page asks the visitor before running code received by a link.
    ConnectorNo auth
  • Install an app template on a VPS/Cloud site. Starts a background installation. Poll get_app_status() for progress. Requires: API key with write scope. VPS or Cloud plan only. Args: slug: Site identifier template: App template slug. Available: django, laravel, nextjs, nodejs, nuxtjs, rails, static, wordpress app_name: Short name for the app (2-50 chars, lowercase alphanumeric + hyphens). Used as subdomain: {app_name}.{site_domain} db_type: Database type. "none", "mysql", or "postgresql" (depends on template) domain: Custom domain override (default: {app_name}.{site_domain}) display_name: Human-friendly name (default: derived from app_name) Returns: {"id": "uuid", "app_name": "myapp", "status": "installing", "message": "Installation started. Poll for progress."} Errors: FORBIDDEN: Plan does not support apps (shared plans) VALIDATION_ERROR: Invalid template, app_name, or duplicate name
    ConnectorNo auth