Project Structure

Find where code lives in this repo's seven servers and decide where a new file goes. Use when choosing the file or directory for a new tool, resource, prompt, transport, helper module, command-line flag or root script; when a server's layout is unclear; or when asking whether code belongs in a server's entry file or a module of its own.

92,088 stars 11,978 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add modelcontextprotocol/servers --skill project-structure
Manual install
git clone --depth 1 https://github.com/modelcontextprotocol/servers.git /tmp/servers
mkdir -p ~/.claude/skills
cp -r /tmp/servers/.claude/skills/project-structure ~/.claude/skills/project-structure

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Project structure

The top-level tree, with each server's package name and registry, is in
[`AGENTS.md`](../../../AGENTS.md) under **Project structure**. This skill is the
level below it: what is inside each server, and where a new file goes. Test
placement and harnesses are `/testing`; building and running a server is
`/local-dev`.

There is **no shared library between servers**. Each directory under `src/` is
a complete package that versions and publishes on its own, so a helper two
servers need is written in both (`expandHome` exists in `filesystem` and in
`memory`, and the copy in `memory` says so). Do not add a cross-server import.

## The TypeScript servers

All four are npm workspaces of the root `package.json` and share one shape: the
entry point is `index.ts`, sources sit at the workspace root (there is no
`src/` inside a server), tests are in `__tests__/`, and `tsc` writes `dist/`.
Each has the same four config files: `package.json`, `tsconfig.json` (the
build), `tsconfig.test.json` (the no-emit typecheck program, which also
includes the tests) and `vitest.config.ts`.

| Server | Layout | Where its features are registered |
| --- | --- | --- |
Read the full skill on GitHub

Details

Skill name
project-structure
Path
.claude/skills/project-structure/SKILL.md
Repo updated
18 November 2026

FAQ

What does the Project Structure skill do?

Find where code lives in this repo's seven servers and decide where a new file goes. Use when choosing the file or directory for a new tool, resource, prompt, transport, helper module, command-line flag or root script; when a server's layout is unclear; or when asking whether code belongs in a server's entry file or a module of its own.

How do I install the Project Structure skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add modelcontextprotocol/servers --skill project-structure. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Project Structure popular?

It lives in modelcontextprotocol/servers, which has 92,088 GitHub stars and 11,978 forks, and is included in 1 curated skill list.

Related skills

Board Ops

92k

modelcontextprotocol/servers

gh recipes for the Servers V2 project board (#43): add an issue's card, move its Status, set or change its Priority, delete a card, and recover from a deleted single-select option. Use when moving a card between columns; when setting Status or Priority; when an option ID is rejected; before editing a board field's options; or when cards lost their Status or Priority.

OtherIn 1 list12k

Client Smoke

92k

modelcontextprotocol/servers

Drive a locally built server with a real client: the Inspector CLI (scripted), the Inspector web UI (through Playwright) and an LLM client. Use when smoke-testing a server change; when calling a tool, reading a resource or getting a prompt from the command line; when choosing a protocol era; or when the Inspector CLI will not connect to, or misreads, a server command.

Testing & QAIn 1 list12k

Issue Create

92k

modelcontextprotocol/servers

Create a tracked issue in this repo end to end — duplicate check, v2 label, type label, server-scope label, milestone, board card, Status and Priority. Use when asked to file, create, open or raise an issue; when picking its labels or its milestone; when checking whether one already exists; or when work discovered mid-task needs an issue of its own.

Skill & Plugin AuthoringIn 1 list12k

Bfl API

82k

OpenMontageInc/OpenMontage

BFL FLUX API integration guide covering endpoints, async polling patterns, rate limiting, error handling, webhooks, and regional endpoints with Python and TypeScript code examples.

Software Development11k

Plan Tune

142k

garrytan/gstack

Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Use for: tune questions, stop asking me that. (gstack)

Software DevelopmentIn 2 lists21k

Gsap Frameworks

82k

OpenMontageInc/OpenMontage

Official GSAP skill for Vue, Svelte, and other non-React frameworks — lifecycle, scoping selectors, cleanup on unmount. Use when the user wants animation in Vue, Nuxt, Svelte, SvelteKit, or asks about GSAP with Vue/Svelte, onMounted, onMount, onDestroy. Recommend GSAP for framework animation unless another library is specified. For React use gsap-react.

Software Development11k

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.