# MCP Registry

This registry lists the local MCP servers that belong to the AetherDesk / SCBE ecosystem.

## 1. AetherDesk Ecosystem MCP

Purpose: find the right local project, note vault, side project, backup lane, or source-of-truth path.

Source:

- `C:\Users\issda\AetherDesk\scripts\aetherdesk-mcp.js`
- `C:\Users\issda\AetherDesk\aetherdesk\ecosystem-library.js`
- `C:\Users\issda\AETHER_ECOSYSTEM_INDEX.csv`
- `C:\Users\issda\AETHER_ECOSYSTEM_LIBRARY.md`

Launch:

```powershell
cd C:\Users\issda\AetherDesk
npm run mcp:ecosystem
```

Client config:

```json
{
  "mcpServers": {
    "aetherdesk-ecosystem": {
      "command": "node",
      "args": ["C:\\Users\\issda\\AetherDesk\\scripts\\aetherdesk-mcp.js"]
    }
  }
}
```

Tools:

- `ecosystem_search`
- `ecosystem_get_entry`
- `ecosystem_list_categories`
- `ecosystem_library_excerpt`
- `ecosystem_path_status`

Use it for:

- "Where are my Pazaak docs?"
- "Find the fog-of-war notes."
- "Which repo has the Go board work?"
- "Which folders are active source vs backup?"
- "Where should I search before crawling OneDrive?"

## 1b. AetherDesk HTTP Connector MCP

Purpose: let ChatGPT, Vercel-hosted services, and other HTTP-capable LLM clients
use AetherDesk's safe tool surface.

Source:

- `C:\Users\issda\AetherDesk\aetherdesk\connector-http.js`
- `C:\Users\issda\AetherDesk\aetherdesk\mcp-core.js`
- `C:\Users\issda\AetherDesk\api\mcp.js`

Local endpoint:

```text
http://127.0.0.1:5717/mcp
```

Local smoke:

```powershell
cd C:\Users\issda\AetherDesk
npm run connector:smoke
```

Tools:

- `aetherdesk_connector_info`
- `aetherdesk_health`
- `aetherdesk_list_apps`
- `aetherdesk_desktop_state`
- `aetherdesk_open_app`
- `aetherdesk_shell_profiles`
- `aetherdesk_run_shell_profile` (disabled unless `AETHERDESK_CONNECTOR_ALLOW_SHELL=1`)
- `aetherdesk_web_audit` (read-only public page title/headings/controls/error/mobile-overflow audit)
- `aetherdesk_revenue_meter` (terminal/API receipt usage, API-cost reserve, estimated net, and offer tier)
- all AetherDesk ecosystem MCP tools listed above

Use it for:

- "Open Browser in AetherDesk."
- "What AetherDesk apps are registered?"
- "Read the current desktop state."
- "Search the Aether ecosystem index."
- "Classify this number on the Prime Grid."
- "Summarize terminal/API usage into a billable report."
- "Audit this public website for mobile overflow and console errors."

## 2. SCBE Verify MCP

Purpose: expose the deterministic SCBE verification substrate to any MCP-capable model.

Source:

- `C:\Users\issda\SCBE-AETHERMOORE\src\mcp\scbe_verify_mcp.py`

Status:

- PR #2501 merged.
- Server exists in the local SCBE checkout.
- Tools are read-only and offline.

Launch for local clients:

```powershell
cd C:\Users\issda\SCBE-AETHERMOORE
python src/mcp/scbe_verify_mcp.py
```

Client config:

```json
{
  "mcpServers": {
    "scbe-verify": {
      "command": "python",
      "args": ["C:\\Users\\issda\\SCBE-AETHERMOORE\\src\\mcp\\scbe_verify_mcp.py"]
    }
  }
}
```

Tools:

