woku AI Toolkit

Connect your AI agent to woku, the voice-of-customer platform.

The toolkit gives your agent woku's full tool catalog through woku's MCP server, plus the woku method so it acts as a customer-experience consultant: design a listening program for your customer journey, place the fast VoC instruments (NPS, CSAT, CES, wokus) at each moment of truth, and turn every signal into a support ticket or an action plan.

It bundles:

• The woku MCP server connection (https://api.woku.app/mcp), so the agent gets the live catalog with woku's OAuth. No API keys to copy.
• The woku skill, which primes the agent with the method and tells it to call woku_guide first.
• The woku SDK skills for JavaScript (@wokuapp/sdk) and Python (woku), so the agent can build server-side woku integrations in code (create tools, send surveys, read responses, drive tickets and action plans) over the public /v1 API.

The live tools/list response is authoritative. The catalog focuses on journeys, feedback instruments, clients, trackers, instrument reports and action plans. Data Studio and support tickets are Corporate capabilities.

Install

Claude Code

Add woku's marketplace, then install the plugin. This ships both the MCP server and the skill:

/plugin marketplace add wokuApp/woku-ai-toolkit
/plugin install woku@woku-ai-toolkit

Once the toolkit is accepted into the official marketplace, /plugin install woku@claude-plugins-official also works.

OpenAI Codex

Add the woku MCP server to ~/.codex/config.toml and authenticate:

[mcp_servers.woku]
url = "https://api.woku.app/mcp"

codex mcp login woku

auth = "oauth" is the default for a bare url, so Codex opens the browser to complete woku's OAuth. Check it with codex mcp list.

OpenCode

Add the woku MCP server to your opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "woku": {
      "type": "remote",
      "url": "https://api.woku.app/mcp",
      "enabled": true
    }
  }
}

OpenCode runs OAuth automatically on the first authenticated call. To start the login yourself, run opencode mcp auth woku.

OpenClaw

Install the plugin (this ships the woku skill):

openclaw plugins install npm:@wokuapp/ai-toolkit

You can also install from the git repository with openclaw plugins install git:github.com/wokuApp/woku-ai-toolkit.

OpenClaw's plugin manifest declares local MCP servers only, so add woku's remote MCP server (https://api.woku.app/mcp) through your OpenClaw MCP configuration.

Pi

The package exposes the woku skill through Pi's pi package convention. Install @wokuapp/ai-toolkit from npm in your project and Pi loads the skill. Add woku's MCP server (https://api.woku.app/mcp) through Pi's MCP configuration.

claude.ai and ChatGPT

These are configured from the app, not from a package. Add a custom connector (claude.ai) or a developer-mode connector (ChatGPT) with the URL https://api.woku.app/mcp.

Any other MCP client

Point it at https://api.woku.app/mcp and approve access from your woku account.

See the connect guide and the agent guide for details.

What you get

Once connected, ask your agent things like:

• "I run an ecommerce, how do I start listening to my customers with woku?"
• "Design a VoC program for my customer journey."
• "How is my NPS this month, and should I open an action plan?"
• "Summarize last week's reviews and the top improvement themes."

Every connection is bound to one company, chosen when you approve access. Read tools need no special permission; write tools require the mcp:write scope, and destructive tools or sends require an explicit confirmation.

License

MIT. See LICENSE.

Periods, search and sends update (0.4.0)

The woku skill follows the admin period picker, search box and Sends tab: from/to on get_woku_report, get_folder_report and get_company_nps_report (the period report is generated on demand), a custom from/to range on get_folder_tools_metrics, q text search on list_woku_reviews, list_nps_responses, list_csat_responses and list_ces_responses, and the read-only invitations toolset (get_invitation_stats, list_invitations_by_tool, list_invitation_recipients). The report tools add get_nps_tool_report, get_csat_report and get_ces_report, and take regenerate. The SDK skills drop quarantines. Verify the server and SDK releases before using them.

Folders and tools update (0.3.0)

The skills now cover the folder tree that holds wokus and NPS, CSAT and CES tools: the MCP tools search_voc_tools (with tracker chips), get_voc_tools_stats, get_folder_tools_metrics, move_voc_tools, update_folder, delete_folder, get_folder_report (scope: "all", format: "csv"), get_journey_folders_status, organize_journey_folders, flow steps in create_flow and update_flow, folderId on the create_*_tool tools, the organize_listening playbook of woku_guide, and the SDK folders and tools resources in JavaScript and Python. Verify the installed SDK and server release before using them.

Journey guidance update (0.2.2)

The bundled skills now route coordinated evaluations through journeys, preserve a reviewed MCP proposal, explain local media capabilities by host, and cover the v4 SDK media and enrollment iterators. They distinguish protected retries from other writes and use variable fragments for NPS questions. Verify the installed SDK release before using journey and media methods.

Local media by host

• Codex and Claude Code upload local files through multipart POST /v1/woku-media or the backend SDK. The remote MCP tool accepts a public HTTPS URL or a supported host-authorized file, never a local path or image bytes pasted as model text. Never put a company secret key in frontend code.
• ChatGPT and Claude web attachment access depends on the host and connector. Use only file references that the connected tool can actually read, or a genuinely public HTTPS URL. Do not invent a URL for a private attachment or promise that every host forwards its uploaded files automatically.
• Check the live tool schema and the customer_journeys playbook before choosing the representation. Upload first, then use its fileId in the reviewed proposal.