Add embeddings, segmenter, and tokenizer as MCP tools#24
Open
SBALAVIGNESH123 wants to merge 1 commit into
Open
Add embeddings, segmenter, and tokenizer as MCP tools#24SBALAVIGNESH123 wants to merge 1 commit into
SBALAVIGNESH123 wants to merge 1 commit into
Conversation
Expose Jina embeddings and segmenter APIs as first-class MCP tools. These APIs were already used internally (embeddings in dedup tools, segment in token guardrail) but never surfaced to MCP clients. - generate_embeddings: vector embeddings via /v1/embeddings - segment_text: semantic chunking via /v1/segment - count_tokens: lightweight token counting via /v1/segment Registered under new 'embedding' tag for tool filtering. No new dependencies. Closes jina-ai#2.
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
1 participant
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.
Hey, noticed the embeddings and segment APIs are used internally (embeddings for the dedup tools, segment for the token guardrail) but aren't exposed as tools that MCP clients can actually call directly.
This adds three new tools:
Everything follows the same pattern as the existing tools (getProps, checkBearerToken, handleApiError, yamlStringify responses, createErrorResponse in catch). Added them to ALL_TOOLS, created a new 'embedding' tag in TOOL_TAGS, updated the server instructions so LLMs know when to pick these tools, and added descriptions to the root endpoint.
No new dependencies, no new files. Bumped version to 1.5.0.
Closes #2