Other MCP clients

The server follows the standard Model Context Protocol, so any MCP-compatible client can use it — Claude Desktop, Windsurf, Zed, Continue, VS Code's MCP support, JetBrains AI Assistant, custom agents built on an SDK, and more.

Most clients accept one of two shapes. Reuse the reference values from the overview: the absolute path to this project's artisan, and your deployed URL.

Local (stdio)

Launch the server as a child process:

• Command: php
• Arguments: ["/absolute/path/to/OiDevDocs/artisan", "mcp:start", "documentation"]

Most JSON-based clients express this as:

{
    "mcpServers": {
        "oi-docs": {
            "command": "php",
            "args": [
                "/absolute/path/to/OiDevDocs/artisan",
                "mcp:start",
                "documentation"
            ]
        }
    }
}

Remote (HTTP)

Point the client at the streamable-HTTP endpoint:

{
    "mcpServers": {
        "oi-docs": {
            "url": "https://dev.olacombe.com/mcp/documentation"
        }
    }
}

Some clients name this field httpUrl, serverUrl, or expect an explicit "type": "http" — check your client's docs, but the endpoint is always the same.

Building your own client

If you're integrating from Laravel itself, the laravel/mcp package ships a client too:

use Laravel\Mcp\Client;

$client = Client::web('https://dev.olacombe.com/mcp/documentation');

$result = $client->callTool('search-documentation', [
    'query' => 'vector search',
]);

Troubleshooting

• Server seems to hang — never run php artisan mcp:start directly; it waits for a client on stdin. Let the client launch it, or test with php artisan mcp:inspector documentation.
• HTTPS locally — some Node-based clients reject self-signed certificates. Prefer the local (stdio) transport on a single machine, or a valid certificate for HTTP.
• No tools listed — confirm the server is registered (php artisan mcp:inspector documentation) and that the search index exists (php artisan doc:gen-index).