Plugin (MCPForUnity/)
↓ Unity Editor API
Scene, Assets, Scripts
```
**Two codebases, one system:**
- `Server/` - Python MCPserver using FastMCP
- `MCPForUnity/` - Unity C# Editor package
### Three Layers on the Python Side
logic lives here; the other packages are thin frontends over it.
- `packages/mcp` (`@zilliz/claude-context-mcp`) — stdio MCPserver, the primary product. ESM (`"type": "module"`).
- `packages/vscode-extension` (`semanticcodesearch`) — VSCode extension. Bundled with webpack; stubs
CLAUDE.md
Guidance for working in this repository.
## What this project is
IDA Pro MCPServer: exposes IDA Pro / idalib functionality to MCP clients.
Main pieces:
- `src/ida_pro_mcp/server.py`: MCPserver entrypoint
- `src/ida_pro_mcp/idalib_server.py
Claude Development Guide for PAL MCPServer
This file contains essential commands and workflows for developing and maintaining the PAL MCPServer when working with Claude. Use these instructions
that coordinates approvals and manages Claude Code sessions
- `hlyr/` - TypeScript CLI with MCP (Model Context Protocol) server for Claude integration
- `humanlayer-wui/` - CodeLayer - Desktop/Web UI (Tauri + React) for graphical approval
desktop app (`hola-boss-oss`) + its in-process runtime
(`runtime/{harnesses,harness-host,api-server,state-store}`). See
`apps/desktop/CLAUDE.md` for desktop-renderer conventions and the parent
`~/Developer/CLAUDE.md` for how this
OpenAI client
5. Streams response back, stores in MongoDB
### Model Context Protocol (MCP)
MCPservers are configured via `MCP_SERVERS` env var. When enabled, tools are exposed as OpenAI function
imports don't need `.js` extensions.
- GitHub API calls should use retry logic (`src/utils/retry.ts`).
- MCPservers are auto-installed at runtime to `~/.claude/mcp/github-{type}-server
Built-in support for Model Context Protocol tools - can integrate with hundreds of existing MCPservers from the ecosystem.
### Safety Engine
Policy-based content filtering and safety enforcement with configurable
humans (probably most things!), put the instructions in README.md instead._
Import @README.md
## Important: Publishing MCPservers
The `data/seed.json` file is seed data for local development only. Do NOT create pull
except-first"` | How to format returned output |
| `mcp_url` | str | `None` | MCPserver URL to load tools from |
| `handoffs` | list | `None` | Agents this agent can hand off to |
| `plan_enabled
resolves to bare `t.procedure` (the cloud layer lives on `dev`)
#### Security Considerations
- Server-side keys come from env vars only; client-held keys are user-supplied
#### Writing Style
- **Never
Cursor AI IDE with Figma. Three components communicate in a pipeline:
```
Cursor AI ←(stdio)→ MCPServer ←(WebSocket)→ WebSocket Relay ←(WebSocket)→ Figma Plugin
```
## Build & Development Commands
```bash
bun install # Install dependencies
applicable skills with `warden --skill `.
-
## Multi-process filesystem state
- MobileBuildMCP explicitly supports multiple concurrent MCPserver, daemon, CLI, test, and helper processes for the same or different workspaces.
- Shared filesystem
teach AI assistants how to build flawless n8n workflows using the n8n-mcpMCPserver.
**Repository**: https://github.com/czlonkowski/n8n-skills
**Purpose**: 14 complementary skills that provide expert guidance on using
sets `output: 'standalone'`
## Agent Control Interfaces
Mission Control provides three interfaces for autonomous agents:
### MCPServer (recommended for agents)
```bash
# Add to any Claude Code agent:
claude mcp add mission
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.