fix: client import & server imports

[jatinsandilya]

Closes issue #511

Motivation and Context

Client imports were broken

How Has This Been Tested?

This is a trivial Metro bundler. Metro seems to have partial support for the exports keyword. Adding a couple of explicit ./client / ./client/index.js entries is the easiest cross-tool fix.

Breaking Changes

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

[cliffhall]

LGTM! 👍

[jatinsandilya]

@cliffhall could you approve it as well? Seems like merging is blocked

[KKonstantinov]

Since client/index is about to be having its own export, probably good to do it with the server?

Also, index.ts is not a barrel file in this SDK, so you'll get a limited amount of types/classes exported by it.

Have suggested going for a single point of exports in #716, an introduction of a barrel index file can be done without it being a breaking change for both clients and servers.

[cliffhall]

@cliffhall could you approve it as well? Seems like merging is blocked

Also, in the title for this PR, what does RN refer to? This is a change to package.json

[cliffhall]

Since client/index is about to be having its own export, probably good to do it with the server?

This makes sense. @jatinsandilya would you care to add that?

Also, index.ts is not a barrel file in this SDK, so you'll get a limited amount of types/classes exported by it.

Have suggested going for a single point of exports in #716, an introduction of a barrel index file can be done without it being a breaking change for both clients and servers.

@KKonstantinov agreed, but until we get a single point of exports (a good Idea I heartily support), this PR fixes a current problem in the field, and I think we should move ahead with it when we have the servers/index change added. Do you foresee any problems with refactoring toward index.ts being single barrel file subsequently?

[jatinsandilya]

Since client/index is about to be having its own export, probably good to do it with the server?

This makes sense. @jatinsandilya would you care to add that?

Also, index.ts is not a barrel file in this SDK, so you'll get a limited amount of types/classes exported by it.
Have suggested going for a single point of exports in #716, an introduction of a barrel index file can be done without it being a breaking change for both clients and servers.

@KKonstantinov agreed, but until we get a single point of exports (a good Idea I heartily support), this PR fixes a current problem in the field, and I think we should move ahead with it when we have the servers/index change added. Do you foresee any problems with refactoring toward index.ts being single barrel file subsequently?

Ah it was React Native, since the original issue was about RN.

1. I've updated the PR title now for clarity
2. Added server exports