chore(deps-dev): update mcp requirement from <2,>=1.0 to >=1.0,<3

[dependabot]

Updates the requirements on mcp to permit the latest version.

Release notes

Sourced from mcp's releases.

v2.0.0

MCP Python SDK v2 Stable Release

This is v2.0.0, the stable v2 release of the MCP Python SDK. It supports the 2026-07-28 revision of the Model Context Protocol and serves every earlier revision from the same server. pip install mcp now installs 2.x.

pip install "mcp[cli]"
# or
uv add "mcp[cli]"

Documentation Rewrite

The documentation has the full tutorial and API reference. Coming from v1? What's new in v2 is the tour of what changed and why, and the migration guide lists every breaking change with before-and-after code.

V1 Maintenance mode

v1.x is in maintenance mode and will only receive security fixes from now on The 1.x line lives on the v1.x branch, continues to receive critical bug fixes and security patches, and is documented at https://py.sdk.modelcontextprotocol.io/v1/. If your project is not ready to migrate, keep a <2 upper bound on your requirement (for example mcp>=1.28,<2).

Highlights

One SDK, both protocol eras

v2 speaks the 2026-07-28 revision (stateless requests with no handshake, server/discover, subscriptions/listen, multi-round-trip requests) and still serves every 2025-era client from the same MCPServer, over Streamable HTTP and stdio, with nothing to configure. Client(target) negotiates the version automatically.

FastMCP is now MCPServer, and there is a first-class Client

The decorator API is unchanged; the low-level Server is rebuilt around a shared dispatcher engine, and one Client object replaces v1's transport-plus-ClientSession-plus-initialize() layering. It connects to a URL, a stdio subprocess, a custom transport, or straight to a server object in memory for tests.

Multi-round-trip requests and resolver dependency injection

At 2026-07-28 the server can no longer call the client, so tools return the question instead. A Resolve(fn) parameter is filled by your function invisibly to the model and can put a question to the user; one tool body serves both eras.

Extension APIs, OpenTelemetry, and a standalone types package

Servers and clients compose protocol extensions through pluggable extension APIs (MCP Apps built in); OpenTelemetry tracing ships on by default; every protocol type is its own package, mcp-types (imported as mcp_types), published in lock-step with mcp.

Hardened stdio and auth

stdio servers keep handler subprocesses and stray prints off the wire, and stdout is diverted to stderr while serving. OAuth adds RFC 9207 issuer validation, the SEP-990 identity-assertion flow, and the client-credentials extension.

Coming from a v2 pre-release

Since the last release candidate: the per-version wire packages are private (mcp_types._v*), mcp.types is a permanent alias for mcp_types, the auth registration request model is split from the registered-client record, cancelled requests are no longer answered, and log notifications are gated on the per-request log-level opt-in at 2026-07-28. Since the betas: Client(cache=False) is now cache=None with CacheConfig() the default; Context.client_id, RFC7523OAuthClientProvider, and OAuthClientProvider(timeout=) are removed; the client-credentials providers take scope=; message_handler receives notifications and exceptions only; FileResource(is_binary=) becomes encoding; MCP_* env vars are gone with pydantic-settings; Streamable HTTP servers reject bodies over 4 MiB with HTTP 413. The migration guide covers all of it.

Known gaps

The tasks extension (SEP-2663) is not part of this release. On the client, the DPoP proof binding (SEP-1932) and the workload-identity jwt-bearer grant are not implemented; both are additive and can land in 2.x.

Feedback

... (truncated)

Commits

• 6f69a37 Present v2 as the stable release across the README, docs, and policies (#3178)
• 78e6fbb Serve v2 docs at the site root, with permanent per-major paths (#3176)
• af06330 Remove unused StreamableHTTPTransport.get_session_id() (#3205)
• 68ca87e Document the two-line release process for stable v2 (#3179)
• c9c431b Expose the middleware chain on MCPServer and stop sending unrequested change ...
• 528e366 Fail fast on server-to-client requests in JSON-response mode instead of hangi...
• 27f5cc7 Remove unused mcpserver.exceptions.ValidationError (#3199)
• 89c5e70 Gate log notifications on the per-request log-level opt-in at 2026-07-28 (#3198)
• b61ce38 docs: fix off-by-one hl_lines in apps.md (#3196)
• b7c9a91 Add mcp.types as a permanent alias for mcp_types (#3190)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[Paulo Lacerda (placerda)]

Closing this one deliberately. Widening the mcp bound to <3 would let agentops-accelerator[mcp] resolve to mcp 2.0.0, which is a breaking rewrite that AgentOps has not migrated to.

Why this is not safe today

src/agentops/mcp/server.py is written against the v1 API:

from mcp.server.fastmcp import FastMCP
server = FastMCP("agentops")

In mcp 2.x, FastMCP is replaced by MCPServer and the module layout changed. tests/unit/test_mcp_server.py also reaches into server._tool_manager._tools, which its own comment describes as "stable across 1.x".

The upstream v2.0.0 release notes give exactly this guidance:

v1.x is in maintenance mode and will only receive security fixes from now on. [...] If your project is not ready to migrate, keep a <2 upper bound on your requirement (for example mcp>=1.28,<2).

Why the green checks here are not evidence

CI runs uv sync --group dev, which does not install the mcp extra. So _HAS_MCP is False and the only test that actually builds the server is skipped. This PR also touches pyproject.toml only, leaving uv.lock pinned at mcp 1.27.1, so nothing in CI ever resolved 2.x. The checks passing says nothing about 2.x compatibility.

What we are doing instead

• chore(deps): bump mcp from 1.27.1 to 1.28.1 #356 bumps the lock to mcp 1.28.1, which clears the three open security advisories (GHSA for mcp <= 1.27.1 and < 1.28.1).
• A follow-up PR raises the declared floor to mcp>=1.28.1,<2 so that a fresh pip install "agentops-accelerator[mcp]" cannot resolve a vulnerable 1.x, while keeping the <2 cap upstream recommends.

Migrating to mcp 2.x is a real piece of work (rewrite server.py against MCPServer, update the tool-registration test, and add the extra to a CI job so it is actually exercised). That deserves its own tracked change, not a constraint widening.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.