Skip to content

Conversation

@jairad26
Copy link
Collaborator

No description provided.

@jairad26
Copy link
Collaborator Author

@calclavia @arjunkmrm
would either of you mind taking a look at this pr to ensure i set up the env vars correctly for smithery? if theres also a way to test the config locally that would be extremely helpful

@arjunkmrm
Copy link

@jairad26 just added my comments. At the moment there isn't a way to test the config locally - but you can easily commit your changes and hit deploy on your server settings to fetch the latest updates to your repo. Let me know if you run into any issues as you deploy, I'm happy to help

@jairad26
Copy link
Collaborator Author

Hi @arjunkmrm , thanks for the quick reply, though i don't see any comments. could you double check that you submitted the comments?

smithery.yaml Outdated
clientType:
type: string
enum:
- "http"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jairad26 we don't support enum yet - the server can validate and throw an error for this instead. Would recommend adding the allowed values to the description instead

@arjunkmrm
Copy link

@jairad26 oops forgot to submit! you should see it now

@jairad26 jairad26 merged commit 442090a into main Apr 1, 2025
2 checks passed
@arjunkmrm
Copy link

@jairad26 you can claim the server at https://smithery.ai/server/@chroma-core/chroma-mcp and deploy it to sync the updates here onto smithery.

@jairad26 jairad26 deleted the smithery-update branch April 2, 2025 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants