# CasaCaddy [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://github.com/johnarndt/soxoa-mcp-portfolio/tree/main/plugins/casacaddy  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/casacaddy

## Description
Read maintenance requirements, prepare confirmed guides and check device-owned guide jobs.

## Tools
Capabilities this server exposes over MCP:

- **get_connected_installation** — Identify the linked CasaCaddy Pro installation and its current maintenance-guide allowance. No device identifier, billing data, on-device home library, appliance list or task history is exposed.
- **get_maintenance_guide** — Use the linked Pro installation to request a maintenance guide for the appliance details and question the user supplied. Ask for confirmation before using existing Pro allowance; a fresh guide uses that allowance and the existing external model pipeline. Existing exact-input cached guides are unmetered. Supply a fresh UUID request_key and reuse it for retries: identical-key results are persisted, so a retry never starts a second provider request. Preserve safetyWarnings, step cautions, whenToCallPro and call_a_pro difficulty. This does not read on-device appliances or schedule tasks.
- **get_saved_guide_request** — Recover one maintenance-guide request made through MCP by the linked installation, using its exact request_key. Only that installation’s request records are returned, for up to 30 days. Does not start generation, consume allowance or read the on-device library. Keep all safety warnings and professional-help boundaries intact.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "casacaddy": {
    "url": "https://soxoa.com/mcp"
  }
}
```

## Documentation & README

# Soxoa MCP portfolio

Public first-party connection configurations and workflow skills for eleven Soxoa LLC products. Each plugin has its own hosted endpoint, documentation, privacy/terms links, owner-aware workflow instructions and truthful account requirements.

| Product | Remote MCP endpoint | Authentication |
| --- | --- | --- |
| [Soxoa](https://github.com/johnarndt/soxoa-mcp-portfolio/blob/HEAD/plugins/soxoa/README.md) | `https://soxoa.com/mcp` | No auth |
| [MentionedOn](https://github.com/johnarndt/soxoa-mcp-portfolio/blob/HEAD/plugins/mentionedon/README.md) | `https://mentioned-on.com/mcp` | No auth |
| [RegSentry](https://github.com/johnarndt/soxoa-mcp-portfolio/blob/HEAD/plugins/regsentry/README.md) | `https://regsentry.com/mcp` | No auth |
| [Intakra](https://github.com/johnarndt/soxoa-mcp-portfolio/blob/HEAD/plugins/intakra/README.md) | `https://intakra.com/mcp` | No auth |
| [Postedly](https://github.com/johnarndt/soxoa-mcp-portfolio/blob/HEAD/plugins/postedly/README.md) | `https://postedly.com/mcp/send` | OAuth 2.1 / PKCE |
| [Portravo](https://github.com/johnarndt/soxoa-mcp-portfolio/blob/HEAD/plugins/portravo/README.md) | `https://portravo.com/mcp` | OAuth 2.1 / PKCE |
| [Dokyumi](https://github.com/johnarndt/soxoa-mcp-portfolio/blob/HEAD/plugins/dokyumi/README.md) | `https://dokyumi.com/mcp` | OAuth 2.1 / PKCE |
| [Afterglow](https://github.com/johnarndt/soxoa-mcp-portfolio/blob/HEAD/plugins/afterglow/README.md) | `https://afterglow-lime.vercel.app/mcp` | OAuth 2.1 / PKCE |
| [Dibatto](https://github.com/johnarndt/soxoa-mcp-portfolio/blob/HEAD/plugins/dibatto/README.md) | `https://dibatto.com/mcp` | OAuth 2.1 / PKCE |
| [Ocolta](https://github.com/johnarndt/soxoa-mcp-portfolio/blob/HEAD/plugins/ocolta/README.md) | `https://app.ocolta.com/mcp` | OAuth 2.1 / PKCE |
| [CasaCaddy](https://github.com/johnarndt/soxoa-mcp-portfolio/blob/HEAD/plugins/casacaddy/README.md) | `https://api.casacaddy.com/mcp` | OAuth 2.1 / PKCE |

All endpoints use Streamable HTTP. Compatible clients normally call that transport `http`. Use the individual plugin's `.mcp.json` or its official documentation. The first four integrations expose public read-only planning/evidence tools; the remaining seven use OAuth and connected owner permissions for account operations.

These files include no hosted application source, private accounts, credentials, payment keys, internal reviewer cases, recordings, or test fixtures. Installation does not authorize arbitrary writes, paid processing or purchases. Server capabilities and plan entitlements remain authoritative.

The local marketplace index is `.claude-plugin/marketplace.json`; individual plugin folders are under `plugins/`. A live source repository is established during the authorized distribution release. Directory review and search discovery depend on their maintainers and do not guarantee recommendations.

MIT applies to these distribution files. Hosted services retain their product terms and implementation rights.