MCP Server Developer Guide

This guide explains how to build a compliant and functional MCP server from scratch. You'll learn about:

• The core architecture and logic of an MCP server
• How to wrap existing APIs into MCP-compatible services

MCP Server

An MCP server is a standalone program (typically Node.js or Python) that exposes a list of tools or capabilities an AI client can invoke. MCP servers:

• Define tools using structured schemas (JSON / zod)
• Accept input from clients via a known protocol (STDIO or SSE)
• Execute logic or call APIs
• Return structured results back to the client

API Integration

This platform supports importing API from Apifox, OpenAPI, and Swagger, which then can be automatically converted into MCP servers via Connectors that can be published as MCP Servers.

Below is the flowchart:

Channel-to-Server Integration

This guide focus on how to configure and register an external API in Item DI using the Channel Store, and convert it into an MCP-compatible server that can be used in Item MCP.

┌────────────┐     API Call     ┌───────────────┐
│ MCP Server │ ───────────────► │   Item DI API │
│ (Tool: getOrder)              │ (GET /orders) │
└────────────┘                  └───────────────┘

  ↓                                ↑
Formatted as Tool           Appears as "Channel" in DI

Shopify Integration via item DI

This guide walks through the process of building a Shopify MCP server using item DI, including OAuth 2.0 setup, connector creation, API testing, and supported feature configuration.

Prerequisites

To obtain the Client ID and Client Secret from Shopify:

1. Log in to the Shopify Partner Portal (opens in a new tab).

2. Navigate to Apps > All apps > Create app.
3. Select Create app manually and give it a name.

4. Copy the Client ID and Client Secret for later use.

Step 1: Configure Basic Connector Info

1. Log in to item DI (opens in a new tab).
2. Go to Integrations > Add New Integration.

3. Fill in the connector metadata:

4. Add the ShopDomain field in Common Parameters Schema.
5. Provide a field description in advanced settings to guide users.

6. Click Save and Next.

Step 2: Configure Authentication Method

1. Choose OAuth 2.0 Code as the authentication type.

2. Fill in the Client ID and Client Secret.

3. Under Build Auth URL, add:
   • grant_options[]
   • scope
4. Set token expiration values to -1 (indicates no expiration).

5. In the Code to Token tab, fill in:
   • Token URL
   • Access/Refresh Token Expiration: -1
6. Click Save and Next.

Step 3: Test the Configuration

1. Create a test API using the GET method.
2. Add the following header:
   • X-Shopify-Access-Token = ${accessToken}
3. Add an assert expression: httpCode == 200

4. Leave output type as Normal.
5. Click Save and Next.
6. Copy the Redirect URL from the Authentication tab.
7. In the Shopify App Dashboard, register this Redirect URL.

8. Click Save and Release in the Shopify developer portal.

Step 4: Create the Connector in Workspace

1. Go to Workspace, select a merchant, and click + Add Connector.
2. Choose the Shopify connector created earlier.

3. Enter the shop domain, e.g., iphone.myshopify.com.

4. Click Go to Verify to complete authentication.

5. After a successful redirect, the message "Connection successful" will appear.
6. Click Test Connection and submit.

7. The connector will now be listed under Connected Systems.

Step 5: View Logs

1. Go to Integrations > Connector.

2. Click View Logs to check connection and request history.

Step 6: Add Supported Features

1. Click Add New Feature.

2. Example: Add a "Query Location" feature.

3. Under JSON Schema Settings, define:
   • params.limit = ${params.limit}
4. Import an api.json configuration file.
5. In Output Processing, choose:
   • Output type: Path
   • JSONPath: $.data
6. Configure request headers, body, and query parameters.

7. Run a test — location information should be returned.

8. The feature will now appear under Supported Features.

After completing these steps, the connector (API) becomes available in Item DI as a "channel". It is now also exposed to Item MCP as a server following the MCP protocol automatically. You can test or register it in Playground, or add it to MCP clients.