The Model Context Protocol, or MCP, provides a standard way for AI assistants to connect to applications, discover available tools, and work with live data.
We created an early MCP prototype to explore how this technology could work inside a generated PHPRunner application.
Watch the PHPRunner MCP demonstration on YouTube
Download the PHPRunner MCP sample project
MCP tools in PHPRunner
The prototype can expose standard operations for enabled application tables, including:
– Listing and searching records
– Retrieving individual records
– Adding and updating records
– Deleting records
The available tools depend on the application configuration and permissions associated with the supplied API key.
An AI assistant can process requests such as “Show me the last five orders” or “Find all products in the Pastry category,” select the appropriate tool, and return the results in a readable format.
Authentication and permissions
This initial prototype uses API-key authentication. OAuth and a separate authorization server are not required.
The MCP layer works with the PHPRunner application layer responsible for permissions, validation, events, and data access. This is especially important for operations that change data. An API key can allow an assistant to view records without granting permission to add, update, or delete them.
Custom MCP actions
Applications often include workflows that require more than a single database operation. Custom MCP actions can represent these higher-level business processes.
Multiple actions can be defined in an mcp_actions.php file. Each action describes its parameters, required permissions, behavior, and PHP handler.
The sample application includes actions for:
– Producing an inventory summary
– Receiving inventory
– Discontinuing or reactivating products
– Marking orders as shipped
– Creating a customer and complete order
– Increasing prices within a category
For example, creating a customer and order requires coordinated changes to several tables. A custom action can complete the entire workflow from one request.
MCP opens some interesting possibilities for conversational queries, application automation, reporting, and multi-step business workflows. Let us know which PHPRunner workflows you would like to access through an AI assistant.
PakarPBN
A Private Blog Network (PBN) is a collection of websites that are controlled by a single individual or organization and used primarily to build backlinks to a “money site” in order to influence its ranking in search engines such as Google. The core idea behind a PBN is based on the importance of backlinks in Google’s ranking algorithm. Since Google views backlinks as signals of authority and trust, some website owners attempt to artificially create these signals through a controlled network of sites.
In a typical PBN setup, the owner acquires expired or aged domains that already have existing authority, backlinks, and history. These domains are rebuilt with new content and hosted separately, often using different IP addresses, hosting providers, themes, and ownership details to make them appear unrelated. Within the content published on these sites, links are strategically placed that point to the main website the owner wants to rank higher. By doing this, the owner attempts to pass link equity (also known as “link juice”) from the PBN sites to the target website.
The purpose of a PBN is to give the impression that the target website is naturally earning links from multiple independent sources. If done effectively, this can temporarily improve keyword rankings, increase organic visibility, and drive more traffic from search results.
Comments are closed, but trackbacks and pingbacks are open.