II.
ToolServer JSON
Structured · livetool-server:mcp-bigcommerce-candidate
BigCommerce MCP candidate json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "tool-server:mcp-bigcommerce-candidate",
"_kind": "ToolServer",
"_file": "extensions/tool-servers/ora-operations-mcp-candidates.yaml",
"_cluster": "extensions",
"attributes": {
"displayName": "BigCommerce MCP candidate",
"description": "Candidate MCP server for BigCommerce products, catalog, orders, inventory, and customer records. Recorded from Ora discovery as a missing MCP/tool-server coverage point.\n",
"protocol": "mcp-stdio",
"provenance": "custom",
"category": "commerce",
"maintainer": "Candidate",
"sourceRef": "source-ref:ora-discover-api",
"candidateStatus": "needs-source-verification",
"ora": {
"domain": "bigcommerce.com",
"score": 72,
"grade": "B"
}
},
"outgoingEdges": [
{
"from": "tool-server:mcp-bigcommerce-candidate",
"to": "tool:bigcommerce",
"kind": "integrates_with",
"attributes": {}
},
{
"from": "tool-server:mcp-bigcommerce-candidate",
"to": "source-ref:ora-discover-api",
"kind": "sourced_from",
"attributes": {}
},
{
"from": "tool-server:mcp-bigcommerce-candidate",
"to": "role:customer-experience-manager",
"kind": "supports_work",
"attributes": {
"confidence": "medium",
"evidence": "Order and customer context supports customer experience review."
}
},
{
"from": "tool-server:mcp-bigcommerce-candidate",
"to": "workflow:end-to-end-customer-journey-audit",
"kind": "supports_work",
"attributes": {
"confidence": "high",
"evidence": "Commerce event and order state access would support journey reconstruction."
}
}
],
"incomingEdges": []
}