Developer Guide
Item MCP supports importing API from Apifox, OpenAPI, and Swagger, which then can be automatically converted into MCP servers via Integrations that can be published as MCP Servers.
API Integration
Below is the flowchart:
Server Integration via item DI
The connector is exposed via the MCP protocol, with each API mapped to a tool. This allows AI agents to interact with it like any other MCP server.
┌────────────┐ API Call ┌───────────────┐
│ MCP Server │ ───────────────► │ Item DI API │
│ (Tool: getOrder) │ (GET /orders) │
└────────────┘ └───────────────┘
↓ ↑
Formatted as Tool Appears as "Connector" in Item DI
Shopify Integration
This guide focus on how to configure and register an external API in Item DI, and convert it into an MCP-compatible server that can be used in Item MCP.
Prerequisites
- Item DI Login Account
- Shopify Client Credentials
- Shopify API
To obtain the Client ID and Client Secret from Shopify:
- Log in to the Shopify Partner Portal (opens in a new tab).
- Navigate to Apps > All apps > Create app.
- Select Create app manually and give it a name.
- Copy the Client ID and Client Secret for later use.
Step 1: Configure Basic Info
- Log in to item DI (opens in a new tab).
- Navigate to Integrations > Add New Integration.
- Fill in the metadata for this integration:
Field | Description | Example |
---|---|---|
Name | Display name for users | Shopify |
Code* | Unique internal identifier | Shopify_demo_06_09 |
Logo | Optional icon | (optional) |
Type* | Type | Sales Channel |
Supported Regions* | Markets supported | US, China, Japan |
Help Document | External doc link | https://shopify.dev/docs/api (opens in a new tab) |
Request Limit* | API call limit | 2 |
Time Unit* | Time unit for rate limit | Per second |
API Endpoints | Dev / Stage / Prod URLs* | https://$ {ShopDomain}.myshopify.com |
Common Parameters | Shared API variables | ShopDomain |
- Add the
ShopDomain
field in Common Parameters Schema. - Provide a field description in advanced settings to guide users.
- Click Save and Next.
Step 2: Configure Authentication Method
- Choose OAuth 2.0 Code as the authentication type.
- Fill in the Client ID and Client Secret.
- Under Build Auth URL, add:
- grant_options[]
- scope
- Set token expiration values to
-1
(indicates no expiration).
- In the Code to Token tab, fill in:
- Token URL
- Access/Refresh Token Expiration:
-1
- Click Save and Next.
Step 3: Test the Configuration
- Create a test API using the GET method.
- Add the following header:
X-Shopify-Access-Token = ${accessToken}
- Add an assert expression:
httpCode == 200
- Leave output type as Normal.
- Click Save and Next.
- Copy the Redirect URL from the Authentication tab.
- In the Shopify App Dashboard, register this Redirect URL.
- Click Save and Release in the Shopify developer portal.
Step 4: Create the Connector in Workspace
- Go to Workspace, select a merchant, and click + Add Connector.
- Choose the Shopify connector created earlier.
- Enter the shop domain, e.g.,
iphone.myshopify.com
. - Click Go to Verify to complete authentication.
- After a successful redirect, the message "Connection successful" will appear.
- Click Test Connection and submit.
- The connector will now be listed under Connected Systems.
Step 5: View Logs
- Go to Integrations > Connector.
- Click View Logs to check connection and request history.
Step 6: Add Supported Features
- Click Add New Feature.
- Example: Add a "Query Location" feature.
Field | Description |
---|---|
Feature Code | Unique ID for function |
Feature Name | Display name |
Feature Description | Detailed purpose and parameters |
- Under JSON Schema Settings, define:
- params.limit = ${params.limit}
- Import an
api.json
configuration file. - In Output Processing, choose:
- Output type: Path
- JSONPath:
$.data
- Configure request headers, body, and query parameters.
- Run a test — location information should be returned.
- The feature will now appear under Supported Features.
Final Step: Test Servers
After completing the Shopify integration in Item DI, it is registered as a connector and can also be automatically published as an MCP server.
You can copy the SSE link and add it to any MCP-compatible client.