Skip to content

Conversation

@filiphr
Copy link

@filiphr filiphr commented Jan 12, 2026

The goal of this PR is to add support for Jackson 3.

Motivation and Context

Jackson 3 is the latest version from Jackson and it is the next iteration of Jackson.

How Has This Been Tested?

The existing tests were enough

Breaking Changes

The Java MCP SDK now pulls in Jackson 3 instead of Jackson 2. This can be potentially a breaking change in case someone was using io.modelcontextprotocol.json.jackson.JacksonMcpJsonMapper then they would need to switch to io.modelcontextprotocol.json.jackson3.JacksonMcpJsonMapper and / or adjust the dependencies so that they pull mcp-core and mcp-json-jackson3

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

@sdeleuze
Copy link
Contributor

@filiphr I was about to submit such PR, so thanks for creating it.

I think I would prefer to have consistency between mcp-json-jackson2 and mcp-json-jackson3 package naming strategy (version-less or with version), see my related #562 (comment) comment, but that would be a breaking change, so let see with the team what is the preferred solution.

@filiphr
Copy link
Author

filiphr commented Jan 12, 2026

Thanks for your comment @sdeleuze. I've read your comment #562 (comment) and I've added an alternative idea in #562 (comment).

In any case, I stumbled onto this since I wanted to contribute Jackson 3 support for Spring AI, but that depends on this project, so I started here first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants