mcp-ayd

This MCP server is the bridge for the Ayd assistant, exposing an MCP endpoint that your client can connect to in order to query and manage Ayd through the MCP protocol. After downloading the latest release binary, configure the MCP client to point to this server by providing the path to the executable and the address of the MCP listener. In the example configuration, the server runs locally on port 9000, and the client is pointed to http://127.0.0.1:9000. With the server running, you can interact with Ayd via the MCP interface just as you would with other MCP-enabled assistants. You can ask the assistant to fetch status updates, perform actions, or inquire about information supported by Ayd, and the MCP layer will relay those requests to the underlying Ayd implementation.

Typical flow: install the binary, configure the client with the ayd server as shown, start the client application, then ask questions like "What's the latest status of Ayd?" or other contextually appropriate prompts. The server handles the MCP protocol wrapping so the client can communicate in a consistent, standard way with the Ayd backend.

Prerequisites:

• A supported operating system with a binary release for mcp-ayd-server
• Administrative privileges may be required to install or run the binary depending on location permissions
• A network path and port that can be reached by your MCP client (default example uses http://127.0.0.1:9000)

Install steps:

1. Download the latest mcp-ayd-server release binary from the GitHub releases page. 2)Extract or place the binary to a desired location. On Windows, you might place it somewhere like C:\path\to\mcp-ayd-server.exe
2. Verify you can execute the binary from your shell or terminal.
3. Create an MCP client configuration that points to the server, for example: { "mcpServers": { "ayd": { "command": "C:\path\to\mcp-ayd-server.exe", "args": ["http://127.0.0.1:9000"] } } }
4. Start the server by running the command or via the MCP client setup, then launch the MCP-enabled client.
5. Confirm connectivity by issuing a test query through the client, e.g., asking for Ayd status or other supported prompts.

Notes and tips:

• Ensure the port (default 9000) is not blocked by a firewall and is available on the host.
• Use an absolute path for the server executable to avoid issues with relative paths.
• If the configuration file uses Windows paths, escape backslashes properly (e.g., C:\path\to\mcp-ayd-server.exe).
• If you encounter connectivity issues, check that the server process is running and listening on the expected address and port.
• This MCP server delegates requests to the Ayd backend; ensure Ayd is properly installed and accessible if your setup requires it beyond the MCP layer.