MCP.so
Sign In

VoDmAl Composer Scripts MCP Server

@VoDmAl

Basic information

Category

Other

License

Activity

Transports

stdio

Author

VoDmAl

About VoDmAl Composer Scripts MCP Server

No overview available yet

#composer-scripts#mcp-server#php-library

VoDmAl Composer Scripts MCP Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

VoDmAl Composer Scripts MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is VoDmAl Composer Scripts MCP Server?

A PHP library that exposes your project’s Composer scripts as MCP (Model Context Protocol) tools. It works with any PHP project and allows you to connect multiple projects without limits, letting AI assistants discover and execute scripts automatically.

How to use VoDmAl Composer Scripts MCP Server?

Install via composer require vodmal/composer-scripts-mcp-server then composer install. Two scripts are added: mcp:server:start and mcp:server:install. Run composer mcp:server:install for automatic integration with MCP clients (e.g., Claude Desktop). Alternatively, start the server manually with vendor/bin/mcp-server-start (stdio) or with --http flag.

Key features of VoDmAl Composer Scripts MCP Server

  • Automatic discovery of all Composer scripts as MCP tools
  • One‑step integration with AI assistants like Claude Desktop
  • Supports stdio and HTTP transports
  • Automatically adds start/install scripts to composer.json
  • Works with any PHP project, no project limit

Use cases of VoDmAl Composer Scripts MCP Server

  • AI assistants can run tests, linting, and code generation without manual command explanations
  • Developers standardize workflows across team members
  • Multiple PHP projects appear distinctly as separate tool sets
  • Simplify CI-like checks (e.g., check:before:commit) via natural language requests

Frequently asked questions

1

What are the requirements?

PHP 8.1 or higher, Composer, and the `php-mcp/server ^2.1` package.

2

How does it handle multiple projects?

You can install the server in each PHP project folder. Each project’s tool name is derived from its `composer.json` name field, so they appear distinctly in the MCP client.

3

What transports are supported?

The server supports stdio transport (default for LLM integration) and HTTP transport (for testing, with optional `--host` and `--port` arguments).

4

Where does the configuration live?

Configuration is merged into the Claude Desktop config file (or printed as JSON if not found). No external data storage is used.

5

Are there any known limitations?

Complex script chains can be harder to debug, and performance may be slightly slower than native binaries. Log messages are written to stderr when using stdio to avoid interfering with JSON communication.

Comments

More Other MCP servers