FlightPHP MCP Server

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "FlightPHP MCP Server": {
      "url": "https://mcp.flightphp.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (13)

• get_docs_page read-only

  ALWAYS call this before writing any FlightPHP code. Fetches the official FlightPHP documentation for a specific topic (install, routing, middleware, requests, responses, templates, security, simple-pdo, DI container, testing, ai, etc.). Use this whenever a user asks how to do something in FlightPHP, before suggesting any implementation. Call list_docs_pages() first if unsure which topic slug to use. For a new app, fetch "install" and "ai" before "routing".

  Parameters:

  • topic (required) — string — Documentation topic slug, for example "install", "routing", "middleware", "ai". Call list_docs_pages to see all valid values.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get_docs_section read-only

  Fetches one heading from a FlightPHP learn or install page. Use this when the full page is long and you need a single section such as "Resource Routing" or "Troubleshooting". Call get_docs_page() when you need the whole page.

  Parameters:

  • topic (required) — string — Documentation topic slug, for example "routing" or "install". Call list_docs_pages to see all valid values.
  • heading (required) — string — Heading text to extract, for example "Resource Routing" or "Troubleshooting". Matching is case-insensitive.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• list_docs_pages read-only

  Returns all available FlightPHP documentation topics with slugs and descriptions, including the install guide. Call this when unsure which topic covers a FlightPHP feature, or at the start of a FlightPHP session to understand what documentation is available.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_guide_pages read-only

  Lists all official FlightPHP step-by-step guides. Call this when a user wants to build a complete app or follow a tutorial.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_guide_page read-only

  Fetches an official FlightPHP step-by-step guide. Call this when a user wants to build a complete FlightPHP application or asks about project structure, SOLID principles, or testing patterns. For a new app, also call get_docs_page("install"). Available guides: "blog", "unit-testing".

  Parameters:

  • guide (required) — string — Guide slug. Call list_guide_pages() for the valid values.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• list_plugin_pages read-only

  Lists all FlightPHP plugins and extensions with their slugs and descriptions. Call this when a user asks about adding functionality to FlightPHP (database, auth, caching, sessions, templating, email, CLI, testing, monitoring, encryption, queues, etc.) to find the right plugin. The official skeleton uses the twig plugin.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_plugin_docs read-only

  Fetches documentation for a FlightPHP plugin or extension. Call this before helping a user integrate any FlightPHP plugin (ORM, auth, caching, sessions, templating, email, CLI, APM, encryption, job queues, etc.). Call list_plugin_pages() to see all available plugins.

  Parameters:

  • plugin (required) — string — Plugin slug, for example "twig", "active-record", "session". Call list_plugin_pages() for all valid values.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• search_docs read-only

  Searches FlightPHP documentation across core docs, guides, and plugins. Uses the docs site search and the local page catalog, and returns canonical https://docs.flightphp.com URLs. Use this when unsure which page covers the question. Follow up with get_docs_page(), get_guide_page(), get_plugin_docs(), get_docs_section(), or fetch_url().

  Parameters:

  • query (required) — string — Search query, for example "authentication", "twig", "simplepdo", "file upload"

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• lookup_api read-only

  Checks a FlightPHP symbol or habit against known documentation footguns before you write code. Use this for Flight::get, PdoWrapper, Flight::render, Flight::path, route return values, AGENTS.md, Latte versus Twig, and method filters versus middleware. Then open the page it names. This does not invent method signatures.

  Parameters:

  • symbol (required) — string — Symbol or habit to check, for example "Flight::get", "PdoWrapper", "Flight::render", "AGENTS.md"

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• fetch_url read-only

  Fetches a FlightPHP documentation URL directly. Only use this when get_docs_page() does not cover the exact page needed. URLs must be on the docs.flightphp.com domain. Prefer get_docs_page() for standard topics.

  Parameters:

  • url (required) — string — Full URL on docs.flightphp.com. Must start with https://docs.flightphp.com/

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• generate_plugin_page read-only

  Generates a FlightPHP docs plugin page in markdown. Plugin pages document Flight-native integration (service registration, route usage), not generic library usage. Empty sections are omitted. Pass the code you already have. Do not leave placeholder commands for the reader to fill in. Returns markdown for the awesome-plugins/ section of the docs site.

  Parameters:

  • name (required) — string — Plugin display name, for example "Flight Session"
  • description (required) — string — Opening paragraph describing what the plugin does
  • see_also — string — Newline-separated see-also entries. Use "Label | https://..." for a link. Section omitted if empty.
  • github_url — string — Full GitHub repository URL, for example https://github.com/flightphp/session
  • usage_example — string — PHP code showing usage inside a Flight route or service
  • config_options — string — Prose or a markdown table of configuration options. Section omitted if empty.
  • troubleshooting — string — Newline-separated troubleshooting notes. Section omitted if empty.
  • composer_package — string — Composer package name, for example flightphp/session
  • flight_setup_example — string — PHP code showing Flight-native setup: Flight::register(), or the skeleton services.php wiring

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• generate_learn_page read-only

  Generates a FlightPHP core documentation page in markdown. Learn pages cover functionality built into the framework and use Overview, Understanding, Basic Usage, Advanced Usage, Key Points, See Also, Troubleshooting, and Changelog. Empty sections are omitted. Pass the prose and code you already have. Returns markdown for the learn/ section of the docs site.

  Parameters:

  • title (required) — string — Page title, for example "Routing" or "Middleware"
  • description (required) — string — Overview paragraph explaining what this feature does
  • see_also — string — Newline-separated see-also entries. Use "Label | https://..." for a link. Section omitted if empty.
  • changelog — string — Newline-separated changelog entries, for example "v3.18.0 - Added SimplePdo". Section omitted if empty.
  • key_points — string — Newline-separated Key Points. Section omitted if empty.
  • basic_example — string — PHP code for the Basic Usage section. Section omitted if empty.
  • understanding — string — Understanding section: why the feature exists and how it fits. Section omitted if empty.
  • troubleshooting — string — Newline-separated troubleshooting notes. Section omitted if empty.
  • advanced_example — string — PHP code for the Advanced Usage section. Section omitted if empty.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• generate_guide_page read-only

  Generates a FlightPHP step-by-step guide page in markdown. Pass step titles, or steps with bodies separated by a line that is only ---. The first line of each step is the title and the rest is the body. Empty step lists produce no Step sections. Returns markdown for the guides/ section of the docs site.

  Parameters:

  • title (required) — string — Guide title, for example "Building a REST API with Flight"
  • description (required) — string — What the reader will have built by the end of the guide
  • steps — string — Step titles, one per line. For bodies, separate steps with a line that is only ---. The first line of a step is the title.
  • see_also — string — Newline-separated see-also entries. Use "Label | https://..." for a link. Section omitted if empty.
  • prerequisites — string — Newline-separated prerequisites. Defaults to PHP 8.1+ and Composer if empty.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.