Agent
Discoverability

Mycloud MCP

Work with your MyCloud Fulfillment data in plain language — orders, stock arrivals and returns — whether that is one lookup, an analysis across a date range, or a spreadsheet.

View in the Claude registry
Brand
Unknown
Category
Pending
Primary Subcategory
Pending
Integration details

Description

MyCloud Fulfillment is an order fulfillment service for online sellers in Thailand. This connector lets a merchant work with their own MyCloud OMS account by asking in plain language, instead of opening the web app and filtering a list by hand. What you can ask about Outbound orders (MC) — the sales orders going out to your customers. Search by date, state, SKU, order number, tracking number or customer name, and pick which date the range applies to: created, instructed, fulfilled, shipped or paid. Open one order in full with its items and the recipient's delivery details. Inbound orders (IO) — stock arriving at the warehouse. Browse by state, or open one to see what was declared against what was actually received. Return orders (RE) — goods coming back from customers, with the condition they arrived in. Spreadsheets — any date range with one row per line item, as a download link or as a table in the conversation. Signing in You sign in with your own MyCloud OMS email and password over OAuth 2.0. The sign-in screens are in Thai and English. Your password is passed to MyCloud OMS to be checked and is never stored here. The connection covers the shops your MyCloud member account belongs to. MyCloud decides that on every request, so a shop you do not belong to is refused. Every answer names the shop it came from, so an answer about the wrong shop is visible rather than silent. Limits worth knowing Searches and exports by date reach back 30 days. A search returns up to 100 rows. An export covers up to 1,000 orders at once and says so when more match, rather than implying it found everything. Inbound and return orders are browsed by state and opened by document number; they carry no date filter. Today the connector only reads. It cannot create, change or cancel anything in MyCloud OMS.

Integration type
Connector
Verification status
Community connector
Platform
Claude
Category
Pending

The broad Category that contains the Primary Subcategory.

Primary Subcategory
Pending

The Primary Subcategory used for this profile’s headline score.

Secondary Subcategories
None listed

Other Subcategories where the Integration is listed.

Brand
Unknown
Access
Account required
First tracked
2026-10-16
Tool count
6
Geography
US
Agent DiscoverabilityClaude Discoverability Score

Claude Connector discovery is coming soon

Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.

No spam. Unsubscribe any time.

No spam. Unsubscribe any time.

What discovery looks like

Claude showing a list of relevant Connectors in a conversation

Claude can surface verified Connectors when they match a user’s Prompt.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce Mycloud MCP has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.
Tools

6 tools agents can invoke

Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.Read guide
FAQs

Mycloud MCP Claude Connector FAQ

How the directory, categories and Discoverability Score work.

Read the methodology
How do I improve Mycloud MCP's Claude Connector discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.