Enjin Platform MCP Server

🚀 Enjin Platform API Tool MCP Server

This MCP server enables interaction with the Enjin Platform API.

🚀 Quick Start

✨ Features

This MCP server allows seamless interaction with the Enjin Platform API, offering a range of tools for NFT collection management and more.

📦 Installation

Prerequisites

• Node.js (v16 or higher)
• Any supported MCP IDE
• Enjin Platform API Key

Setup Instructions

1. Obtain an Enjin Platform API Key

• Create an account on the Enjin platform.
• Generate an API key.

2. Initial Project Setup

Install dependencies:

npm install

3. Configure Environment Variables

Create a .env file for local development (do not commit this file), or define environment variables in your IDE's MCP server configuration.

Example:

ENJIN_API_ENDPOINT=https://platform.canary.enjin.io/graphql
ENJIN_API_KEY=your-enjin-api-key

4. Configure Your Supported IDE

Follow the instructions for your specific IDE to configure the MCP server. This typically involves the following steps:

1. Add a new server configuration.
2. Specify the command to run the server (e.g., node build/index.js).
3. Set environment variables (e.g., ENJIN_API_KEY). Refer to your IDE documentation for detailed instructions.

💻 Usage Examples

Available Tools

The current server provides the following tools:

create_collection

Create a new NFT collection on the Enjin platform. Requires the following parameters:

• name: (string) The name of the collection.
• description: (string) The description of the collection.
• media: (string) The collection media URL.

get_collection

Retrieve a collection from the Enjin platform. Requires the following parameters:

• collection_id: (string) The collection ID.

📚 Documentation

Type Definitions

// Example type definitions - adjust according to your API responses
interface EnjinApiError {
    status?: number;
    message: string;
    code?: string;
}

interface Collection {
    id: string;
    name: string;
    description: string;
    media: string;
    // ... other collection attributes
}

Error Handling

The server handles various error scenarios:

Environment Errors

• Missing ENJIN_API_KEY
• Invalid API key

API Errors

• Rate limiting
• Invalid request parameters
• Internal server error

Troubleshooting

Tool Not Displayed in IDE

• Check the IDE logs
• Verify that ENJIN_API_KEY is correctly set
• Ensure the server is running

Authentication Errors

• Verify that the API key is valid
• Check if the key has the necessary permissions

Viewing Logs

To view server logs, refer to your IDE documentation on how to view MCP server logs.

Environment Variables

If you encounter environment variable errors, verify the following:

• ENJIN_API_ENDPOINT: Should be a valid Enjin platform API endpoint
• ENJIN_API_KEY: Should be a valid Enjin platform API key

🔧 Technical Details

Security Considerations

• Keep your API key secure
• Do not commit credentials to version control
• Use environment variables to store sensitive data
• Rotate API keys regularly
• Monitor API usage on the Enjin platform