Merged
Conversation
agtraveso
approved these changes
Feb 24, 2026
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
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.
Note
Low Risk
Documentation-only updates; no runtime behavior, APIs, or security logic changes.
Overview
Expands the README’s product positioning by clarifying YepCode as a dynamic MCP tools server: each process can be exposed as a tool, tool inputs are defined via JSON Schema, and tools can be implemented in Python or Node.js.
Adds a dedicated section detailing the “one process, one tool” model, supported auth options (OAuth/API tokens/credentials), and how tags map to exposed tools.
Written by Cursor Bugbot for commit 7896b7a. This will update automatically on new commits. Configure here.