Feature · Model Context Protocol

MCP

A Model Context Protocol client for PHP, TypeScript and Python. Discover and call server tools with explicit trust policies, definition pinning and bounded results.

For TypeScript, a server package registers and dispatches your own tools over a transport you supply.

PHP
TypeScript
Python

Read the docs →View packages GitHub

Capabilities

What it does

Trust is required

Every server needs a trust policy. Without one, asking for its tools throws server_not_trusted and no tool is offered.

TypeScript

const github = new Client({
  server: 'github',
  transport: httpTransport(process.env.MCP_GITHUB_URL!),
  trust: TrustPolicy.allowing(['search_repositories']),
});

Pinned definitions

A pin records the digest of a tool definition you have reviewed. If the server later changes it, the tool is refused instead of being offered to the model.

Guarded results

Every result passes a guard before it reaches the model: one larger than the cap is refused, not truncated, and the text is framed as data.

A gate per call

Trust decides which tools the model is told about; a gate decides whether a given caller may run one, checked before each call is sent.

Tool names that cannot collide (PHP)

PHP names tools mcp__<server>__<tool>, so two servers can both publish search.

Serve your own tools (TypeScript)

The server package registers tools and dispatches calls over a consumer-supplied transport, with a per-request visibility predicate that hides a tool from callers who should not see it.

How it fits

Where it sits in the ecosystem

MCP tools are ordinary Prism tools in PHP, so they go straight into a text request. TypeScript and Python carry the protocol rules (trust, pins, gates, result guarding) and take a transport you supply.

The PHP package replaces prism-php/relay and cannot be installed alongside it.

PHP