repo from the inside (`resources: [{type: "github_repository", ...}]`)
- **MCP tools**: wire an external data MCPserver (`mcp_servers` + `mcp_toolset` on the agent, credentials via a vault, `vault
MCPserver (TypeScript) × Claude Managed Agents
MCPserver that exposes Managed Agents session primitives as tools. Two entrypoints sharing one tool set: `src/server.ts` (stdio → Claude Desktop and Claude Code
affected`) instead of using the underlying tooling directly
- You have access to the Nx MCPserver and its tools, use them to help the user
- When answering questions about
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
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
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
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
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
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
when working with code in this repository.
## Project Overview
**Gemini Notebook (formerly Google NotebookLM) MCPServer & CLI** - Provides programmatic access to Gemini Notebook (notebook.google.com) via both a Model Context Protocol
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.