Skip to content

(bug) Unable to resolve "@modelcontextprotocol/sdk/client/index" #511

Closed
Closed
(bug) Unable to resolve "@modelcontextprotocol/sdk/client/index"#511
Labels
P1Significant bug affecting many users, highly requested featurebugSomething isn't workingready for workEnough information for someone to start working on
Milestone
package issues

Description

@thearyanag
thearyanag
opened on May 18, 2025

Describe the bug
Trying to integrate into a react native project, and getting

Unable to resolve "@modelcontextprotocol/sdk/client/index.js" from "src/hooks/useChat.ts"

when importing

import { Client } from "@modelcontextprotocol/sdk/client/index.js";

To Reproduce
Steps to reproduce the behavior:

  1. Install @modelcontextprotocol/sdk in any react native project
  2. Try to import the sdk in any random TS file

Expected behavior
A clear and concise description of what you expected to happen.
I expect it to import properly

Activity

  1. thearyanag
    added
    bugSomething isn't working
    on May 18, 2025

  2. PhoneixT commented on May 20, 2025

    @PhoneixT
    PhoneixT
    on May 20, 2025

    +1

  3. kanishq1 commented on May 20, 2025

    @kanishq1
    kanishq1
    on May 20, 2025

    +1

  4. ms-sch commented on May 22, 2025

    @ms-sch
    ms-sch
    on May 22, 2025

    +1

  5. gabehyland commented on Jun 26, 2025

    @gabehyland
    gabehyland
    on Jun 26, 2025

    +1

  6. Pizzaface
    added a commit that references this issue on Aug 20, 2025

    Merge pull request modelcontextprotocol#511 from modelcontextprotocol…

    21fd2f9
  7. felixweinberger
    added
    ready for workEnough information for someone to start working on
    P0Broken core functionality, security issues, critical missing feature
    on Oct 27, 2025
  8. felixweinberger
    added this to the package issues milestone on Oct 27, 2025
  9. felixweinberger
    added this to 2025-11-25 Implementationon Oct 30, 2025
  10. felixweinberger
    moved this to Backlog in 2025-11-25 Implementationon Oct 30, 2025
  11. felixweinberger
    moved this from Backlog to Ready in 2025-11-25 Implementationon Oct 30, 2025

  12. KKonstantinov commented on Dec 5, 2025

    @KKonstantinov
    KKonstantinov
    on Dec 5, 2025
    Contributor

    Planned for v2 (#809) and planned in PR #870

  13. KKonstantinov
    closed this as completedon Dec 5, 2025
  14. github-project-automation
    moved this from Ready to Done in 2025-11-25 Implementationon Dec 5, 2025
  15. felixweinberger
    added
    P1Significant bug affecting many users, highly requested feature
    and removed
    P0Broken core functionality, security issues, critical missing feature
    on Feb 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Significant bug affecting many users, highly requested featurebugSomething isn't workingready for workEnough information for someone to start working on

    Type

    No type

    Projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions