![Tests & Lint](https://github.com/<ORGANIZATION>/pytest-mcp-tools/actions/workflows/ci.yaml/badge.svg?branch=main)
![PyPI](https://img.shields.io/pypi/v/pytest-mcp-tools.svg)
![Downloads](https://static.pepy.tech/badge/pytest-mcp-tools)
![Monthly Downloads](https://static.pepy.tech/badge/pytest-mcp-tools/month)
![License](https://img.shields.io/github/license/sinan-ozel/pypi-publish-with-cicd.svg)
[![Documentation](https://img.shields.io/badge/docs-github--pages-blue)](https://sinan-ozel.github.io/pytest-mcp-tools/)

# ✨ Introduction

I created this repository to automatically test my MCP tool servers.
```
pytest --mcp-tools=http://localhost:8000
```

Will create some tests, automatically, and you will get an output that looks like this:
```
🔍 MCP Tools: Discovering endpoints at http://test-server:8000...
   Retry 1/10: Checking http://test-server:8000...
   ✓ Server reachable (status: 404)
   ✓ Found endpoint: /mcp (status: 406)
   ✗ Endpoint /sse not found (status: 404)
   ✗ Endpoint /messages not found (status: 404)
✅ MCP Tools: Discovered endpoints: /mcp

============================= test session starts ==============================
platform linux -- Python 3.11.14, pytest-9.0.2, pluggy-1.6.0 -- /usr/local/bin/python3.11
cachedir: .pytest_cache
rootdir: /app
configfile: pyproject.toml
plugins: cov-7.0.0, anyio-4.12.1, depends-1.0.1, mock-3.15.1, mcp-tools-0.1.0
collecting ... collected 3 items

✅ MCP tools test created for discovered endpoints: /mcp
   📡 HTTP streaming support detected

test_samples/test_sample_math.py::test_sample_addition PASSED            [ 25%]
test_samples/test_sample_math.py::test_sample_multiplication PASSED      [ 50%]
.::test_mcp_tools[POST /mcp] PASSED                                      [ 75%]
test_samples/test_sample_math.py::test_sample_string_operations PASSED   [100%]

============================== 4 passed in 0.03s ===============================
```

Note the test called `.::test_mcp_tools[POST /mcp] PASSED                                      [ 75%]`.
This is automatically generated by the plugin, and the plan is to make more of these automatically-generated tests based on descriptions of the tools.


# Reporting Issues
If you tested this on your server, and think that there is an issue, just give me the docker image of your server in the issue, and tell me what you are expecting, what you got.

If you don't have a docker hub image, give me a minimal example. That's all I need.

# 🛠️ Development

The only requirement is 🐳 Docker.
(The `.devcontainer` and `tasks.json` are prepared assuming a *nix system, but if you know the commands, this will work on Windows, too.)

1. Clone the repo.
2. Branch out.
3. Open in "devcontainer" on VS Code and start developing. Run `pytest` under `tests` to test.
4. Akternatively, if you are a fan of Test-Driven Development like me, you can run the tests without getting on a container. `.vscode/tasks.json` has the command to do so, but it's also listed here:
```
docker compose -f tests/docker-compose.yaml up --build --abort-on-container-exit --exit-code-from test
```
