Get the FREE Ultimate OpenClaw Setup Guide →

Server-facu 2.0.5

MCP server from PoQaT/Server-facu-mcp2.0.5

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio poqat-server-facu-mcp2.0.5 node path/to/server.js

How to use

This MCP server, named server-facu, implements the MCP protocol facade for the poqat-server-facu-mcp2.0.5 release. It exposes a configurable MCP endpoint that can be integrated with Minecraft clients or proxy layers supporting the MCP adapter. Once started, you can connect your MCP-aware tooling or proxy to the server-facu endpoint to perform MCP-style commands, fetch metadata, and interact with the server’s command handlers. The included features are designed to align with the MCP protocol expectations for version 2.0.5, and the slug poqat-server-facu-mcp2.0.5 indicates the specific build and naming convention used for this release.

How to install

Prerequisites:

  • Node.js (v14+ or as required by the project).
  • Access to the repository with the MCP server sources.
  1. Install Node.js from the official website or via your package manager.
  2. Ensure you have the MCP server files checked out, including the server.js entrypoint referenced in the configuration.
  3. Install dependencies (if a package.json exists). Run: npm install
  4. Run the server using the configuration described in mcp_config. For the Node-based setup shown, start the server with: node path/to/server.js
  5. Verify the server starts without errors and that the MCP endpoint is reachable at the configured port/address.
  6. If you need to adjust environment variables, set them before starting the process, for example: export VAR_NAME=value node path/to/server.js

Additional notes

Notes:

  • The release is labeled Server-facu 2.0.5 with slug poqat-server-facu-mcp2.0.5, indicating versioning and deployment naming for this MCP build.
  • The msp faco 2.5 line in the README suggests compatibility or reference to a facsimile module or feature set; verify any integration points against your MCP tooling.
  • If you encounter port binding or connection issues, check firewall rules and ensure the configured port is not in use by another process.
  • If the process crashes, inspect logs for MCP protocol negotiation errors or missing dependencies; ensure the Node.js version matches the project's compatibility matrix.

Related MCP Servers

Sponsor this space

Reach thousands of developers