Spec: MCP direct endpoint to expose all proxied tools#280
Draft
technicalpickles wants to merge 2 commits intosmart-mcp-proxy:mainfrom
Draft
Spec: MCP direct endpoint to expose all proxied tools#280technicalpickles wants to merge 2 commits intosmart-mcp-proxy:mainfrom
technicalpickles wants to merge 2 commits intosmart-mcp-proxy:mainfrom
Conversation
Related smart-mcp-proxy#279 Adds feature specification for a new `/mcp/direct` endpoint that exposes all upstream MCP tools directly alongside internal MCPProxy tools. This spec documents the design decisions, user stories, functional requirements, and success criteria for the feature. Implementation will follow in subsequent commits. ## Key Design Decisions - Config flag `enable_direct_endpoint` (default: false, opt-in) - Quarantined/disabled/disconnected servers excluded - Tool annotations preserved from upstream - Upstream tools namespaced as `server:tool` ## Spec Contents - 5 prioritized user stories (P1-P3) - 15 functional requirements - 5 measurable success criteria - Edge cases and assumptions documented
- Add User Story 6: Admin Server Management (disable/enable/quarantine) - Add FR-016: Require `notifications/tools/list_changed` for tool sync - Add SC-006: Notification delivery within 1 second of admin action - Update FR-003: Exclude redundant search-workflow tools from /mcp/direct - Update Key Entities: Document notification mechanism Related smart-mcp-proxy#279
Contributor
|
@technicalpickles This PR makes a lot of sense! I've added some details to the spec:
These changes ensure the spec covers the full MCP protocol compliance for dynamic tool list updates. |
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
2 participants
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
This PR adds the specification for a new
/mcp/directendpoint that exposes all upstream MCP tools directly alongside internal MCPProxy tools.Related #279
Motivation
Per Anthropic's Advanced Tool Use announcement, AI platforms are adopting built-in tool search capabilities. This creates a need for MCPProxy to support direct tool access without the search-first workflow, while preserving its other value (centralized auth, Docker sandboxing, single management point).
What This PR Contains
Specification only - no implementation yet.
specs/025-mcp-direct-endpoint/spec.md- Full feature specificationspecs/025-mcp-direct-endpoint/checklists/requirements.md- Quality validation checklistKey Design Decisions
enable_direct_endpointfalseserver:toolfor upstreamSpec Highlights
Next Steps
/speckit.planto generate implementation planTest Plan