MCP Test Kits - Python
Build from source using FastMCP.
Build
cd python
uv sync
stdio
{
"mcpServers": {
"mcp-test-kits": {
"command": "uv",
"args": ["run", "mcp-test-kits"],
"cwd": "/path/to/mcp-test-kits/python",
"transport": "stdio"
}
}
}
HTTP
Start server:
uv run mcp-test-kits --transport http --port 3000
MCP client config:
{
"mcpServers": {
"mcp-test-kits": {
"url": "http://localhost:3000/mcp",
"transport": "http"
}
}
}
With OAuth
Start server:
uv run mcp-test-kits --transport http --port 3000 --enable-oauth
# or auto-approve for testing
uv run mcp-test-kits --transport http --port 3000 --enable-oauth --oauth-auto-approve
MCP client config (OAuth discovery automatic):
{
"mcpServers": {
"mcp-test-kits": {
"url": "http://localhost:3000/mcp",
"transport": "http"
}
}
}
Or with pre-obtained token:
{
"mcpServers": {
"mcp-test-kits": {
"url": "http://localhost:3000/mcp",
"transport": "http",
"headers": {
"Authorization": "Bearer YOUR_ACCESS_TOKEN"
}
}
}
}
SSE
Start server:
uv run mcp-test-kits --transport sse --port 3000
MCP client config:
{
"mcpServers": {
"mcp-test-kits": {
"url": "http://localhost:3000/sse",
"transport": "sse"
}
}
}
With OAuth
Start server:
uv run mcp-test-kits --transport sse --port 3000 --enable-oauth
# or auto-approve for testing
uv run mcp-test-kits --transport sse --port 3000 --enable-oauth --oauth-auto-approve
MCP client config (OAuth discovery automatic):
{
"mcpServers": {
"mcp-test-kits": {
"url": "http://localhost:3000/sse",
"transport": "sse"
}
}
}
Or with pre-obtained token:
{
"mcpServers": {
"mcp-test-kits": {
"url": "http://localhost:3000/sse",
"transport": "sse",
"headers": {
"Authorization": "Bearer YOUR_ACCESS_TOKEN"
}
}
}
}
Test with MCP Inspector
# stdio
npx @modelcontextprotocol/inspector uv run mcp-test-kits
# HTTP (start server first: uv run mcp-test-kits --transport http --port 3000)
npx @modelcontextprotocol/inspector --transport http --server-url http://localhost:3000/mcp
# SSE (start server first: uv run mcp-test-kits --transport sse --port 3000)
npx @modelcontextprotocol/inspector --transport sse --server-url http://localhost:3000/sse
Development
uv sync --all-extras
uv run pytest
uv run mypy src --check-untyped-defs
uv run ruff check src
Metadata
Release files for mcp-test-kits 0.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mcp_test_kits-0.0.6.tar.gz | 81.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_test_kits-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 105.7 kB
Release files / mcp_test_kits-0.0.6.tar.gz
| Download URL | mcp_test_kits-0.0.6.tar.gz |
|---|---|
| Size | 81.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db8cbd8d209ddd648c1adb1ca9891a792b90cf96d894d3149ce45eb86e346bf8
|
|
BLAKE2b-256 checksum How to use checksums |
1b814b764974bd285fed6b803f9ef36992abe7751b8fdd7dca10f66db8910330
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 4, 2026.
Transparency logRelease files / mcp_test_kits-0.0.6-py3-none-any.whl
| Download URL | mcp_test_kits-0.0.6-py3-none-any.whl |
|---|---|
| Size | 24.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ea544479835bdcf27d862c653b887ffb001b39944535e08e9553b79d9c3ffe96
|
|
BLAKE2b-256 checksum How to use checksums |
9b4758da81a35e303d7c46fc3461178d07dd7ee5a2b1dcd63bdfcbb4e5400b47
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 4, 2026.
Transparency log