0.7.0

Breaking Changes

Important

This release contains breaking API changes.

If you've implemented custom transports or directly referenced MCP error types, you'll need to update your code.

Error renamed to MCPError

Renamed the Error type to MCPError to avoid namespace collision with Swift's standard Error protocol. The MCPError type now properly conforms to Swift.Error.

// Old code
catch let error as MCP.Error {
    // Handle MCP error
}

// New code
catch let error as MCPError {
    // Handle MCP error
}

Transport protocol updated to use Data instead of String

The Transport protocol methods now work with Data instead of String to avoid unnecessary memory copies:

// Old protocol signature
func send(_ message: String) async throws
func receive() async throws -> String

// New protocol signature
func send(_ data: Data) async throws
func receive() async throws -> Data

This change should not affect most users who rely on the standard StdioTransport, but will require updates if you've implemented a custom transport.

What's Changed

• Update README to reflect MIT License by @mattt in #41
• Add configurable strict mode for MCP client initialization by @mattt in #43
• Update transports to send and receive data instead of strings by @mattt in #42
• Rename Error to MCPError by @mattt in #44
• Add Changelog section to README by @mattt in #45

Full Changelog: 0.6.0...0.7.0