Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Conqueror's Haki Prioritize my app features for launch: login, payments, search, notifications, dark mode. Goal: ship in 2 weeks."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP server that cuts a long list down to the one to three things that actually matter right now.
A Model Context Protocol (MCP) server — one focused tool you plug into an MCP-compatible client (Claude Desktop, Claude Code, Cursor, and others).
Models tend to treat every item on a list as equally worthy of attention. That's the opposite of prioritization. Real prioritization means deciding what to ignore.
Conqueror's Haki takes a list and a single goal, forces a ruthless head-to-head ranking, and eliminates everything that doesn't directly serve that goal.
Related MCP server: Aidderall MCP Server
Give it your backlog and a North Star (e.g. "Launch a paid MVP in two weeks"). It returns:
The Conquered — what was eliminated, each with a one-line reason it's a distraction
The Standing Kings — the survivors, strictly ranked (at most three)
Reason for Dominance — why each survivor earns the focus
Set strictness_level="Overwhelming" to force exactly one survivor.
Tool reference: assert_conquerors_haki(items_to_evaluate: list[str], north_star_goal: str, strictness_level: str = "Supreme King")
No API key, no cost, nothing leaves your machine. The server returns an engineered ranking prompt that your existing model executes — it makes no language-model call of its own.
Requires Python 3.10 or newer.
pip install conquerors-haki-mcpThis installs the conquerors-haki command.
Then register it with your MCP client — either run claude mcp add conquerors-haki -- conquerors-haki,
or add this to the client's config (e.g. claude_desktop_config.json):
{
"mcpServers": {
"conquerors-haki": { "command": "conquerors-haki" }
}
}Restart the client and the tool is available.
Conqueror's Haki is part of a four-tool set. Each tool stands alone, but installing all of them unlocks a final surprise via Laugh Tale.
Package | ||
🗿 | Road Poneglyph | |
⚔️ | Conqueror's Haki · ← this repo | |
⏳ | Toki Toki no Mi | |
🏴☠️ | Laugh Tale |
git clone https://github.com/xfloukiex-lab/conquerors-haki
cd conquerors-haki
python -m venv .venv && . .venv/Scripts/activate # macOS/Linux: source .venv/bin/activate
pip install -e ".[dev]"
python tests/test_conquerors_haki.pyReleased under the Apache-2.0 license. The icon is original artwork
(see icon.svg), generated locally; the repository ships no third-party assets.
This is a fan-inspired project. It is not affiliated with, sponsored by, or endorsed by the creators or rights holders of One Piece (Eiichiro Oda / Shueisha / Toei Animation). "One Piece" and related names are used only as thematic flavour and remain the property of their respective owners.
Exert supreme willpower over a chaotic list of ideas/tasks/features.
Knocks out the weak elements and forces a definitive, ranked priority list against one goal.
Args: items_to_evaluate: Raw list of features, tasks, bugs, or ideas. north_star_goal: The one objective that matters now (e.g. "Launch MVP in 2 weeks", "Get 10 active users"). strictness_level: "Supreme King" → max 3 survivors; "Overwhelming" → exactly 1 survivor.
| Name | Required | Description | Default |
|---|---|---|---|
| items_to_evaluate | Yes | ||
| north_star_goal | Yes | ||
| strictness_level | No | Supreme King |
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so description must disclose behavior. It explains that weak elements are knocked out and a ranked list is forced, with strictness levels controlling survivors. However, it does not state whether the operation is read-only, idempotent, or modifies state, leaving some behavioral ambiguity.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is relatively concise, front-loading with a metaphor and then plain explanation. The 'Args' section is separate and clear. Could be slightly more direct but overall well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (3 params, output schema exists), the description explains the core operation and parameter details adequately. It covers the prioritization logic and strictness levels. While output is not described, the existence of an output schema reduces the burden.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has 0% description coverage, so description must compensate. It provides clear, meaningful explanations for all three parameters: items list, north star goal with examples, and strictness level with defined options. Adds significant value beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states it will produce a ranked priority list from a chaotic list of items, using a goal and strictness level. The verb 'exert willpower' is metaphorical but the action is clear. No sibling tools exist to differentiate, so purpose is clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when there is a chaotic list of ideas/tasks/features needing prioritization against a single goal. However, it does not explicitly state when to use or avoid this tool, nor mention alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.1.0assert_conquerors_hakiOnly one tool exists, so there is no possibility of confusion between tools.
With a single tool, naming is trivially consistent; the name follows a clear verb_noun pattern.
A single tool feels thin for a server, but it serves a focused purpose (prioritization), which is borderline acceptable.
The tool covers its single targeted operation well, but lacks any auxiliary or complementary operations, leaving notable gaps.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Life-balance task manager that prioritises your tasks to restore balance across your life areas.
Mobile-first AI life planner — turn goals into daily, synced tasks from your AI assistant.
Brain dump, routines, task planning, focus, and instant thought retrieval
Turn any goal with a deadline into a private, gamified, evidence-based execution calendar.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/xfloukiex-lab/conquerors-haki'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
