Skip to content
Back to search

duoke-mcp

Local stdio MCP server for Duoke (ai.duoke.com) — inbox, orders, customers. Per-user browser session, guarded writes.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/krpx0341--duoke-mcp/badge.svg)](/listings/krpx0341--duoke-mcp)

HTML

<a href="/listings/krpx0341--duoke-mcp"><img src="/api/listings/krpx0341--duoke-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

git clone https://github.com/krpx0341/duoke-mcp.git
cd duoke-mcp
python3 -m venv .venv
. .venv/bin/activate
pip install -r requirements.txt
chmod +x duoke-mcp login.sh server.py

No browser download is required. Server uses installed Chromium or Chrome.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 173 lines
  1. # Duoke MCP
  2. Local MCP server for [Duoke](https://ai.duoke.com/). Gives Grok/GrokBot compact domain tools for reading customer conversations, replying with explicit confirmation, and searching orders or customers.
  3. This integration drives Duoke through an isolated Chromium profile. Each operator signs in with their own Duoke account. Browser sessions are never shared or committed.
  4. ## Tools
  5. | Tool | Mode | Purpose |
  6. | --- | --- | --- |
  7. | `status` | Read-only | Check browser session and login state |
  8. | `list_inbox(limit=20, unread_only=false)` | Read-only | List recent conversations |
  9. | `read_conversation(index=0, limit=30)` | Read-only | Read recent messages from one conversation |
  10. | `send_reply(index, text, confirm=false)` | Write | Preview by default; sends only when `confirm=true` |
  11. | `search_orders(query, limit=20)` | Read-only | Search orders by visible ID, buyer, store, phone, or product text |
  12. | `search_customers(query, limit=20)` | Read-only | Search customers by visible name, account, email, phone, or platform ID |
  13. ## Requirements
  14. - Linux
  15. - Python 3.11+
  16. - Chromium or Google Chrome
  17. - Grok CLI/GrokBot with local stdio MCP support
  18. - Duoke account
  19. If Chromium is not on `PATH`, set `DUOKE_CHROMIUM` to its executable path.
  20. ## Install
  21. ```bash
  22. git clone https://github.com/krpx0341/duoke-mcp.git
  23. cd duoke-mcp
  24. python3 -m venv .venv
  25. . .venv/bin/activate
  26. pip install -r requirements.txt
  27. chmod +x duoke-mcp login.sh server.py
  28. ```
  29. No browser download is required. Server uses installed Chromium or Chrome.
  30. ## Authenticate
  31. ```bash
  32. ./login.sh
  33. ```
  34. Sign in to Duoke in opened browser, confirm inbox is accessible, then close browser. Login state stays in local `browser-profile/` directory.
  35. Never copy or commit `browser-profile/`. Every operator must authenticate their own account.
  36. ## Register with Grok/GrokBot
  37. ```bash
  38. grok mcp add duoke -- "$(pwd)/duoke-mcp"
  39. grok mcp doctor duoke --json
  40. ```
  41. Expected doctor result:
  42. - server started
  43. - handshake OK
  44. - 6 tools discovered
  45. Restart Grok/GrokBot if it does not hot-reload MCP configuration.
  46. ## Agent operating guide
  47. Agents should follow this sequence:
  48. 1. Call `status` before first domain operation.
  49. 2. Call `list_inbox` before `read_conversation` or `send_reply`.
  50. 3. Treat returned conversation `index` as temporary UI position, not durable ID.
  51. 4. Call `send_reply` first with `confirm=false` to produce preview.
  52. 5. Ask human to approve exact conversation and message.
  53. 6. Call `send_reply` again with identical arguments and `confirm=true`.
  54. 7. Never claim reply succeeded unless tool returns `sent: true`.
  55. 8. Keep `limit` small unless broader retrieval is necessary.
  56. Example agent requests:
  57. ```text
  58. Use Duoke. Check status, then list 10 unread conversations.
  59. Read conversation index 0 and summarize customer intent. Do not reply.
  60. Preview this reply for conversation index 0: "Pesanan sedang kami cek."
  61. Do not send until I approve.
  62. Search orders for "ORDER-12345" and return only matching rows.
  63. ```
  64. ## Manual MCP configuration
  65. Equivalent entry in `~/.grok/config.toml`:
  66. ```toml
  67. [mcp_servers.duoke]
  68. command = "/absolute/path/to/duoke-mcp/duoke-mcp"
  69. startup_timeout_sec = 30
  70. tool_timeout_sec = 120
  71. ```
  72. Then run:
  73. ```bash
  74. grok mcp doctor duoke --json
  75. ```
  76. ## Troubleshooting
  77. ### `Duoke session not logged in`
  78. Run `./login.sh`, finish login, close browser, then retry.
  79. ### Browser profile is locked
  80. Close browser opened by `login.sh` before calling MCP tools. Only one Chromium process can own profile at a time.
  81. ### Chromium not found
  82. ```bash
  83. export DUOKE_CHROMIUM=/path/to/chromium
  84. ```
  85. Keep variable available to MCP process. For Grok config:
  86. ```toml
  87. [mcp_servers.duoke]
  88. command = "/absolute/path/to/duoke-mcp/duoke-mcp"
  89. env = { DUOKE_CHROMIUM = "/path/to/chromium" }
  90. ```
  91. ### Tools are discovered but return no rows
  92. Duoke changes UI selectors occasionally. Verify account can access target page in `./login.sh`, then open an issue with:
  93. - Duoke language
  94. - failing tool name
  95. - visible page section
  96. - sanitized error text
  97. Do not attach cookies, profile files, customer conversations, or credentials.
  98. ## Security
  99. - `browser-profile/` contains authenticated session material and is gitignored.
  100. - `send_reply` requires `confirm=true`.
  101. - Package exposes domain tools, not generic browser click or arbitrary JavaScript execution.
  102. - Each installation belongs to one operator and one Duoke session.
  103. - Do not expose this stdio server as shared network service.
  104. ## Verification
  105. ```bash
  106. python -m py_compile server.py
  107. bash -n login.sh duoke-mcp
  108. grok mcp doctor duoke --json
  109. ```
  110. After setup and login:
  111. 1. `grok mcp doctor duoke --json` → handshake OK + 6 tools.
  112. 2. In Grok: "Use Duoke MCP. Call status and list_inbox."
  113. 3. Confirm `status.logged_in` is true and inbox returns rows.
  114. Protocol discovery does not prove live Duoke behavior. Complete verification requires authenticated `status`, one real read call, and an approved low-risk reply test.
  115. ## Current limitations
  116. - Browser automation depends on Duoke UI labels/selectors.
  117. - Conversation indices can change when inbox order changes.
  118. - Designed for one operator, one process, one Duoke browser profile.
  119. - Linux launcher only.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.