Wallu Now Has an MCP Server: Manage Your Discord Support Bot From Claude Code, Cursor & Co.
If you're a developer, there's a good chance an AI agent already sits in your terminal or editor - Claude Code, Cursor, Codex, whatever you've settled on. Wallu now has a remote MCP server, which means that same agent can manage your Discord support bot directly: read and change settings, update FAQs and documents, and test answers through the real pipeline.
No SDK, no custom integration code. One API key and a config snippet.
The problem this actually solves
Keeping a support bot's knowledge up to date is the chore that always happens after the interesting work. You ship a release, the docs drift a little, and two weeks later the bot is confidently explaining a setting that no longer exists. The fix used to mean opening the panel, finding the right document, editing it by hand.
Now the agent that just helped you write the release can also update the bot. It's the difference between "I should update the FAQs at some point" and adding one sentence to the prompt you were already typing.
Setup
- Create an MCP API key on the addons page (
mcp_...- shown once, treat it like a password). - Add the server to your tool. For Claude Code:
claude mcp add --transport http wallu https://mcp.wallubot.com/mcp --header "Authorization: Bearer YOUR_MCP_KEY"
For Cursor, Codex and most other clients it's the usual mcpServers JSON:
{
"mcpServers": {
"wallu": {
"url": "https://mcp.wallubot.com/mcp",
"headers": { "Authorization": "Bearer YOUR_MCP_KEY" }
}
}
}
The key is bound to one Discord server, so there's nothing else to configure. It works on all plans, including free. Full details in the docs.
What you can actually use it for
"We just shipped - update the bot"
Paste your changelog into your agent and say: "We released v2.0, here's what changed - update our Wallu FAQs and documents accordingly." The agent can search your existing knowledge base first, so it edits the entries that became wrong and adds what's missing instead of piling up duplicates. This is the workflow we built the server around: support knowledge stops being a separate maintenance task and becomes a line item in your release routine.
Keeping knowledge in sync with your codebase
A while ago I wrote about generating how-to docs from your code with AI agents. The workflow ended with
"save the file and upload it to Wallu". That manual step is gone now: the same agent that sweeps your repo and writes the how-tos can push them straight
to Wallu with the upsert_document tool.
Upserts are idempotent (documents are matched by a stable ID you choose), so re-running is always safe - which makes this CI-friendly. On every release,
have your coding agent regenerate the docs that changed and upsert them. Then have it call test_bot_answer with a question a real user would ask, to
verify the bot actually picks up the new content.
First-time setup
If you're new to Wallu, you can skip most of the clicking around: "Import our help center at example.com/help into Wallu" or "Look at my Wallu server and set it up to only answer in the support channels." The MCP server exposes every setting with an inline explanation, so your AI reads the current config, explains what a setting does, and changes it - you just approve.
(If you'd rather do this inside Discord instead of your editor, that's what the Setup Agent is for. The MCP server is the same idea pointed the other way: instead of our agent in your Discord, it's your agent connected to Wallu.)
Debugging wrong or missing answers
"Why isn't Wallu answering questions about refunds? Fix it." The agent searches your knowledge base, notices there's nothing about refunds (or that the
one FAQ about it is ambiguous), fixes it, and verifies with a test question through the real answer pipeline. One honest note: test_bot_answer consumes
credits exactly like a real answered question, because it is a real answered question.
Bulk work over the HTTP API
For big jobs - export every document to files, run a find-and-replace across all of them, sync everything back - going document-by-document over MCP is
slow. Your mcp_ key also works on the plain HTTP API, so the agent can script bulk operations with
curl instead. (Caveat: MCP keeps the key hidden from the AI, but raw HTTP calls need the key in the request, so for this you hand the key to the agent,
e.g. as an environment variable.)
What it deliberately can't do
MCP keys are more limited than a panel login, on purpose:
- Documents can be deactivated but not permanently deleted - hard deletes stay in the panel.
- No access to API key management, custom bot tokens, billing, or data exports.
- Imported sources (Discord channels, websites, Git repos) keep syncing from their origin and can't be hand-edited over MCP.
- Everything is rate-limited per key, and every change shows up in your panel audit log.
Destructive tools (removing FAQs, deactivating documents, config changes) are marked as such, so well-behaving MCP clients ask you before running them. And if a key leaks, revoke it on the addons page - it only ever had access to that one server.
It's a beta
This is new and we're still shaping it based on what people actually do with it. If you wire it into a release pipeline, hit a rough edge, or build a workflow we didn't think of, tell us in the support Discord - that feedback directly decides what we build next.
Setup instructions and the full tool list live in the MCP docs.
