Merge pull request #1 from tadata-org/improvements

Refactor

Author: shahar4499

.gitignore

@@ -0,0 +1,178 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+.python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.
+.idea/
+*.iml
+*.iws
+*.ipr
+*.iws
+.idea_modules/
+
+# VSCode
+.vscode/
+
+# Ruff linter
+.ruff_cache/
+
+# Mac/OSX
+.DS_Store
+
+# Windows
+Thumbs.db
+ehthumbs.db
+Desktop.ini
+
+# Repomix output
+repomix-output.txt

CHANGELOG.md

@@ -5,6 +5,25 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.1.2]
+
+### Changed
+- Complete refactor: transformed from a code generator to a direct integration library
+- Replaced the CLI-based approach with a direct API for adding MCP servers to FastAPI applications
+- Integrated MCP servers now mount directly to FastAPI apps at runtime instead of generating separate code
+- Simplified the API with a single `add_mcp_server` function for quick integration
+- Removed code generation entirely in favor of runtime integration
+
+### Added
+- Main `add_mcp_server` function for simple MCP server integration
+- Support for adding custom MCP tools alongside API-derived tools
+- Improved test suite
+- Manage with uv
+
+### Removed
+- CLI interface and all associated commands (generate, run, install, etc.)
+- Code generation functionality
+
 ## [0.1.1] - 2024-07-03
 
 ### Fixed

CONTRIBUTING.md

@@ -2,46 +2,58 @@
 
 First off, thank you for considering contributing to FastAPI-MCP! 
 
-## Development Process
+## Development Setup
 
-1. Fork the repository
-2. Create a feature branch (`git checkout -b feature/amazing-feature`)
-3. Make your changes
-4. Run the tests (`pytest`)
-5. Format your code (`black .` and `isort .`)
-6. Commit your changes (`git commit -m 'Add some amazing feature'`)
-7. Push to the branch (`git push origin feature/amazing-feature`)
-8. Open a Pull Request
-
-## Setting Up Development Environment
+1. Make sure you have Python 3.10+ installed
+2. Install [uv](https://docs.astral.sh/uv/getting-started/installation/) (recommended) or pip
+3. Fork the repository
+4. Clone your fork and set up the development environment:
 
 ```bash
 # Clone your fork
-git clone https://github.com/tadata-org/fastapi_mcp
+git clone https://github.com/YOUR-USERNAME/fastapi_mcp.git
 cd fastapi-mcp
 
-# Create a virtual environment
-python -m venv venv
-source venv/bin/activate  # On Windows: venv\Scripts\activate
+# Create a virtual environment with uv (recommended)
+uv venv
+source .venv/bin/activate  # On Windows: .venv\Scripts\activate
+
+# Install development dependencies with uv
+uv add -e ".[dev]"
 
-# Install development dependencies
-pip install -e ".[dev]"
+# Alternatively, using pip
+# python -m venv venv
+# source venv/bin/activate  # On Windows: venv\Scripts\activate
+# pip install -e ".[dev]"
 ```
 
+## Development Process
+
+1. Fork the repository
+2. Create a feature branch (`git checkout -b feature/amazing-feature`)
+3. Make your changes
+4. Run type checking (`uv run mypy .`)
+5. Run the tests (`uv run pytest`)
+6. Format your code (`uv run ruff check .` and `uv run ruff format .`)
+7. Commit your changes (`git commit -m 'Add some amazing feature'`)
+8. Push to the branch (`git push origin feature/amazing-feature`)
+9. Open a Pull Request
+
 ## Code Style
 
 We use the following tools to ensure code quality:
 
-- **Black** for code formatting
-- **isort** for import sorting
 - **ruff** for linting
 - **mypy** for type checking
 
 Please make sure your code passes all checks before submitting a pull request:
 
 ```bash
-black .
-isort .
+# Using uv
+uv run ruff check .
+uv run mypy .
+
+# Or directly if tools are installed
 ruff check .
 mypy .
 ```
@@ -51,6 +63,10 @@ mypy .
 We use pytest for testing. Please write tests for any new features and ensure all tests pass:
 
 ```bash
+# Using uv
+uv run pytest
+
+# Or directly
 pytest
 ```