Fix smithery.yaml: Add missing runtime: typescript declaration #1
Conversation
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
The smithery.yaml was missing the required 'runtime: typescript' field, causing deployment failures on Smithery with invalid_literal errors. This field is required by the Smithery config schema and is present in the working exa-mcp-server configuration. Fixes the deployment error: - Invalid literal value, expected "typescript" - Invalid input for startCommand Tested locally with npm install and build:stdio - builds successfully. Co-Authored-By: Tanishq Jaiswal <tanishq.jaiswal97@gmail.com>
Original prompt from Tanishq |
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
10ishq
approved these changes
Oct 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix smithery.yaml: Add missing runtime: typescript declaration
Summary
Fixes Smithery deployment failure by adding the required
runtime: typescriptfield to smithery.yaml. The previous config only hadname: websetswhich caused validation errors during deployment.Root cause: Smithery's config schema requires either
runtime: typescriptorruntime: pythonto be explicitly declared. The websets-mcp-server was missing this field while exa-mcp-server had it correctly configured.Changes:
smithery.yamlfromname: websetstoruntime: typescriptto match exa-mcp-server's working configurationValidation:
npm installwhich runs the prepare script → build:stdio completed successfully.smithery/stdio/index.cjs(595.34 KB)Review & Testing Checklist for Human
Notes
Invalid literal value, expected "typescript"which directly led to this fixLink to Devin run: https://app.devin.ai/sessions/a6b83525c3384b38b2b822b32b11ae7c
Requested by: Tanishq Jaiswal (tanishq@exa.ai) / @10ishq