BRONTO-1667 initial version of Bronto MCP server#1
Merged
Conversation
mcgauranc
approved these changes
May 19, 2025
mcgauranc
left a comment
mcgauranc
left a comment
Contributor
There was a problem hiding this comment.
wow. i really thought there would be more to setting this up.
Contributor
Author
|
The key at https://github.com/brontoio/bronto-mcp-server/pull/1/files#diff-7af7e68a71752070663b2e844b9554da443774f64aba9695f7f034ad39bcaa96R6 was only temporary and has been deleted. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Down the line, we'll probably want to rely on library regarding ways to express time in plain english.
Also having a Bronto python client may be a good idea (maybe we can autogenerate one with some tool, from our openapi spec).
This is just a P.O.C. We can change anything there. For instance, log data retrieval is currently done using
export. This is to accommodate a use case that I wanted to test but moved away from.