PHP MCP Server Generator

PHP MCP server generator

Generate a production-ready PHP MCP server by collecting project requirements, reading the bundled implementation reference, then producing a Composer project with typed tools, optional resources and prompts, tests, runnable stdio or HTTP transport configuration, and clear tools/resources boundaries.

When to invoke

• "Generate a PHP MCP server."
• "Create a complete MCP server project using the PHP SDK."
• "Scaffold MCP tools, resources, prompts, and tests in PHP."
• "Build a stdio or HTTP PHP MCP server for Claude Desktop."
• "I need project requirements for a PHP MCP server."

Prerequisites and context

• PHP 8.2 or higher is required.
• Composer is required for dependency installation and autoloading.
• Read references/templates-and-development.md before generating files or implementing PHP tools/resources.
• Use the official PHP SDK patterns from the bundled reference; do not invent framework APIs when the reference gives an attribute, bootstrap, or test pattern.

Required inputs

Project structure

Generate this tree and omit only optional folders the user explicitly excludes:

{project-name}/
├── composer.json
├── .gitignore
├── README.md
├── server.php
├── src/
│   ├── Tools/
│   │   └── {ToolClass}.php
│   ├── Resources/
│   │   └── {ResourceClass}.php
│   ├── Prompts/
│   │   └── {PromptClass}.php
│   └── Providers/
│       └── {CompletionProvider}.php
└── tests/
    └── ToolsTest.php

Implementation rules

Commands and runtime configuration

Claude Desktop configuration:

{
  "mcpServers": {
    "{project-name}": {
      "command": "php",
      "args": ["/absolute/path/to/server.php"]
    }
  }
}

Tool design checklist

Progressive disclosure and bundled resources

• references/templates-and-development.md: PHP MCP templates, SDK development details, and implementation patterns. Open it before generating composer.json, server.php, tool classes, resources, prompts, providers, or tests.

Gotchas

• Do not skip the bundled reference: the reference carries the SDK-specific templates that prevent plausible but wrong PHP MCP APIs.
• Do not generate untyped PHP: strict types, PHPDoc, and return types are required because MCP schemas are inferred from code.
• Do not make every transport default: implement stdio, http, or both according to the user's requirement.
• Do not cache discovery only in memory for production: use PSR-16 cache for stable production discovery.

Output template

## PHP MCP server project

**Status:** generated | requirements needed | blocked
**Project:** `{project-name}`
**Transport:** stdio | http | both
**PHP target:** `8.2+`

### Files
| Path | Purpose |
| --- | --- |
| `composer.json` | Dependencies, scripts, autoloading |
| `server.php` | MCP server entrypoint |
| `src/Tools/{ToolClass}.php` | Tool implementation |
| `src/Resources/{ResourceClass}.php` | Resource implementation, if requested |
| `src/Prompts/{PromptClass}.php` | Prompt implementation, if requested |
| `tests/ToolsTest.php` | PHPUnit coverage for tools |

### Commands
- `composer install`
- `vendor/bin/phpunit`
- `php server.php`
- `npx @modelcontextprotocol/inspector php server.php`

### Claude Desktop
```json
{
  "mcpServers": {
    "{project-name}": {
      "command": "php",
      "args": ["/absolute/path/to/server.php"]
    }
  }
}
```

Quality gate

• The project name, description, transport type, tools, resource/prompt choice, and PHP version are known.
• references/templates-and-development.md was read before generating implementation code.
• The generated tree contains composer.json, .gitignore, README.md, server.php, src/, and tests/.
• Tool classes use #[McpTool]; resource and prompt classes use #[McpResource] and #[McpPrompt] when present.
• Parameters use #[Schema], strict types, PHPDoc, and explicit return types.
• Production discovery uses PSR-16 cache.
• README includes composer install, vendor/bin/phpunit, php server.php, inspector usage, and Claude Desktop JSON.