deepset-ai / deepset-ai/haystack-core-integrations
After Haystack 3.0: refactor the MCP integration to use the async tool
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 203
- Forks
- 332
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 80
Description
In Haystack 3.0, we'll introduce support for async tools.
Given this, it should be possible to simplify this integration, where much work is done to bridge sync/async.
If we end up implementing tool lifecycle handling (https://github.com/deepset-ai/haystack-private/issues/426), this should be adopted in this component, leading to further simplification.
👋 Hello there! This issue will be handled internally and isn't open for external contributions. If you'd like to contribute, please take a look at issues labeled contributions welcome or good first issue. We'd really appreciate it!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the MCP integration; the issue names no files, tests, or entry points. Read Haystack 3.0's async tool support and the linked tool lifecycle issue, then determine how the integration can adopt them and what sync/async bridging remains to remove.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100