تخطيط مشروع الخادم

A small server fits in one file, but a good layout lets it grow without becoming a mess. A little planning now saves real pain later. 🗂️

Most servers begin life as a single server.py. It holds your FastMCP instance plus a tool or two, which is plenty to get running.

At the root sits pyproject.toml, declaring your project name and its dependencies. uv reads it to know exactly what to install.

Right beside it lives uv.lock, the pinned record of every resolved version. Commit it so teammates reproduce your exact setup.

The .venv folder is generated, not source code. Add it to .gitignore so you never commit a heavy, machine-specific environment.

As you grow, split code by what it does. Putting tools, resources, and prompts in separate modules keeps each file focused and readable.

A growing server often looks like this: a server entry point next to a folder for each kind of capability. Clear folders mean fast navigation. 🌳

Keep a single entry point that creates the FastMCP instance and registers everything. Clients only ever need to launch this one file.

Define tools in their own modules, then import and register them in the entry file. Your server.py stays short and easy to scan.

A short README telling others how to install and run your server makes it shareable. Future-you will thank present-you for it.

Never hardcode keys in your code. Read them from environment variables and keep a sample .env so config stays safe and portable. 🔐

You're deciding what to commit to version control.

You learned to start in one file, keep pyproject.toml and the lockfile tracked, ignore .venv, and split by primitive. Your server can grow cleanly. ✅