-
Notifications
You must be signed in to change notification settings - Fork 10
fix(workflow-executor): match MCP tools by config id #1584
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
Changes from all commits
ecbeed0
acffd6b
63567f9
4edc2e4
ceacd35
095113b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,15 +4,20 @@ export default abstract class RemoteTool<ToolType = unknown> { | |
| base: StructuredToolInterface<ToolType>; | ||
| sourceId: string; | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. sourceId is currently the mcp server name. And Id the mcp server id. Could we improve it by adding a commentary or an alias or ... on other idea?
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. get sourceMcpServerName() => return sourceId.
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If I'm reading this right, Would a short JSDoc here clarifying that it covers both user MCP and Forest connectors be enough, or are you leaning toward the broader
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Well, the Forest connectors and user MCP servers live in the same ai_mcp_configs so currently we treat them all as MCP servers. But yes I think a comment is suitable. Not pushing for the broader
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I've added the comment. |
||
| sourceType: string; | ||
| // Shared across McpServerRemoteTool and ServerRemoteTool because the orchestrator | ||
| // stores Forest connectors alongside user MCP servers in the same ai_mcp_configs table. | ||
| mcpServerId?: string; | ||
|
|
||
| constructor(options: { | ||
| tool: StructuredToolInterface<ToolType>; | ||
| sourceId?: string; | ||
| sourceType?: string; | ||
| mcpServerId?: string; | ||
| }) { | ||
| this.base = options.tool; | ||
| this.sourceId = options.sourceId; | ||
| this.sourceType = options.sourceType; | ||
| this.mcpServerId = options.mcpServerId; | ||
| } | ||
|
|
||
| get sanitizedName() { | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.