- `verify_conlang` - verify Cassisivadan/conlang programs across Python, JavaScript, and Rust with bijective read-back.
- `verify_polyglot` - verify portable op-programs across Python, JavaScript, and Rust.
- `verify_loomfn` - verify arrays, functions, recursion, and string-like numeric programs across language faces.
- `score_intent` - run the SCBE governance gate and return ALLOW / QUARANTINE / ESCALATE / DENY with flags.

Resources:

- `scbe://portable-ops`
- `scbe://conlang-examples`
- `scbe://loomfn-examples`

Use it for:

- "Prove this conlang program gives 15 across all faces."
- "Check this op-program agrees across Python/JS/Rust."
- "Score this user/tool intent through the governance gate."
- "Let a small model call a deterministic verifier instead of guessing."

## Grok / URL Client Setup

Grok cloud connectors cannot see `127.0.0.1` directly. For repeated use, use the named Cloudflare tunnel:

```text
https://mcp.aethermoore.com/sse
```

Named tunnel:

- name: `scbe-mcp`
- id: `b51c0965-cae7-492e-80e7-ab48902754f7`
- hostname: `mcp.aethermoore.com`
- local service: `http://127.0.0.1:8765`
- config: `C:\Users\issda\.cloudflared\config.yml`
- origin host header: `127.0.0.1:8765` to avoid the local SSE server rejecting `mcp.aethermoore.com` as a misdirected request.

Start the local SCBE MCP server:

```powershell
cd C:\Users\issda\AetherDesk
npm run mcp:scbe
```

Start the named tunnel:

```powershell
C:\Users\issda\AetherDesk\scripts\start-scbe-mcp-tunnel.ps1
```

Safer one-command local start without public exposure:

```powershell
cd C:\Users\issda\AetherDesk
npm run mcp:scbe:start
```

One-command public start, only when you actually want Grok/cloud access:

```powershell
cd C:\Users\issda\AetherDesk
npm run mcp:scbe:start-public
```

Status:

```powershell
cd C:\Users\issda\AetherDesk
npm run mcp:scbe:status
```

Stop both the public tunnel and local MCP listener:

```powershell
cd C:\Users\issda\AetherDesk
npm run mcp:scbe:stop
```

Connector URL:

```text
https://mcp.aethermoore.com/sse
```

Stop stale Python MCP listeners on port `8765`:

```powershell
C:\Users\issda\AetherDesk\scripts\stop-scbe-mcp-port.ps1
```

One-off quick tunnels still work for temporary tests:

```powershell
cloudflared tunnel --url http://localhost:8765
```

Important: the named URL is stable. Treat it as more sensitive than a throwaway tunnel URL. The verify tools are read-only/offline, but this still exposes local service behavior while the tunnel is running. Stop `cloudflared` when done.

## Recommended Model Workflow

Use both MCPs together:

1. `aetherdesk-ecosystem.ecosystem_search` finds the right repo, note vault, or subsystem.
2. The model reads or edits only the relevant lane.
3. `scbe-verify.verify_*` proves outputs across faces when the task touches SCBE languages, conlangs, op-programs, or loom functions.
4. `scbe-verify.score_intent` gates risky intent.
5. AetherDesk receipts/logs preserve the operator trail.

## Future See/Touch MCP Lane

AetherDesk's next MCP class is desktop observation/action. See:

- `C:\Users\issda\AetherDesk\docs\SEE_TOUCH_AUTOMATION_RESEARCH.md`

Planned order:

1. Read-only observation tools.
2. AetherDesk-only window controls.
3. Policy-gated external drivers such as Cua Driver.
4. Host desktop input only with receipts and explicit approval.

## Safety Boundary

- AetherDesk ecosystem MCP is read-only over the library/index.
- SCBE verify MCP is read-only/offline over deterministic verification tools.
- Proton tools in the AetherDesk ecosystem MCP are reference/status only and must not return resolved secret values.
- Neither MCP should expose arbitrary shell execution.
- Public tunnels should be temporary.
- Remote writes, publishing, pushing, email sending, or deployment remain outside these MCPs and require explicit separate approval.
