-
Notifications
You must be signed in to change notification settings - Fork 3.2k
improvement(deployed-mcp): added the ability to make the visibility for deployed mcp tools public, updated UX #2853
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
…or deployed mcp tools public, updated UX
Greptile SummaryThis PR adds public visibility for deployed MCP tools and significantly improves the UX for MCP server management. The implementation includes database schema changes, API route updates to conditionally bypass authentication for public servers, and extensive UI enhancements. Key Changes
Technical ImplementationThe public visibility feature works by:
The migration to React Query consolidates deployment logic across chat, form, and MCP deployments, creating reusable hooks in Confidence Score: 4/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant Client as MCP Client
participant API as MCP Serve Route
participant Auth as Authentication
participant TokenGen as Token Generator
participant Workflow as Workflow Executor
participant DB as Database
Client->>API: POST /api/mcp/serve/{serverId}
API->>DB: Fetch server (isPublic, createdBy)
DB-->>API: Server configuration
alt Server is Public
Note over API,Auth: Skip auth check
API->>TokenGen: Generate temporary token
TokenGen-->>API: Internal JWT
API->>Workflow: Execute with owner context
else Server is Private
API->>Auth: Verify request credentials
Auth-->>API: Validation result
alt Auth Failed
API-->>Client: 401 Unauthorized
else Auth Success
API->>Workflow: Execute with user context
end
end
Workflow->>Auth: Verify credentials
Auth-->>Workflow: Extract user context
Workflow->>DB: Execute as workflow owner
DB-->>Workflow: Execution results
Workflow-->>API: Response
API-->>Client: MCP tool output
|
26c1362 to
65b18d1
Compare
…reactquery instead of manual state management
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
36 files reviewed, 1 comment
Summary
Type of Change
Testing
Tested manually
Checklist