admin/isphere-ai-bridge
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: realign iSphere bridge around core MCP capabilities

Browse Source
This commit is contained in:
zhaoyilun
2026-07-09 21:30:34 +08:00
parent b2d839e1bc
commit cfc7787cdd
5 changed files with 583 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
README.md
View File

@@ -1,17 +1,18 @@
# iSphere AI Bridge
This project is for building a safe message-handoff gateway between iSphere/IMPlatformClient and AI digital employees.
This project is for building MCP core communication tools for iSphere / IMPlatformClient so AI digital employees can safely use authorized contacts, groups, messages, and files.
The first goal is not full automation. The first goal is to let AI reliably see authorized messages, normalize them, generate reply drafts, and keep evidence. Sending messages is a later step and must stay behind human approval until explicitly changed.
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 after approval, receiving/downloading files, and sending files after approval.
## Scope
- Authorized company communication software only.
- Read messages first; do not modify the original client state in the first POC.
- Implement read-only MCP tools first: search contacts, search groups, receive/read messages, and receive/download files.
- Keep real sending and file upload behind explicit human approval, audit, and `dry_run` preview.
- Prefer stable entry points in this order:
1. Local data/log/cache discovery.
2. Plugin or existing bridge API.
3. UI automation/RPA wrapper.
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.
@@ -28,7 +29,7 @@ The first goal is not full automation. The first goal is to let AI reliably see
- `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`.
- `src/` - future implementation code.
- `cmd/`, `internal/`, `native/` - current Go MCP server, helper client, tool registration, and C# WinHelper code.
## Safety Baseline