Prerequisites
What are you trying to do that currently feels hard or impossible?
Navigating to the base URL of an integration, such as https://mcp-toolbox.dev/integrations/alloydb/, currently results in a dead end. Users clicking on the top-level integration name (e.g., AlloyDB PostgreSQL) expect to see an overview or the main configuration page, but instead hit a page with no content.
Expected behavior
The base path for any integration (e.g., /integrations/<integration_name>/) should automatically redirect users to its corresponding /source endpoint (e.g., /integrations/<integration_name>/source/).
Suggested Solution(s)
Implement an automatic redirect rule in the documentation site's routing configuration so that whenever a user navigates to an integration's root directory, they are seamlessly redirected to the source documentation page.
For example:
https://mcp-toolbox.dev/integrations/alloydb/ ➡️ https://mcp-toolbox.dev/integrations/alloydb/source/
This should be applied globally across all existing integrations to prevent similar dead ends.
Alternatives Considered
This could be another page with an overview.
Additional Details
No response
Prerequisites
What are you trying to do that currently feels hard or impossible?
Navigating to the base URL of an integration, such as https://mcp-toolbox.dev/integrations/alloydb/, currently results in a dead end. Users clicking on the top-level integration name (e.g., AlloyDB PostgreSQL) expect to see an overview or the main configuration page, but instead hit a page with no content.
Expected behavior
The base path for any integration (e.g., /integrations/<integration_name>/) should automatically redirect users to its corresponding /source endpoint (e.g., /integrations/<integration_name>/source/).
Suggested Solution(s)
Implement an automatic redirect rule in the documentation site's routing configuration so that whenever a user navigates to an integration's root directory, they are seamlessly redirected to the source documentation page.
For example:
https://mcp-toolbox.dev/integrations/alloydb/ ➡️ https://mcp-toolbox.dev/integrations/alloydb/source/
This should be applied globally across all existing integrations to prevent similar dead ends.
Alternatives Considered
This could be another page with an overview.
Additional Details
No response