SEFAZ ES DEC: Caixa Postal

I'll use "サーバーのMCP" or "MCP サーバー".

---

One important thing: The output should not include Markdown code fences. I will leave the raw translated markdown only.

Let me double-check every element in the original is present and in order.

Original:
1. `# SEFAZ ES DEC: Postal` → present.
2. blank line.
3. `### SEFAZ ES DEC: Caixa Postal para Claude, ChatGPT e agentes de IA` → present. My heading: "### SEFAZ ES DEC: Postal（Claude、ChatGPT、AIエージェント向け）" - hmm the original has "para Claude, ChatGPT e agentes de IA" meaning "for Claude, ChatGPT and AI agents". My rendering "（Claude、ChatGPT、AIエージェント向け）" works. The product name retained. OK.

4. blank.
5b. Paragraph. Present.
6-9. Bullets. Present.
10. Links line. Present (with `***` lines? Wait original has "***" then links? No, the links line, then `***`. Actually after links line, there's `***`. Let me check: Original order: after bullets, "[English version](README.en.md) · [Documentação completa](docs/) · [Skill pra agentes](skills/)" then "***" then "## Instalar em 1 clique". Yes, we have that.

11. `***`. Present.
12. `## Instalar em 1 clique`. Present.
13. `### Claude (Web e Desktop)` -> "### Claude（Web・Desktop）". Present.
14. Paragraph. Present.
15. link line. Present.
16. `**Manual** (se o deeplink não abrir): ...` paragraph. Present.
17. `### Cursor`. Present.
18. link line. Present.
19. `### VS Code（Copilot Chat）`. Present.
20. link line. Present.
21. `### ChatGPT, Manus, OpenClaw e mais 40+ clientes`. Present.
22. paragraph "Funciona em qualquer cliente MCP ..." Present.
23. line "GXP1". Present.
24. "クライアント別..." line. Present.
25. `***`.
26. `## Exemplos use`.
27. `GXP2`.
28. `***`.
29. `## 1 tool available`, table.
30. Detal track.
31. `***`.
32. `## Preços`, etc.
33. `***`.
34. `## Privacidade & LGPD` bullets.
35. `***`.
36. `## Perguntas frequentes`.
37-39. Q&A.
40. `***`.
42. `## Suporte`.
43. bullets.
44. `***`.
45. `## Licença`.
46. text.

Good.

Another detail: The `***` lines are thematic break. Keep them exactly as `***`.

There's a bullet line: **Sub-processadores**: does it have a colon. I need to keep emphasis markers `**...**`.

The bullet 2 of privacy: `* Os dados retornados pelas tools são enviados ao **LLM host que você escolher**, sub-processador fora do nosso controle. Recom Back ... with opt-out`.

In my translation, I need to reflect "for our control" etc.

Let me carefully translate Bullet 2: "Os dados retornados pelas tools são enviados ao **LLM host que você escolher**, sub-processador fora do nosso controle. Recomend plans with opt-out of training."

=> "ツールが返したデータは、選択した**LLMホスト**（当社の対立するサブプロセッサー）に送信されます。トレーニングのオプトアウトが利用できるプランをお勧めします。"

But "sub-processador fora do nosso controle" = "sub-processor outside our control". So Japanese: "当社の管理範囲外のサブプロセッサー". Hmm "outside our control" - "our control scope" - OK.

I'll write: "ツールが返すデータは、選択した**LLMホスト**（当社の管理外であるサブプロセッサー）に送信されます。学習利用をオプトアウトできるプランをお選びください。"

Maybe "sub-processor" in LGPD context is "subprocessador". In Japanese data protection, it's "sub-processor" (サブプロセッサー). OK.

Also bullet 1: "**Sub-processores**: o LLM host que you escolher (Claude, GPT, Cursor, agente próprio), full list in ..." 

"LLM host que você escolher" - Japanese: "選択するLLMホスト". "ホスト" is the hosting provider, e.g., Anthropic (Claude?) Actually LLM host here means the LLM provider you are using (Claude, ChatGPT, etc.) that hosts the LLM. Keep "LLMホスト".

So bullet 1: "* **サブプロセッサー**: あなたが選ぶLLMホスト（Claude、ChatGPT、Cursor、独自エージェント）。完全なリストは [docs/privacidade-lgpd.md](docs/privacidade-lgpd.md) にあります。"

Just to be safe, "at full in [..]" - "完全なリストは" .

Now finalize the punctuation and line breaks.

I need to ensure each Markdown table row has exact `| content | content |` structure.

In the table row, the description would be "SEFAZ, CAIXA POSTAL"... Let's choose: "SEFAZ ES DEC: Caixa Postal、公式 source를通した照会。" Hmm maybe "公式ソースに基づく" (based on official source). Yet "em frota" = "in official". I'll use "公式ソースでの照会". Since the intro phrase also "consulta em source official"; use same for consistency: "SEFAZ ES DEC: Caixa Postal は公式ソースでの照会サービスです。" In table, maybe just "SEFAZ ES DEC: Caixa Postal、公式ソースでの照会です。"

OK.

For the line "A Anthropic unificou a 설치..." - maybe "Anthropic は MCP の installationを `claude.ai/customize/connectors` にまとめました". "unificou" = unified/consolidated. "一元化". I'll use "一元化しました".

Also, I should preserve the anchor part in the deep link: `...customize-connector#settings/customize-connectors`. It's a URL with anchor. Keep whole URL exactly.

Now, word order in the heading "### SEFAZ ES DEC: Caixa Postal（Claude、ChatGPT、AIエージェント向け）". Good.

Maybe "向け " could be "のための" . Keep "向け".

Now for "## 1クリックでインストール" - emoji? The original heading has no emoji. Fine.

Now "It is safe? Use contact: " "📧" - keep.

Now, let me examine if the source includes "GXP1" and "GXP2" as placeholder tokens and whether they should be "kept". Yes.

Maybe I should also check if "magic-link" is a product? No.

Now produce the final output. Let's compose carefully with markdown.

One thing: In the "Manual" paragraph, the original: `cole **Nome** `...` e **URL** `https://...`` . The Japanese: "**名前** に `SEFAZ ES DEC: Caixa Postal`、**URL** に `https://api_mcp` を貼り付けます。"

However, the phrase "cole [Name] and [URL]" - the expected: "「名前」に「SEFAZ ES DEC: Caixa Postal」を、「URL」に「https://...」を入力します". Let me finalize:

"**手動設定**（如果想在 деплинк не открылся да): [claude.ai/customize/connectors](https://claude.ai/customize/connectors?surface=cowork) → **+** → **カスタムコネクターを追加** → **名前** に `SEFAZ ES DEC: Caixa Postal`、**URL** に `https://api.mcp.ai/p_sefaz_es_dec_caixa_postal` を貼り付けます。"

Hmm "deeplink" in Portuguese doesn't contain backticks. Fine.

Also "manual" can be "手動" but stands "Manual" - OK.

Now let's write the final output. Ensure there are no extra newlines issues. I'll use normal blank lines between blocks, following the original.

Let me compose the entire output:

---

# SEFAZ ES DEC: Caixa Postal

### SEFAZ ES DEC: Caixa Postal (Claude、ChatGPT、AIエージェント向け)

SEFAZ ES DEC: Caixa Postal は、公式ソースを検索するサービスです。プラットフォームでホストされているなので、プラットフォームの認証情報は不要で、プリペイド残高による照会ごとの支払いです。

* 📊 **1つのツール**
* ✏️ **読み書き**
* 💬 **あらゆるMCPクライアントで動作**: Claude Desktop、Cursor、VS Code、Cline、Continue
* 🔑 **マジックリンクでログイン（パスワード不要）**

[英語版](README.en.md) · [完全なドキュメント](docs/)) · [エージェント向けスキル](skills/)

---

Wait, there is a tiny issue: "公式ソースを照会するサービスです" - "consulta em fonte oficial" = "query from official source" - get the Portuguese meaning right: "inquiry/consultation made in the official source". Japanese: "公式ソースを使用した照会" better. Let me use "公式ソースへの照会" or "公式ソースに対する照会". Actually "consulta em" = search on the official source. Since you pay "por consulta" – "abilityコンサルティング". So "公式ソースでの検索". I think "照会" is good. Use "公式ソースを照会照会するサービス" maybe "公式ソースでの照会サービス". So the first sentence: "SEFAZ ES DEC: Caixa Postal は、公式ソースでの照会サービスです。" Good. Then follow.

Actually original sentence had "SEFAZ ES DEC: Caixa Postal, consulta em fonte official." The product name is subject. In Japanese: "SEFAZ ES DEC: Caixa Postal は、公式ソースでの照会サービスです。"

Then: "プラットフォームがホストするため、プラットフォームの認証情報は不要で、プリペイド残高で照会ごとに支払います。" 

All good.

Now, bullet: "💬 **Funciona com qualquer cliente MCP**: Claude Desktop, Cursor, VS Code, Cline, Continue" - translated. "**あらゆるMCPクライアントで動作**: ..." 

Now link line: "[English version](README.en.md) · [Documentación completa](docs/) · [Skill para agentes](skills/)" - I have "[英語版](README.en.md) · [完全なドキュメント](docs/) · [エージェント向けスキル](skills/)".

