II.
ToolServer JSON
Structured · livetool-server:mcp-loops-candidate
Loops MCP candidate json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "tool-server:mcp-loops-candidate",
"_kind": "ToolServer",
"_file": "extensions/tool-servers/ora-operations-mcp-candidates.yaml",
"_cluster": "extensions",
"attributes": {
"displayName": "Loops MCP candidate",
"description": "Candidate MCP server for Loops contacts, transactional messages, campaigns, and email automation. Recorded from Ora discovery as a missing MCP/tool-server coverage point.\n",
"protocol": "mcp-stdio",
"provenance": "custom",
"category": "marketing",
"maintainer": "Candidate",
"sourceRef": "source-ref:ora-discover-api",
"candidateStatus": "needs-source-verification",
"ora": {
"domain": "loops.so",
"score": 71,
"grade": "B"
}
},
"outgoingEdges": [
{
"from": "tool-server:mcp-loops-candidate",
"to": "tool:loops",
"kind": "integrates_with",
"attributes": {}
},
{
"from": "tool-server:mcp-loops-candidate",
"to": "source-ref:ora-discover-api",
"kind": "sourced_from",
"attributes": {}
},
{
"from": "tool-server:mcp-loops-candidate",
"to": "role:marketing-manager",
"kind": "supports_work",
"attributes": {
"confidence": "medium",
"evidence": "Campaign and audience APIs support lifecycle marketing automation."
}
},
{
"from": "tool-server:mcp-loops-candidate",
"to": "workflow:customer-marketing-campaign",
"kind": "supports_work",
"attributes": {
"confidence": "medium",
"evidence": "Email automation data supports customer campaign analysis."
}
}
],
"incomingEdges": []
}