Timmy_Foundation/timmy-config
16
0
Fork 0
Code Issues 57 Pull Requests 1 Actions 1 Packages Projects Releases Wiki Activity

[HARNESS] Register steam-info + desktop-control MCP servers in config.yaml #19

New Issue
Closed
opened 2026-03-26 19:57:09 +00:00 by perplexity · 9 comments
perplexity commented 2026-03-26 19:57:09 +00:00
Member
Copy Link

Context

Per research spike the-nexus#576 and direction shift the-nexus#542.

mcp/servers.json defines steam-info-mcp and mcp-pyautogui but they are not registered in config.yaml under mcp_servers. Hermes Agent reads mcp_servers from config.yaml — not from servers.json. So Timmy currently has no eyes and no hands.

Task

Add the two MCP servers to config.yaml mcp_servers section alongside the existing orchestration entry:

mcp_servers:
  orchestration:
    command: /Users/apayne/.hermes/hermes-agent/venv/bin/python3
    args:
      - /Users/apayne/.hermes/hermes-agent/tools/orchestration_mcp_server.py
    env: {}
    timeout: 120
  steam-info:
    command: steam-info-mcp
    args: []
    env:
      STEAM_API_KEY: ${STEAM_API_KEY}
  desktop-control:
    command: mcp-pyautogui
    args: []
    env:
      DISPLAY: ":0"

Prerequisites

  • pip install steam-info-mcp mcp-pyautogui (run mcp/setup.sh)
  • macOS Accessibility permission granted for the Python process
  • STEAM_API_KEY set in ~/.hermes/.env

Acceptance criteria

  • hermes config show | grep -A 20 mcp_servers shows all three servers
  • /reload-mcp in Hermes shows steam-info and desktop-control tools discovered
  • /tools lists screenshot, click, type_text from desktop-control
  • /tools lists steam-owned-games, steam-recently-played from steam-info

Pillar: Harness

Research update — 2026-03-27

Raise priority. Hermes already has real MCP support, so this is a direct leverage task rather than speculative research.

Focus:

  • register the real servers in config
  • verify live discovery/use
  • prove reload/operator workflow
## Context Per research spike the-nexus#576 and direction shift the-nexus#542. `mcp/servers.json` defines `steam-info-mcp` and `mcp-pyautogui` but they are **not registered** in `config.yaml` under `mcp_servers`. Hermes Agent reads `mcp_servers` from config.yaml — not from servers.json. So Timmy currently has no eyes and no hands. ## Task Add the two MCP servers to `config.yaml` `mcp_servers` section alongside the existing `orchestration` entry: ```yaml mcp_servers: orchestration: command: /Users/apayne/.hermes/hermes-agent/venv/bin/python3 args: - /Users/apayne/.hermes/hermes-agent/tools/orchestration_mcp_server.py env: {} timeout: 120 steam-info: command: steam-info-mcp args: [] env: STEAM_API_KEY: ${STEAM_API_KEY} desktop-control: command: mcp-pyautogui args: [] env: DISPLAY: ":0" ``` ## Prerequisites - `pip install steam-info-mcp mcp-pyautogui` (run `mcp/setup.sh`) - macOS Accessibility permission granted for the Python process - `STEAM_API_KEY` set in `~/.hermes/.env` ## Acceptance criteria - [ ] `hermes config show | grep -A 20 mcp_servers` shows all three servers - [ ] `/reload-mcp` in Hermes shows steam-info and desktop-control tools discovered - [ ] `/tools` lists screenshot, click, type_text from desktop-control - [ ] `/tools` lists steam-owned-games, steam-recently-played from steam-info ## Pillar: Harness ## Research update — 2026-03-27 Raise priority. Hermes already has real MCP support, so this is a direct leverage task rather than speculative research. Focus: - register the real servers in config - verify live discovery/use - prove reload/operator workflow
Timmy was assigned by perplexity 2026-03-26 19:57:09 +00:00
Timmy commented 2026-03-26 20:00:49 +00:00
Owner
Copy Link

⚡ Dispatched to claude. Huey task queued.

⚡ Dispatched to `claude`. Huey task queued.
Timmy commented 2026-03-26 20:00:51 +00:00
Owner
Copy Link

⚡ Dispatched to gemini. Huey task queued.

⚡ Dispatched to `gemini`. Huey task queued.
Timmy commented 2026-03-26 20:00:52 +00:00
Owner
Copy Link

⚡ Dispatched to kimi. Huey task queued.

⚡ Dispatched to `kimi`. Huey task queued.
Timmy commented 2026-03-26 20:00:53 +00:00
Owner
Copy Link

⚡ Dispatched to grok. Huey task queued.

⚡ Dispatched to `grok`. Huey task queued.
Timmy commented 2026-03-26 20:00:54 +00:00
Owner
Copy Link

⚡ Dispatched to perplexity. Huey task queued.

⚡ Dispatched to `perplexity`. Huey task queued.
grok commented 2026-03-27 14:41:29 +00:00
Member
Copy Link

🔧 grok working on this via Huey. Branch: grok/issue-19

🔧 `grok` working on this via Huey. Branch: `grok/issue-19`
grok commented 2026-03-27 14:41:37 +00:00
Member
Copy Link

⚠️ grok produced no changes for this issue. Skipping.

⚠️ `grok` produced no changes for this issue. Skipping.
gemini commented 2026-03-27 15:00:39 +00:00
Member
Copy Link

🔧 gemini working on this via Huey. Branch: gemini/issue-19

🔧 `gemini` working on this via Huey. Branch: `gemini/issue-19`
Timmy commented 2026-03-28 04:53:07 +00:00
Owner
Copy Link

Closing during the 2026-03-28 backlog burn-down.

Reason: this issue is being retired as part of a backlog reset toward the current final vision: Heartbeat, Harness, and Portal. If the work still matters after reset, it should return as a narrower, proof-oriented next-step issue rather than stay open as a broad legacy frontier.

Closing during the 2026-03-28 backlog burn-down. Reason: this issue is being retired as part of a backlog reset toward the current final vision: Heartbeat, Harness, and Portal. If the work still matters after reset, it should return as a narrower, proof-oriented next-step issue rather than stay open as a broad legacy frontier.
Timmy closed this issue 2026-03-28 04:53:07 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 enhancement
epic
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 research
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity
No Assignees Timmy
4 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#19
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?