mcp

The Apillon MCP Server provides a modular collection of MCP integrations for Storage, Hosting, and NFT workflows. It exposes these capabilities as MCP modules that an LLM-driven agent can invoke to manage files, deploy web applications, and handle NFT operations across multiple chains. You can connect your LLM tooling to this server and seamlessly perform actions like creating and listing storage buckets, uploading files, deploying websites to staging or production, and minting or transferring NFTs. The server is designed to be accessed through the MCP interface, enabling your agents to call module endpoints through the standard MCP protocol and receive structured results.

Typical usage involves running the MCP server locally or in your infra, then instructing your agent to perform specific actions. For Claude Desktop, you can wire the server as an MCP source by configuring an mcpServers entry that points to the server’s package and environment variables (such as your Apillon API key/secret). The server package exposes the Storage, Hosting, and NFT modules, so your prompts can request tasks like creating a storage bucket, uploading a folder, deploying a website, minting an NFT, or transferring collection ownership. Integrations are designed to work with various data sources and tooling, enabling flexible and secure data handling within your environment.

Prerequisites

• Node.js 22 or higher
• npm 11 or higher
• TypeScript (for local development scenarios)
• An Apillon API key and secret (for MCP access)

Installation steps

1. Clone the repository and install dependencies

git clone https://github.com/Apillon/mcp-server.git
cd mcp-server
npm install

2. Start the MCP server locally

npm start

3. If you want to run via Claude Desktop integration, ensure your Claude config points to the MCP server as shown in the example:

{
  "mcpServers": {
    "apillon-mcp-server": {
      "command": "npx",
      "args": ["-y", "@apillon/mcp-server"],
      "env": {
        "APILLON_API_KEY": "<APILLON_API_KEY>",
        "APILLON_API_SECRET": "<APILLON_API_SECRET>"
      }
    }
  }
}

4. Validate the server is reachable from your MCP client (e.g., Claude) and test with a simple storage/hosting/NFT operation.

Additional notes

• If you prefer a local TS-based run (for development), you can point Claude to ts-node/tsx runner with the index.ts entry, e.g.:

{
  "mcpServers": {
    "apillon-mcp-server": {
      "command": "tsx",
      "args": ["/full/path/to/index.ts"],
      "env": {
        "APILLON_API_KEY": "<APILLON_API_KEY>",
        "APILLON_API_SECRET": "<APILLON_API_SECRET>"
      }
    }
  }
}

• Ensure API keys are kept secure and not committed to version control. Use environment variables or secret management where possible.
• The server supports multiple modules; you can expand the mcpServers configuration to include additional MCP-enabled components (e.g., filesystem workers) if needed.

Tips and common issues:

• Make sure your APILLON_API_KEY and APILLON_API_SECRET are valid and have the necessary permissions for Storage, Hosting, and NFT modules.
• When using Claude Desktop, restarting Claude after updating the MCP configuration ensures the new endpoints are loaded.
• If you encounter schema errors, verify that the MCP server version matches the client’s expected MCP schema and that the server is reachable at the configured address.
• For local development, using TS/tsx runner provides faster iteration; for production, running via npx or your package manager is recommended for stability.
• Consider setting explicit timeouts and retry policies in your MCP client to handle network hiccups gracefully.