AI SummaryA Symfony package that simplifies building secure Model Context Protocol servers with real-time communication via SSE and StreamableHTTP, designed for enterprise applications. Developers building AI agents, agentic systems, or MCP-based tools in Symfony/Windsurf environments benefit from this specialized toolkit.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "symfony-mcp-server — Windsurf Rules" prompt rules to my project. Repository: https://github.com/klapaudius/symfony-mcp-server Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
A Symfony package designed for building secure servers based on the Model Context Protocol, utilizing Server-Sent Events (SSE) and/or StreamableHTTP for real-time communication. It offers a scalable tool system tailored for enterprise-grade applications.
Features
• https://modelcontextprotocol.io/docs/concepts/architecture • https://modelcontextprotocol.io/docs/concepts/tools • https://modelcontextprotocol.io/docs/concepts/transports • https://modelcontextprotocol.io/sdk/java/mcp-server
Technical Specification
• Support Symfony 6.4 and 7 • Support PHP 8.2+
Symfony Package Development Guideline
• Create new class and refactor if the file is getting too long. (more than 300 lines)
Documentation Guidelines
• Document all public methods and classes with PHPDoc annotations. • Include @param, @return, and @throws tags for all methods. • Document configuration options with sample values and explanations. • Keep documentation up-to-date when changing functionality. • Use descriptive variable and method names to improve self-documentation. • Add inline comments for complex logic explaining the "why" not just the "what". • Create markdown documentation for end-users in the docs/ directory. • Include version compatibility information in all documentation. • Document breaking changes prominently in CHANGELOG.md and README.md. • Add type hints and return types to all methods for better IDE support. • Document expected environment variables and their purposes. • Maintain a FAQ section in the documentation for common issues. • Document how the package integrates with Symfony's existing features. • When specifying types, especially for nullable types, do not use ?string. Always write string|null instead of using ?, and make sure null is placed at the end.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts