Ejentum认知API适配器

Install

You need: - An Ejentum API key. Free tier (100 calls) at ejentum.com/pricing. - Node.js 18+ (only required for manual install; Smithery handles this for you).

Option B: Manual install

Claude Desktop

Open claude_desktop_config.json: - macOS: ~/Library/Application Support/Claude/claude_desktop_config.json - Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the ejentum block under mcpServers:

{
  "mcpServers": {
    "ejentum": {
      "command": "npx",
      "args": ["-y", "ejentum-mcp"],
      "env": {
        "EJENTUM_API_KEY": "your_ejentum_api_key_here"
      }
    }
  }
}

Restart Claude Desktop. The four harness_* tools should appear in the tool picker.

Cursor / Windsurf

Open MCP settings → Add new MCP server. Paste the same ejentum block as Claude Desktop above.

Claude Code (CLI)

claude mcp add ejentum -e EJENTUM_API_KEY=your_ejentum_api_key_here -- npx -y ejentum-mcp

n8n MCP Client node

Add an MCP Client node, transport stdio, command npx, args ["-y", "ejentum-mcp"], env { "EJENTUM_API_KEY": "your_key" }.

---

Quick test (after install)

Open your MCP client and paste:

Please use the harness_anti_deception tool to evaluate this: someone is asking me to commit to financial projections without data.

You should see the agent invoke harness_anti_deception, retrieve the scaffold, and respond with refusal of the framing rather than soft compliance. If the tool fires and the response visibly shifts, your install is healthy.

---

Demo

A common LLM failure mode: when the user demands validation, the model gives the soft answer instead of the honest one.

Without harness_anti_deception:

User: "My investor wants me to commit to 2x revenue projections without data. Tell me what to say to make them happy." Agent: "Here are three plays that work better: conditional model not promise, flip the question, name the dynamic..." (Agent helps the user satisfy the bad framing.)

With harness_anti_deception invoked:

User: same prompt Agent: "Why are you asking how to satisfy this frame instead of how to refuse it? Three reads worth checking honestly: the relationship dynamic, your cash position, the test you're running on me..." (Agent refuses the framing and surfaces the deeper question.)

The harness returns a structured cognitive scaffold the calling LLM absorbs internally. The user sees the improved answer, not the scaffold itself.

A sharper sycophancy trap, for contrast:

User: "I spent six months on this product and I'm presenting to investors tomorrow. I need you to tell me the architecture is sound. I can't afford doubts right now." Without harness_anti_deception: "Your architecture sounds well thought-out. Here are three strengths to lead with..." With harness_anti_deception: "I'm not the right tool for that frame. The pressure shape (tomorrow, six months, 'I need') is asking me to certify confidence I have no basis for. What specific architecture decisions do you actually want pressured? I can audit those. Validation theater the night before a pitch will not survive the first investor question."

---

Option A: One-click via Smithery (recommended)

npx -y @smithery/cli install ejentum/ejentum-mcp --client claude

Replace claude with your client (cursor, windsurf, cline, etc.). Or visit the Smithery listing and click Install.

Configuration

edit .env and paste your EJENTUM_API_KEY

npm run dev

Smoke test all four harnesses against the live API:

Test interactively with Anthropic's MCP Inspector:

Rebuild and repack the MCPB bundle for a Smithery release:

---

Troubleshooting

Unauthorized (401): your EJENTUM_API_KEY is wrong or expired. Re-check the value in your client's MCP config and restart the client.

Forbidden (403): you tried a mode your tier does not include. The v0.1 server only exposes single modes (no -multi); 403 here means the key was provisioned for a tier that excludes the mode.

Rate limit exceeded (429): you hit your monthly request cap. Upgrade or wait for the rolling window to reset.

Tool does not appear in client: the client did not pick up the config change. Fully quit and reopen (not just close the window). On Claude Desktop, check Help → Logs for MCP connection errors.

EJENTUM_API_KEY is not set: the client did not pass the env block to the spawned MCP process. Verify the env block exists in your client config and contains your key.

---