Chatcone

Active

An AI agent for Chatcone. It works in a scene with a live connection to Chatcone. It asks before it writes, and every run is traced.

Connect Chatcone, Thailand's omnichannel chat and AI-chatbot platform (LINE OA, Facebook, Instagram, web widget, marketplaces), to read your channel and rich-menu configuration and taxonomy, and to map and tag contacts against your own customer ids through the official Open API.

Communication API Key 2 asset types

What you can connect

Add these to your scene and AI gets access.

Chatcone Account Chatcone Accounts

A connected Chatcone account

Name

Guide Guides

Chatcone setup guides, troubleshooting, and reference — pin one to read it in-scene, or ask the agent.

TitleSummary

Connect Chatcone over MCP

Daslab is itself an MCP server.

Connect Chatcone in a scene, then pin that scene's URL in Claude Code, Cursor, or any MCP client. The agent there gets your Chatcone tools, and your approval gate and trace travel with them.

https://daslab.run/mcp/<your-world>/<your-scene>

One scene can hold Chatcone and everything else you connect, so a single endpoint carries them all. Set up a client.

Use cases

List the channels and rich-menu layouts configured on a workspace
Read the chat-label taxonomy used to segment contacts
Map a LINE or Facebook user to a customer id and tag them

Knowledge base

Connecting a Chatcone workspace api-access
The API key and Company ID, where each comes from, the per-channel channel key, and the two Chatcone surfaces (Open API v3 and Platform API v2).
What the API key can and cannot do scope-and-limits
Configuration reads and contact tagging work with an API key; contact lists and message history do not — those need an agent session token or a portal export. New messages arrive via the outbound webhook only.

Ships with the integration — agents read these with docs_read, before the account is connected. Knowledge bases →