This project is for building MCP core communication tools for iSphere / IMPlatformClient so AI digital employees can use contacts, groups, messages, and files through a clear tool surface.

The business goal is not a selector/report project. The business goal is an MCP tool surface for searching contacts, searching groups, receiving/reading messages, sending messages, receiving/downloading files, and sending files.

Scope

Implement the six core MCP capabilities: search contacts, search groups, receive/read messages, send messages, receive/download files, and send files.
Build from stable capability sources first, then fill gaps with UI automation only where it directly serves a core tool.
Prefer stable entry points in this order:
1. Existing bridge / API / local service.
2. Local data/log/cache discovery in read-only mode.
3. UI automation/RPA wrapper as fallback.
4. Network/API discovery.
5. Binary reverse engineering only when needed to explain or validate the above.

Existing Source Material

Previous iSphere work: E:\coding\codex\isphere
Installer: E:\coding\codex\isphere\iSphere_4.1.2.6841.exe
Existing bridge artifacts: OpenClawBridge, MockCloud, XmppBridgeService
Existing MCP spec: E:\coding\codex\isphere\docs\MCP接口需求规格.md

Key Directories

docs/ - design notes and installed skill map.
prompts/ - ready-to-use Codex prompts for each investigation phase.
evidence/ - local evidence output; ignored by Git except .gitkeep.
runs/ - run logs and temporary investigation outputs; ignored by Git except .gitkeep.
cmd/, internal/, native/ - current Go MCP server, helper client, tool registration, and C# WinHelper code.

Operating Notes

runs/ and evidence/ are local evidence/work directories and are not part of normal commits.
Route work through the MCP core tool contract instead of expanding selector/report-only nodes.