AIOZ Pin MCP Server: IPFS Pinning, Now Agent-Ready

AIOZ Pin MCP Server: IPFS Pinning, Now Agent-Ready

AIOZ Pin MCP Server is now LIVE, bringing IPFS pinning and account operations into Super Intelligence (SI) agent workflows.

With 11 tools across pinning, NFTs, gateways, and billing, MCP-compatible SI agents can interact with AIOZ Pin through natural-language prompts.

From pinning content by CID to retrieving NFT records and reviewing usage, SI agents can perform supported operations directly within their MCP clients.

Bring AIOZ Pin into SI Agent Workflows

The Model Context Protocol (MCP) is an open standard that enables SI applications to connect with external tools and services through a standardized interface, reducing the need for separate integrations.

AIOZ Pin MCP Server brings IPFS pinning, NFT records, gateway discovery, and account usage into this workflow through a single MCP server.

Once connected, MCP-compatible SI agents can discover and invoke AIOZ Pin tools in response to natural-language prompts.

The server is hosted at mcp.aiozpin.network and uses Server-Sent Events (SSE) for connections.

11 Tools Across Four Core Workflows

AIOZ Pin MCP Server provides 11 tools covering four key areas:

  • IPFS Pinning: Pin existing content by CID, retrieve pin details, list pinned files, and remove pins.
  • NFTs: Create NFT records from public asset URLs with metadata, retrieve records, and list NFTs.
  • Gateways: Discover available public and premium gateways.
  • Billing & Usage: Review usage history, monthly usage, and top-up records.

Connect with MCP-Compatible Clients

AIOZ Pin MCP Server supports integration with several MCP-compatible clients.

  • Cursor: Configure the MCP Server in mcp.json.
  • Claude CLI: Register the server using SSE transport.
  • ChatGPT: Add a custom MCP Server through Settings under Plugins.
  • VS Code: Configure .vscode/mcp.json and use GitHub Copilot in Agent mode.

Each client follows its own configuration process while accessing the same 11 AIOZ Pin tools.

Secure Access with Scoped API Credentials

AIOZ Pin MCP Server uses a pinning API key and secret key to authenticate connections.

Both credentials are supplied as base64url-encoded JSON in the api_key parameter of the connection URL. Once configured, tools can operate without requiring credentials as individual arguments.

AIOZ Pin also supports scoped API keys, allowing users to configure agent permissions according to the intended tasks.

Since the connection URL contains credentials, it should be handled securely and kept out of shared chats, screenshots, and public repositories.

Get Started with AIOZ Pin MCP Server

Connecting an MCP-compatible agent involves four steps:

  1. Create API credentials: Generate a pinning API key and secret key from the AIOZ Pin API Keys page, with scopes appropriate for your intended operations.
  2. Prepare the connection: Encode the credentials as base64url JSON following the documentation.
  3. Configure your client: Add the AIOZ Pin MCP Server using the setup instructions for your MCP client.
  4. Start prompting: Ask your SI agent to list pinned files, retrieve NFT records, or discover available gateways.

Explore the documentation for configuration steps, tool arguments, and example prompts.

AIOZ Pin MCP Server Documentation

Start with a CID. Bring AIOZ Pin into your SI agent's next workflow.