Add MCP to server#2091
Open
shangyian wants to merge 7 commits intoDataJunction:mainfrom
Open
Conversation
✅ Deploy Preview for thriving-cassata-78ae72 canceled.
|
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.
Summary
DJ's current MCP server only speaks stdio - we provide a
dj-mcpCLI that users can run locally that translates stdio MCP requests into HTTP calls back to DJ. That works for some clients like Claude Desktop, but locks out HTTP-based MCP consumers (e.g., Slack agents or other hosted assistants).This PR makes DJ a first-class HTTP MCP server. Tools live next to the code they wrap, meaning that latency also drops (no self-HTTP loop), and the stdio CLI shrinks to a thin proxy for the few clients that still need stdio.
Test Plan
make checkpassesmake testshows 100% unit test coverageDeployment Plan