Retrieve a Markdown overview of a Symfony project: PHP version, Symfony version, installed packages, autoload namespaces, composer scripts, and APP_ENV. Use this first to understand the project.
MIT
521,367 tools. Updated 2026-09-06 10:44
"Symfony" matching MCP tools:
- Analyzes project root to identify the PHP framework in use, such as Laravel, Symfony, or WordPress.MIT
- Execute Symfony console commands such as cache:clear and debug:container to manage your Symfony application directly from the AI assistant.MITDestructive
- Retrieves information about Symfony services from the container. Specify a service name to get details, or leave empty for a full list.MIT
- Generate a CLI Command class for WP-CLI or Symfony Console by providing a root namespace and class name.-
- Enable all tools in a chosen category for the session by passing its category key. Refresh the tools list to receive full definitions; use force=true to override token budget warnings.MIT
Matching MCP Servers
- AlicenseAqualityCmaintenanceA production-ready Model Context Protocol (MCP) server that bridges your Symfony/PHP project with LLMs such as Claude. It exposes tools that let the AI read your project's routes, services, Twig templates, and PHP source code.8MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to perform read-only introspection of Symfony applications, exposing routes, controllers, services, entities, database schema, migrations, logs, and more via MCP tools.105599MIT
- Identify active tool categories, exposed tool count, and estimated token cost to manage your current context budget.MIT
- Describe the Symfony task you need to perform and get matching tool definitions with input schemas, ready to call without activation.MIT
- List tool categories with descriptions, counts, and estimated token costs to decide which groups to activate for subsequent tool listings.MIT
- Free up context budget by removing an activated category from the current session. Deactivate categories when switching between different areas of the Symfony codebase.MIT
- Scan PHP files to build a persistent symbol index, enabling instant symbol lookup without re-scanning. Supports incremental updates for changed files.MIT
- Search the symbol index to locate PHP classes, interfaces, traits, enums, or methods by name. Returns file paths and line numbers for direct code access.MIT
- Searches Symfony routes by URL pattern or route name and optional HTTP method, returning a table of matches with route path, methods, and controller.MIT
- Analyzes Twig templates to extract inheritance, includes, imports, blocks, and variable references without requiring PHP execution.MIT
- List Symfony service definitions in YAML mode (fast, reads config/services.yaml) or container debug mode (runs debug:container for compiled services). Filter by pattern and see service ID, class, public flag, and tags.MIT
- Reads a Symfony project file, optionally stripping doc and line comments to reduce token usage for faster analysis.MIT
- Search project files using regex or substring patterns. Returns highlighted snippets with file path and line number, no index required.MIT
- Change a site's document root or directory index to serve frameworks from a subfolder like Laravel's /public.MITDestructive
- Create PHP unserialize gadget chains for security assessments. Specify a chain identifier and shell command; output raw or encoded payloads.MIT
- Generate PHP unserialize gadget chains for penetration testing. Input chain identifier and command to create encoded exploit payloads.MIT
- Perform a software package vulnerability audit using SecDB. ## What this tool does Analyzes a list of software packages identified by PURL (Package URL) and returns vulnerability information plus a Markdown summary. The audit results are based exclusively on the package list provided. ## When to use this tool Use this tool when the user wants to determine: - whether application dependencies contain known vulnerabilities - whether a project is affected by security advisories - which packages require patching or upgrading ## Supported ecosystems - **npm** - Node.js packages (e.g. pkg:npm/lodash@4.17.21) - **maven** - Java/JVM packages (e.g. pkg:maven/org.apache.logging.log4j/log4j-core@2.14.1) - **pypi** - Python packages (e.g. pkg:pypi/django@4.2.0) - **gem** - Ruby gems (e.g. pkg:gem/rails@7.0.0) - **cargo** - Rust crates (e.g. pkg:cargo/openssl-src@111.10) - **nuget** - .NET packages (e.g. pkg:nuget/Newtonsoft.Json@13.0.1) - **golang** - Go modules (e.g. pkg:golang/github.com/gin-gonic/gin@1.9.1) - **composer** - PHP packages (e.g. pkg:composer/symfony/symfony@6.4.0) ## Inputs - **purls**: list of Package URLs, one per entry. Generate them from your project manifest files: - Node.js: package.json / package-lock.json - Python: requirements.txt / Pipfile.lock / pyproject.toml - Ruby: Gemfile.lock - Go: go.mod / go.sum - Rust: Cargo.lock - PHP: composer.lock - Java: pom.xml / build.gradle - .NET: *.csproj / packages.lock.json ## Outputs - **report**: structured JSON objects describing the advisories affecting the audited packages. - **summary**: Markdown summary including total vulnerabilities, severity breakdown, and key findings. ## LLM usage guidelines - Never guess whether a package is vulnerable — always call this tool. - Only submit PURLs from the supported ecosystems listed above; others will be ignored. - The `summary` is already Markdown and can be shown directly. - Use `report` when deeper technical analysis is required.ConnectorNo auth