Apillon MCP Server

Created By
Apillona year ago
Overview

What is Apillon MCP Server?

The Apillon MCP Server is a server implementation that utilizes the Model Context Protocol (MCP) to provide modules for Storage, Hosting, and NFT functionalities, enabling seamless integration with Large Language Models (LLMs).

How to use Apillon MCP Server?

To use the MCP Server, install the necessary dependencies, configure your local environment, and run the server using the provided commands. You can also integrate it with the Claude LLM for enhanced functionality.

Key features of Apillon MCP Server?

  • Storage Module: Manage files and folders, generate IPFS links, and track file metadata.
  • Hosting Module: Deploy web applications, manage instances, and monitor deployment status.
  • NFT Module: Create and manage NFT collections, mint NFTs, and transfer ownership.

Use cases of Apillon MCP Server?

  1. Building applications that require file storage and management.
  2. Deploying web applications with ease.
  3. Managing NFT collections across various blockchain platforms.

FAQ from Apillon MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a standardized protocol that allows applications to connect AI models to various data sources and tools.

  • Is there a cost to use the Apillon MCP Server?

The server is open-source and free to use under the MIT License.

  • What are the prerequisites for local development?

You need Node.js 22 or higher, npm 11 or higher, and TypeScript installed.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Apillon
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago