Skip to content

fix: correct JSDoc on McpServerConfigSchema to describe actual resolver mechanics #310

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.

Sign up for GitHub

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

Merged
sroussey merged 2 commits into from
Mar 14, 2026
+4 −2
Merged

fix: correct JSDoc on McpServerConfigSchema to describe actual resolver mechanics #310

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
84efb1e
Initial plan
Copilot Mar 13, 2026
688c5da
fix: correct doc comment on McpServerConfigSchema to accurately descr…
Copilot Mar 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions packages/tasks/src/mcp-server/McpServerSchema.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,10 @@ import { DataPortSchemaObject, FromSchema, mcpServerConfigSchema } from "@workgl
/**
* A lightweight MCP server configuration suitable for task config/input schemas.
*
* When a string `server_id` is provided, the input resolver system resolves it
* to the full server record from the registry.
* This schema carries `format: "mcp-server"`. Task input properties annotated
* with that format (e.g. a `server` field) are resolved by the input resolver
* system: when such a property receives a plain string, the resolver looks up
* that ID in the MCP server registry and substitutes the full server config object.
*/
export const McpServerConfigSchema = {
type: "object",
Expand Down