"***" symbol present.

OK.

Now "Installing in Rust": The heading "### Claude（Web・Desktop）" - the Portuguese "Web e Desktop" aka variants of Claude access (Claude.ai web vs desktop app). "### Claude（Web / Desktop）". Fine.

Paragraph: "Anthropic は MCP のインストール先を `claude.ai/customize/connectors` に統一しました。**同じリンクがClaude Web と Claude Desktop の両方で使えます**（ログインしていればOK）："

Maybe "インストール先を...に統一" - nuance "unificado". I'd say "Anthropic は MCP のインストールを `claude.ai/customize/connectors` に統合しました" is natural.

Also "the same link serves for Claude Web and Claude Desktop" - "同じリンクがClaude WebとClaude Desktopの両方で使えます". Good.

".)。

Link: "[➕ Claude で開いて接続](https://claude.ai/new?modal=add-custom-connector#settings/customize-connectors)" - Keep emoji, text.

---

Manual:

"**Manual** (if deeplink doesn't open):" Translation: "**手動設定**（ディープリンクが開かない場合）："

Or "manual" maybe "マニュアル" - Better "手動" seems right.

Then [claude.ai/customize/connectors](https://claude.ai/customize/connectors?surface=cowork) → **+** → **カスタムコネクターを追加** → **名前** に `SEFAZ ES DEC: Caixa Postal`、**URL** に `...` を貼り付けます。"

Maybe "対する" -- no.

---

Cursor link:

`[➕ CursorにSEFAZ ES DEC: Caixa Postalをインストール](cursor://anysphere.cursor-deeplink/mcp/install?name=sefaz_es_dec_caixa_postal\&config=eyJ1cmwiOiJodHRwczovL2FwaS5tY3AuYWkvcF9zZWZhel9lc19kZWNfY2FpeGFfcG9zdGFsIn0=)`

Check URL: Original "config=eyJ1cmwiOiJodHRwczovL2FwaS5tY3AuYWkvcF9zZWZhel9lc19kZWNfY2FpeGFfcG9zdGFsIn0=" -- I need copy exactly. Let me verify with original: `eyJ1cmwiOiJodHRwczovL2FwaS5tY3AuYWkvcF9zZWZhel9lc19kZWNfY2FpeGFfcG9zdGFsIn0=` (yes).

VS Code link:

`[➕ VS CodeにSEFAZ ES DEC: Caixa Postalをインストール](vscode:mcp/install?name=sefaz_es_dec_caixa_postal\&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%13A%2F%2Fapi.mcp.ai%2Pp_sefaz_es_dec_caixa_postal%22%7D)`

Original: `vscode:mcp/install?name=sefaz_es_dec_caixa_postal\&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fapi.mcp.ai%2Fp_sefaz_es_dec_caixa_postal%22%7D`. Copy it exactly.

Note the original line in the prompt shows `\&` (backslash). I need to preserve that.

---

ChatGPT section:

`### ChatGPT、Manus、OpenClaw、その他40以上のクライアント`

Paragraph: "**MCP over HTTP** をサポートするMCPクライアントならどれでも動作します。サーバーのURLは常に次のとおりです："

GXP1

"クライアントごとの詳細：[INSTALL.md](INSTALL.md)."

Actually original "Detalhes" - not "Install.md." It uses parentheses: "Detalhes por cliente: [INSTALL.md](INSTALL.md)." We keep.

---

Examples:

`## 使用例`

GXP2

---

Table section:

`## 利用可能なツール（1つ）`

| Tool | Descrição |
|... |... |
| `sefaz_es_dec_caixa_postal_consultar` | SEFAZ ES DEC: Caixa Postal, consulta em fonte oficial. |

I will use "説明" header.

"各ツールの詳細：[docs/ferramentas.md](docs/ferramentas.md)"

---

Prices:

"## 料金"

プリペイド（クレジット残高）で、使用分だけ支払います。 [docs/precos.md](docs/precos.md) を参照してください。

---

Privacy:

"## プライバシー & LGPD"

* **サブプロセッサー**: あなたが選択するLLMホスト（Claude、ChatGPT、Cursor、自作エージェント）。完全なリストは [docs/privacidade-lgpd.md](docs/privacidade-lgpd.md) 。
* ツールたちが返すデータは、選択した **あなたのLLMホスト**（当社の管理外のサブプロセッサー）に送信されます。トレーニング用オプトアウトのあるプランをお勧めします。

Wait, "LLM host" - "選択する LLM host" Not "あなたの" necessarily. Keep "選択した**LLMホスト**（当社の管理外のプロセッサー）に送信されます". 

Actually "sub-processador se fora do nosso controle" is a noun phrase in apposition to LLM host: "sent to the LLM host you choose, [which is] a sub-processor outside our control." So well "サブプロセッサー" is the role.

Fine.

---

FAQ:

"## よくある質問"

**サーバーはオープンソースですか？**
サーバーはプロプライエタリ（ホステッド）です。本“repository” is open wrapper для manifests, docs, skills — all MIT.

**同名エージェントでも使えますか（Claude/Cursorではない）？**

Wait, keep the original em "Posso usar com agente próprio (não Claude/Cursor)?" - In Japanese: "**独自エージェント（Claude/Cursor以外）でも使えますか？**".

"Sim — qualquer cliente que suporte MCP over HTTP. URL: `ops`." 

Ja: "はい — **MCP over HTTP** をサポートするクライアントなら何でも使えます。URL: `https://api.mcp.ai/p_sefaz_es_dec_caixa_postal`。"

---

Support:

## サポート

* 📧 <sefaz_es_dec_caixa_postal@mcp.ai>
* 🐛 [GitHub Issues](https://github.com/mcp-dir/sefaz_es_dec_caixa_postal-mcp/issues)
* 📄 [docs/](docs/)

---

License:

## ライセンス

MIT — [LICENSE](LICENSE) を参照してください。 `api.mcp.ai/p_sefaz_es_dec_caixa_postal` のMCPサーバーはプロプライエタリ（ホステッド）であり、本リポジトリ（マニフェスト、ドキュメント、スキル）はMITライセンスです。

---

That's the complete structure.

Now double-check the document has no raw HTML in the prompt. It doesn't.

Also ensure I don't accidentally translate "English version" - I have "英語版" which is Japanese for "English version". Good.

One more check: "consult" and "tool" words in the title "docs/ferramentas" etc. File path.

Potential issue with "VS Code" vs "VS コード" - keep "VS Code".

Also in bullet: "Cline, Continue" - keep names.

Now the table pipe separators: the header separator row in original has "| --- | --- |" (with spaces maybe) - Keep "|---|" style. It's fine as long as same columns.

Input table: