About declaude
declaude rewrites Claude-style wording into plain English while retaining meaning, code, and structure. It is for users who want concise text from an MCP client, Claude Code hook, document workflow, or API; text is processed in memory and not logged.
Key features
- 01Removes filler and hedging
- 02Preserves meaning and structure
- 03Keeps code intact
- 04Rewrites documents
- 05Offers Claude Code response hook
- 06Processes text without prompt logging
Use cases
- 01Trim verbose assistant replies
- 02Rewrite Markdown or text documents
- 03Automatically revise Claude Code responses
MCP support
The MCP server provides `translate` and `usage` tools to MCP clients. It supports HTTP connection with OAuth sign-in.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://speak-english.tenken.co/mcpclaude mcp add --transport http tenkenco-declaude https://speak-english.tenken.co/mcp{"mcpServers":{"tenkenco-declaude":{"type":"http","url":"https://speak-english.tenken.co/mcp"}}}Open in Cursor{"servers":{"tenkenco-declaude":{"type":"http","url":"https://speak-english.tenken.co/mcp"}}}Open in VS Code{"mcpServers":{"tenkenco-declaude":{"type":"http","url":"https://speak-english.tenken.co/mcp"}}}{"mcpServers":{"tenkenco-declaude":{"serverUrl":"https://speak-english.tenken.co/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEdeclaude
Claude-English → plain English, as a service.
Strips sycophantic openers, hollow superlatives and hedging filler.
Meaning, code and structure survive intact.
Before "Great question! Before I answer, let me make sure I understand what
you're asking. You want to know why the build is failing. Let me walk
through my thinking, and then I'll give you the answer."
After "I understand you want to know why the build is failing. Here's what
I think is happening."
Before "One thing I didn't touch, but you won't want to leave hanging, is the
migration script. I'd be happy to walk you through it whenever you're
ready!"
After "One thing I didn't cover is the migration script. When you're ready,
I can go through it with you."
Runs on an open-source model (Qwen2.5-14B-AWQ) on our own L4 GPUs, so your text never reaches a commercial AI provider. Prompt logging is disabled at the model server: text is processed in memory and discarded, never written to disk, a database, or logs.
Live: speak-english.tenken.co · Get an API key · Translate a document
| Free | $5 / month | |
|---|---|---|
| Translations | 100 / month | Unlimited |
| Documents | 5 / month, 200 KB | 500 / month, 2 MB |
| Card required | No | Yes |
Quick start
In Claude Code, install the plugin. It brings the skill and registers the hook:
/plugin marketplace add tenkenco/declaude
/plugin install declaude@tenken
Then run /declaude:setup. It safely migrates any manual hook and configures a dk_ key.
Claude Code stores the key in secure plugin configuration. The hook rewrites replies as soon
as a key exists. Set the hook_enabled option to false to stop it. The hook stays silent
without a key, and it never blocks a session.
For the MCP server on its own, in Claude Code or any other MCP client:
claude mcp add --transport http declaude https://speak-english.tenken.co/mcp
No API key to paste: your client discovers OAuth, opens a browser sign-in, and holds the token. That is the whole setup.
| Surface | Use it for | Docs |
|---|---|---|
| MCP server | Claude Code, Cursor, any MCP client. Tools: translate, usage | skill |
| Claude Code hook | Rewrites replies as they render, costs zero Claude tokens. The plugin registers it | hook/ |
| Documents | Drop a .md/.txt, get it back rewritten | web |
| REST API | POST /v1/translate, /v1/documents, /v1/usage | skill |
| OpenAI-compatible | POST /v1/chat/completions — point any OpenAI client at /v1 | skill |
Full usage, authentication and quota behaviour live in skills/declaude/SKILL.md — installable as an agent skill, so your agent can read it directly.
Architecture
client ── API key / OAuth / Clerk JWT ──> Cloud Run gateway ── VPC ──> internal LB ──> vLLM GPU MIG
│ (Qwen2.5-14B, spot L4)
├─> Firestore (usage, paid flags, key hashes)
└─> Stripe (payment link + signed webhooks)
- gateway/ — FastAPI. Every boundary is injectable, which is why the suite runs without network, GPU or cloud credentials.
- infra/ — Terraform, state in GCS, plan converges to zero diff. The GPU tier is private-IP spot instances behind an internal L7 load balancer.
- hook/ — Claude Code hook client. Fails open; never blocks a session.
- hooks/ —
hooks.json, the plugin registration Claude Code reads on install. - CI — lint, tests and coverage on every PR; security scans and a production smoke test daily.
Operating notes
/healthzis reserved by Google Frontend on run.app — use/health.- Model swaps are one Terraform variable; 32B needs 2×L4 (quota bump), 14B fits one L4.
- MIG template rollouts are deliberate (
OPPORTUNISTIC): a proactive policy turned benign template edits into surprise 15-minute outages. - Secrets live in Secret Manager only. API keys are stored as SHA-256 digests, so a database leak yields no usable credential.
- Prompt logging is disabled at the model server; request text is processed in memory and discarded.
- Developed test-first. Every production defect found while dogfooding became a regression test before its fix.
Development
cd gateway
uv sync --dev
uv run pytest -q # 197 tests
uv run ruff check .
Credit
Grew out of gvzdv/claudish-to-english, the original local-Ollama hook. Licensed MIT; upstream notice in THIRD_PARTY_LICENSES.md.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.