store
```
$INTEL_HOME/cases/ / # = intel_engine/cases/ /
```
The CLI (`scripts/backend/intel.py`), the pipeline (`intel_engine/tools/intel.py`) and the MCPserver (`intel_engine/harness/tools.py`) **all** resolve to it. Confirm with
`python3 scripts/backend/backend.py status`.
**Never create
luong
[Kiem tra truoc khi giao]
```
## MCP Ads Integration
Khi user da ket noi MCPserver cho nen tang quang cao, cac skill co the pull data tu dong thay
agent runs as an isolated Docker container with standardized interfaces for credentials, tools, and MCPserver integrations.
**Local**: http://localhost
**Backend API**: http://localhost:8000/docs
---
## Development Skills (`.claude` submodule)
Skills
Détermine l'importance d'une information
async fn assess_importance(&self, content: &str) -> Result ;
}
```
## MCPServer Tools
Le serveur MCP doit exposer ces tools pour Claude Code:
### icm_store
```json
same time this repository itself uses Simone to organize its own work (currently the mcp-server based version).
## Activity Logging
You have access to the `log_activity` tool
CLAUDE Instructions - MCPServer Development
## Overview
This is the MCP (Model Context Protocol) server implementation for Simone. This is a complete rewrite of the legacy directory-based command system.
## Tech
fields: `server`, `tool`; optional `input` with
`${tool_input.field}` substitution. Caveat: SessionStart and Setup fire before
MCPservers finish connecting, so for service detection prefer a direct probe
(see `detect-tidewave.sh`); reserve `mcp
Mobile app → Server → Claude SDK → Server → Mobile app
4. **Permission Handling**:
- Claude requests permission → MCPserver intercepts → Sends to mobile → Mobile responds → MCP approves/denies
## Key Design Decisions
1. **File-based
test:integration` - Integration tests with TouchDesigner WebServer
- `npm run test:unit` - Unit tests for MCPserver components
- `npm run test:python` - TouchDesigner-side Python tests against a stubbed `td` module
Claude Code (claude.ai/code) when working with code in this repository.
## Project Overview
Telegram MCPServer - a full-featured Telegram integration for Claude, Cursor, and MCP-compatible clients. Uses Telethon
Claude adds them. The MCP tools are individual operations — Claude is the orchestrator.
## Tool Reference
| Tool | When to use |
| ---- | ----------- |
| `onto_status` | To check if the server is running and healthy
order: which lane to use (shell out to the `xactions` CLI, or
load the MCPserver), the CLI lane and its output contract, the MCP lane, a table from
common
right one per task:
| Surface | What it's for | When to use it |
|---|---|---|
| **MCP tools** (this plugin) | Provisioning, schema, RLS, OAuth setup, function deploy, frontend deploy, integrations, billing config | Orchestration
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.