Update Readme to redirect to the docs site#277
Conversation
|
I don't think this make sense to update the changelog so hopefully that's an okay failing test |
|
As we now have more space in the README 😄, can we mention the With the docs on the official docs site, people landing here might be the more technical ones looking for how to integrate the MCP server into their agentic workflows. |
@b-per of course :) but what would you like to say? Since shouldn't folks integrating with their agentic workflows also be going to our docs? I think it makes more sense to link back to those files in our docs to make it more consistent. We don't put "more technical" example in the dbt core repo either. |
Co-authored-by: Devon Fulcher <24593113+DevonFulcher@users.noreply.github.com>
Yes, we can add the examples to docs.getdbt.com, but they aren't added so far, are they? |
|
@b-per nope! not yet. we will want to write something more fully on it. Perhaps we start there? |
|
@DevonFulcher @b-per could we merge this in and then follow up with more? |
| ## Troubleshooting | ||
|
|
||
| - Some MCP clients may be unable to find `uvx` from the JSON config. If this happens, try finding the full path to `uvx` with `which uvx` on Unix systems and placing this full path in the JSON. For instance: `"command": "/the/full/path/to/uvx"`. | ||
| For integration guides, we do |
There was a problem hiding this comment.
I think you meant to finish this part?
3 participants
Related to this issue #276