Add claw-army/claude-node - Python subprocess bridge for Claude Code CLI

[niceban]

Adds claw-army/claude-node to the MCP Servers section.

• Python subprocess bridge for Claude Code CLI
• Gives Python code direct access to Claude Code native capabilities via stream-json
• Enables building Python applications that leverage Claude Code capabilities

[qodo-code-review]

Review Summary by Qodo

Add claw-army/claude-node MCP server to README

📝 Documentation

Walkthroughs

Description

• Add claw-army/claude-node to MCP Servers list
• Python subprocess bridge for Claude Code CLI
• Enables Python code access to Claude capabilities

Diagram

flowchart LR
  A["README.md"] -- "Add new MCP server entry" --> B["MCP Servers section"]
  B --> C["claw-army/claude-node"]
  C --> D["Python subprocess bridge"]

Loading

File Changes

1. README.md 📝 Documentation +1/-0

Add claw-army/claude-node MCP server entry

• Added new entry for claw-army/claude-node to MCP Servers list
• Describes it as Python subprocess bridge for Claude Code CLI
• Highlights stream-json capability for direct Python access

README.md

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📎 Requirement gaps (0) 📐 Spec deviations (0)

1. Breaks list ordering 🐞 Bug ⚙ Maintainability

Description

The new MCP Servers entry is placed at the end even though the section appears alphabetically
ordered, making the list harder to scan and maintain. This will likely cause future additions to
drift further from a predictable order.

Code

README.md[28]

+- [claw-army/claude-node](https://github.com/claw-army/claude-node) - Python subprocess bridge for Claude Code CLI, giving Python code direct access to Claude Code native capabilities via stream-json.

Evidence

In README.md, the MCP Servers list is currently ordered by entry name: Atlassian → GitHub → Google →
Notion → Supabase. Adding an entry starting with “claw-…” after “Supabase…” breaks that established
ordering pattern.

README.md[22-28]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The MCP Servers bullets appear alphabetically ordered, but the new `claw-army/claude-node` item is appended at the end, breaking the established ordering.

### Issue Context
This repo runs `npx awesome-lint` in CI, and consistent list formatting/order improves maintainability even when not strictly enforced.

### Fix Focus Areas
- README.md[22-28]
 - Move the `claw-army/claude-node` bullet into the correct alphabetical position (likely between Atlassian and GitHub, depending on the final display name you choose).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Uses slug as title 🐞 Bug ⚙ Maintainability

Description

The new MCP Servers bullet uses the GitHub owner/repo slug as the visible link text, unlike other
entries that use human-readable product/server names. This reduces readability and consistency
within the section.

Code

README.md[28]

+- [claw-army/claude-node](https://github.com/claw-army/claude-node) - Python subprocess bridge for Claude Code CLI, giving Python code direct access to Claude Code native capabilities via stream-json.

Evidence

Other MCP Servers entries use human-readable names like “GitHub MCP Server” and “Supabase MCP
Server”. The new entry displays “claw-army/claude-node”, which is a repo identifier rather than a
product/server name.

README.md[22-28]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The new bullet’s visible title is a repo slug (`claw-army/claude-node`) rather than a human-readable name, inconsistent with the rest of the list.

### Issue Context
Contribution guidelines request the format `[Title](link) - Description.`; the title should be a readable name.

### Fix Focus Areas
- README.md[22-28]
 - Change the link text to a human-friendly name (e.g., `Claude Node`, `Claude Code Node Bridge`, or similar), optionally mentioning the repo slug in the description if useful.
 - If you rename the title, re-check alphabetical placement in the list.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more