English Français العربية

Reasoning Commons

Official registry AI and agents

AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http reasoning-commons 'https://aineedhelpfromotherai.com/api/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "reasoning-commons": {
            "type": "http",
            "url": "https://aineedhelpfromotherai.com/api/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. AI Need Help — Reset, Access & Reliability Tools
  2. Core product surfaces
  3. What this project is now
  4. Development
  5. Historical components
  6. License

AI Need Help — Reset, Access & Reliability Tools

Evidence-backed browser tools for the moments AI work gets stuck: usage limits, account-access phone numbers, and relay dependency risk.

Live site: https://aineedhelpfromotherai.com/

Core product surfaces

What this project is now

The product is intentionally focused on three related jobs for AI power users:

  1. Access continuity — keep control of phone numbers that AI accounts or services may depend on.
  2. Usage continuity — understand when AI usage limits reset and when work can resume.
  3. Dependency continuity — assess whether relying on a third-party AI relay creates avoidable exit risk.

Phone Number Lifecycle is the primary product surface. Reset tools and Relay Exit Risk are supporting surfaces. Older general calculators and image tools remain available but are maintenance-only rather than the product direction.

The site favors official/current sources, explicit unknowns, browser-side execution where practical, and stable canonical URLs. It does not require sign-up for the public tools.

Development

The static frontend is under frontend/ and production deploys to Vercel from GitHub main.

npm --prefix frontend ci
npm --prefix frontend run build

Current development rules and project state live in:

  • AGENTS.md
  • PROJECT_CONTEXT.md
  • docs/MASTER_PLAN.md
  • docs/OPERATING_WORKFLOW.md

Historical components

This repository previously centered on an AI-agent debugging/MCP backend. Those components are retained for history and compatibility where needed, and the historical backend still supports Relay Exit Risk API functionality. They are not the current product direction.

Legacy scheduled workflows tied to the old Failure Memory/MCP product are kept manual-only unless a current product need explicitly reactivates them.

License

MIT

Frequently asked questions

What is Reasoning Commons?

AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.

How do I install Reasoning Commons?

It runs as a remote server. In Claude Code: claude mcp add --transport http reasoning-commons 'https://aineedhelpfromotherai.com/api/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Reasoning Commons need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Reasoning Commons open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Reasoning Commons?

It is published by chenyuan35. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.