-
Notifications
You must be signed in to change notification settings - Fork 42
"Failed to get tools" error seen when adding PostgreSQL MCP server and no tools get added. #2977
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.
By clicki 8000 ng “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
Comments
im going to assume that you let the ${input:pg_url} as-is and didnt modify it at all. that is the problem. @njhale this is a good real world scenario to fix using the variable expansion. My expectation for the full end-to-end fix for this is thatyou modify this entry in daishans catalog to make the pg url an env var and that ulimately gets piped all the way through to this UI and the user just has to put in the pg url as an env var |
put as really high just because it is what youre already working on |
note that you will be able to log into the catalog service to make these modifications. see here: https://acorn-io.slack.com/archives/C03FU91U4SX/p1747435736873229 |
@njhale im moving this to testing now that the variable stuff is in |
Describe the bug
"Failed to get tools" error seen when adding PostgreSQL MCP server and no tools get added.
To Reproduce
Steps to reproduce the behavior:
PostgreSQL MCP server
Notice that user is presented with the following error message

PostgreSQL MCP server
itself gets added to the agent with no tools.When trying to list the tools for this server by selecting this server from the tools option presented in the chat view, we are stuck in the is state forever:
The text was updated successfully, but these errors were encountered: