MCP Marketplace

Item MCP Marketplace acts as a discovery and integration hub for prebuilt MCP servers where you can browse, preview and integrate servers to client platforms as needed.

Server Categories

The servers listed in the Marketplace divided into two main categories. Each serves a different purpose depending on whether the user operates within the item ecosystem or integrates external tools.

Category	Description	Examples
Item Ecosystem Servers	Built specifically for the item platform, designed to connect internal systems and close functional gaps across OMS, WMS, DI, etc.	item OMS, item WMS
Third-party & Open-source Servers	Official or community-maintained servers widely used in daily workflows or the logistics domain.	GitHub, Amazon Knowledge Base, File System, Shopify

Search / Filter Servers

The MCP server marketplace categorizes servers using tags based on business scenarios.

MCP Marketplace

To browse or filter servers:

Filter categories by Tags or type Keyword to search the specific server. Server categories include:
- Productivity & Project Management
- Development Tools
- Data and File system
- Web & Browser Automation
- and so on
Click Explore Integration. Each server displays the following detailed info:

Section	Description
Basic Info	Display the server description, connection type (STDIO/SSE), usage instructions, version number, provider, and user rating.
Available Features	List all tools included in the server, along with brief tool descriptions.
Instructions	Display either the Generate link button or JSON configuration content. Provide documentation or tutorial videos to guide you through installation. Multiple setup options are available depending on the environment.
Tool Quick-Test	Quick-test tools directly from the Marketplace before integrating them into a client.

Integrate Servers

When integrating MCP servers, the authentication method determines how access is authorized. Item MCP provides multiple authentication methods depending on the server type.

Item Internal Servers (via Generate link)
Open-Source / Community Servers (via CLI or Manual Setup)

Generate Server Link

This method applies to both Item systems (item OMS) and third-party platforms (Shopify).

To generate a server link in Item MCP:

Click Generate Link.
Provide the required information.

For Shopify servers, enter your Shop Domain, click Go to verify, you will be redirect to your-store.myshopify.com to complete OAuth authorization.

shopify-oauth

For Item OMS, clicking Generate Link will redirect you to the Item IAM login page to sign in with your Item credentials.

oms-oauth-2

Click Test Connection to verify the setup.
If the test is successful, Click Submit.
A server link will appear under the Existing Links section, which is ready to be added to item MCP client.

exsit-link

Internal Servers Auth Methods

The authentication process depends on the server’s required method.

Auth Method	Operation
API Key	Paste the API key manually when prompted. It will be included in the request headers.
Basic Auth	Enter your username and password. These are encoded and used to authenticate each request.
Session Auth	You’ll be redirected to a login page to complete sign-in.
OAuth 2.0 (Authorization Code)	You’ll be redirected to the third-party platform (e.g., Shopify) to approve access, then returned to Item MCP with a token automatically issued.

CLI or Manual Setup

Item MCP fetches several popular MCP servers from the official MCP site, allowing you to explore servers in the marketplace and find documents with instructions. For more servers, see Model Context Protocol Server Repository (opens in a new tab). As it currently does not support adding open-source MCP servers directly to its built-in client interface. You can manually add them in external MCP-compatible clients such as Cursor or Claude by pasting the corresponding JSON configuration.

github

To add servers to Cursor:

Open Cursor > Settings > MCP > Add new global server.
The config file may looks like:

{
  "mcpServers": {
    // Add your entries here
  }
}

Paste one (or both) of the server entries under "mcpServers".

Github

"github": {
  "command": "npx",
  "args": ["-y", "@modelcontextprotocol/server-github"],
  "env": {
    "GITHUB_PERSONAL_ACCESS_TOKEN": "your_token"
  }
}

This uses a Personal Access Token, set via env, to authorize GitHub API requests.

Filesystem

"filesystem": {
  "command": "npx",
  "args": [
    "-y",
    "@modelcontextprotocol/server-filesystem",
    "C:/Users/your_file_path"
  ]
}

No auth required. Replace C:/Users/your_file_path with the root path that you want the server to access.

Save and restart Cursor if needed.
Go to the MCP section in Cursor. The new servers with available tools will appear.

use-case

Open-source Servers Auth Methods

Open-Source servers Authentication depends on the package or repo design. Common patterns include:

Server	Auth Method	Description	How It's Passed
GitHub	Personal Access Token	Token generated in GitHub settings to access repos, issues, etc.	`GITHUB_PERSONAL_ACCESS_TOKEN` via `env`
Google Sheets	Service Account JSON	Requires a credential file from Google Cloud (OAuth 2.0 behind the scenes).	Path to `.json` file via `GOOGLE_APPLICATION_CREDENTIALS`
Notion	Internal Integration Token	Generated in Notion's developer portal to access workspace content.	`NOTION_API_KEY` via `env`
Slack	Bot/User Token	Token to access Slack APIs via a bot or workspace.	`SLACK_BOT_TOKEN` via `env`
PostgreSQL	Basic Auth + Connection URL	Username/password (or .pgpass) plus DB connection URL.	Passed in tool config or `env`
AWS Knowledge Base	Access Key + Secret	Requires IAM credentials for access to S3/Retrieval Index.	`AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`
Filesystem	No Auth / Local Access	Assumes access to local directories or files; may require base path or sandbox.	Base path passed as argument

For Developers Playground