@mseep/mcp-openapi-schema-explorer/memory-bank/activeContext.md

MCP OpenAPI schema explorer

# Active Context

## Current Focus

Successfully upgraded @modelcontextprotocol/sdk and addressed breaking changes in test mocks.

## Implementation Status

- @modelcontextprotocol/sdk updated from 1.8.0 to 1.10.1
- Updated all test mocks to include new RequestHandlerExtra properties (sendNotification, sendRequest)
- Modified test files:
  - component-map-handler.test.ts
  - component-detail-handler.test.ts
  - operation-handler.test.ts
  - path-item-handler.test.ts
  - top-level-field-handler.test.ts
- All tests passing successfully
- Server now loads OpenAPI v3.0 and Swagger v2.0 specs from local files or remote URLs
- Swagger v2.0 specs are automatically converted to v3.0
- Internal references are transformed to MCP URIs
- Added `json-minified` output format option
- Server name is now dynamically set based on the loaded spec's `info.title`
- Automated versioning and release process implemented using `semantic-release`
- CI workflow adapted for Node 22, uses `just` for checks, and includes a `release` job
- Docker support added with automated Docker Hub publishing
- Dependencies correctly categorized
- Resource completion logic implemented
- Dynamic server name implemented
- Minified JSON output format added
- Remote spec loading and Swagger v2.0 conversion support added
- Core resource exploration functionality remains operational
- Unit tests updated for latest SDK version
- E2E tests cover all main functionality

## Recent Changes

### SDK Update & Test Fixes (✓)

1. **Dependency Update:**

   - Updated @modelcontextprotocol/sdk from 1.8.0 to 1.10.1 in package.json
   - Identified breaking changes in RequestHandlerExtra type requiring sendNotification and sendRequest properties

2. **Test Suite Updates:**
   - Added missing RequestHandlerExtra properties to mockExtra objects in all handler tests
   - Confirmed test fixes by running full test suite
   - Verified no other test files needed similar updates

## Next Actions

1. **Continue with Previous Plans:**

   - Complete README updates with release process details
   - Clean up any remaining TODOs in codebase
   - Address minor ESLint warnings

2. **Documentation:**

   - Document the SDK upgrade in CHANGELOG.md
   - Update dependencies section in relevant documentation

3. **Testing:**

   - Monitor for any new breaking changes in future SDK updates
   - Consider adding test utilities to simplify mock creation

4. **Code Cleanup:**
   - Refactor duplicated mock setup code in tests
   - Consider creating shared test fixtures for common mocks

## Future Considerations

1. **SDK Integration:**

   - Stay updated with MCP SDK releases
   - Plan for future breaking changes
   - Consider automated dependency update checks

2. **Testing Infrastructure:**

   - Improve test mock reusability
   - Add test coverage for edge cases
   - Consider adding integration tests

3. **Previous Future Considerations:**
   - Implement reference traversal/resolution service
   - Enhance support for all component types