Skip to main content

pytest-mcp-contract

Pytest helpers for domain MCP tool contracts: registered names, annotations, and in-memory handler calls.

This is not protocol conformance. It does not wrap npx @modelcontextprotocol/conformance, does not ship security payloads, and does not run an LLM in CI.

Install

pip install pytest-mcp-contract

For in-memory registry access against the MCP Python SDK:

pip install "pytest-mcp-contract[mcp]"

The mcp extra pins the MCP Python SDK the same way swamp-ops does today: mcp[cli]>=2.0.0 (SDK 2.x MCPServer).

Develop from a git checkout:

pip install -e ".[mcp]"

Usage

Override the mcp_server fixture with your server object. The plugin lists names from the in-memory registry (no stdio subprocess).

import pytest
from mcp_contract.assert_mcp import assert_tools_named
from mcp_contract.session import list_tool_names

@pytest.fixture
def mcp_server():
    from swamp_ops.server import server
    return server

def test_tool_names(mcp_server):
    assert_tools_named(list_tool_names(mcp_server), {"swamp_estate_status", ...})

list_tool_names reads MCPServer._tool_manager._tools (or tool_manager._tools). That is the same private registry swamp-ops already inspects. If the shape is unknown, the helper fails instead of skipping — registry drift is what this plugin is for.

Calls go through the registered Tool.fn handler, not mcp.Client. v1 is in-memory only. Async handlers are supported: call_registered_tool uses asyncio.run; use acall_registered_tool inside async tests.

Input schema snapshots

Pin tool input JSON schemas and fail CI on accidental drift:

import json
from pathlib import Path
from mcp_contract.schemas import assert_tool_input_schemas_match

@pytest.fixture
def mcp_server():
    from swamp_ops.server import server
    return server

def test_schemas(mcp_server):
    expected = json.loads(Path("tests/fixtures/mcp_schemas.json").read_text())
    assert_tool_input_schemas_match(mcp_server, expected, tools=set(expected))

Refresh a snapshot from a live server module:

python -m mcp_contract snapshot tests/fixtures/mcp_schemas.json --module swamp_ops.server

See also

Those cover protocol and transport. This plugin asserts your tool set.

License

Apache-2.0

Release files for pytest-mcp-contract 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pytest-mcp-contract 0.1.3
File Size Uploaded
pytest_mcp_contract-0.1.3.tar.gz 12.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for pytest-mcp-contract 0.1.3
File Interpreter ABI Platform
pytest_mcp_contract-0.1.3-py3-none-any.whl Python 3 none any Details

Total release size: 27.7 kB

Release files / pytest_mcp_contract-0.1.3.tar.gz

Download URL pytest_mcp_contract-0.1.3.tar.gz
Size 12.6 kB
Tags Source
SHA-256 checksum
How to use checksums
ae04466aecc8cbeae03d5cc6d9dfe60d0721fc45e578453e57988768c7b0edba
BLAKE2b-256 checksum
How to use checksums
1e9fd9a242476cbbb107b687f8136b7bb2371f1b493f3f280d1e01d553cb863a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 20, 2026.

Transparency log

Release files / pytest_mcp_contract-0.1.3-py3-none-any.whl

Download URL pytest_mcp_contract-0.1.3-py3-none-any.whl
Size 15.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
eb31823f37fa8ac5ac8157cb3ea4494d3acb4b548fda929dd09a94ed62031300
BLAKE2b-256 checksum
How to use checksums
2a4c5d8c7d73e13fda252ee77bb97f3d5b40cd3536c9b2ad94649de4d7dff64a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 20, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

This release

0.1.3 This release

2 release files

0.1.2

2 release files

0.1.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page