New. tools #29
Merged
New. tools #29
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Pull Request Overview
This pull request updates the README to introduce two new tools.
- Added Markitdown, a lightweight Python utility for converting various files to Markdown.
- Added MarkItDown-MCP, a SSE MCP server for calling MarkItDown.
Comments suppressed due to low confidence (1)
README.md:1550
- The naming 'MarkItDown' appears inconsistent with 'Markitdown' in the previous entry. Consider standardizing the casing for clarity.
9. A SSE MCP server for calling MarkItDown - [MarkItDown-MCP](https://github.com/microsoft/markitdown/tree/main/packages/markitdown-mcp)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Overview
Please provide a brief summary of the changes made in this pull request.
This helps reviewers understand the context and intent of your changes.
Changes Introduced
List specific changes made (e.g., added new or refactored existing syntax).
Include reasons for complex or significant changes
Linked Issue(s)
Fixes #123)Additional Notes