Integrations
MCP · CLI · Skill · SDK
Tools use the same schemas and policy path across HTTP, CLI, MCP, SDK and Skill.
Connect an MCP client
OAuth MCP clients use the server's /mcp endpoint and let the user choose an existing Agent authorization.
Each logical tool appears once. Its target list contains only authorized devices that advertise that tool, and device execution requires the Agent to select one of those targets.
MCP URL
https://adc.zioon.tech/mcpAccess-key MCP
mcp.json
{
"mcpServers": {
"adc": {
"url": "https://adc.zioon.tech/mcp",
"headers": {
"Authorization": "Bearer <ACCESS_KEY>"
}
}
}
}Command line
Run adc login once and confirm the code in your browser. GitHub and email accounts use the same flow.
adc
adc login --url https://adc.zioon.tech
adc access list --json
adc connect ACCESS
adc node list --json
adc tool list --json
adc tool show file.read --json
adc invoke file.read --node node_example \
--args '{"path":"/Users/me/work/README.md"}' --json
adc invocation status INVOCATION_ID --jsonOfficial Skill
Install the complete official Skill directory with your Agent host. It discovers live tools and devices, follows approvals and task results, and never reads device credentials.
Skill
skills/agent-device-cloud/
SKILL.md
references/
account-and-device-management.md
tool-invocation.md