This MCP server exposes the FOAAS (Fuck Off As A Service) API as a set of 23 tools, each mapped 1:1 to a FOAAS operation and prefixed with foaas_. The server runs inside a Docker container and communicates via standard input/output, keeping network exposure limited as per MCP best practices. You can invoke specific tools directly through MCP in your development workflows or CI pipelines, such as foaas_logs to fetch logs, foaas_legend to praise someone, or foaas_think to question a decision. The repository provides concrete examples of how to call tools, including target parameters when required (for example, to and from values). In typical usage via MCP, you’ll specify the tool name and the argument structure, then receive a FOAAS-style response in return. This makes it easy to incorporate humorous, context-appropriate responses into issue templates, pull requests, or automated checks without leaving your development environment.

Prerequisites:

• Docker installed and running on your machine or CI environment
• Access to the container image registry (ghcr.io) used by this MCP server

Install and run (pre-built image):

1. Pull the pre-built FOAAS MCP image: docker pull ghcr.io/gusztavvargadr/foaas-mcp:latest

2. Run the MCP server via Docker (as an MCP server entry): docker run --rm -i ghcr.io/gusztavvargadr/foaas-mcp:latest

3. Alternatively, configure in your IDE (e.g., VS Code) to connect MCP using: mcpServers: foaas: command: docker args: ["run", "--rm", "-i", "ghcr.io/gusztavvargadr/foaas-mcp:latest"]

Building from source (optional):

1. Clone the repository: git clone https://github.com/gusztavvargadr/foaas-mcp.git cd foaas-mcp

2. Build the Docker image locally (if the project provides a Dockerfile or npm script):

   Example depending on repository setup

   npm install npm run docker:build

3. Run the locally built image as in step 2 of the pre-built image instructions.

Tips and notes:

• This MCP server emphasizes Docker-based isolation and stdio-only transport (no network exposure). Ensure your environment maintains these constraints if you’re integrating with CI.
• The 23 FOAAS tools are accessed with the foaas_ prefix (e.g., foaas_logs, foaas_legends). Each tool corresponds to a FOAAS endpoint and will return a FOAAS-style message.
• When using MCP tool calls, include the required from parameter and, if the tool supports a target, include to as needed (see examples in the README).
• If you’re behind a proxy or firewall, ensure Docker can pull the FOAAS MCP image from ghcr.io and that your MCP calls are routed correctly in your workflow.
• The project emphasizes a Docker-first workflow; updates to the image will typically be published as new tags (e.g., latest, v1.0.0). Use the appropriate tag for reproducibility.