Access different environments

Accessing Deprecations in Specific Environments with Tideways MCP Server

A user is encountering difficulty retrieving deprecation issues from a specific environment (UAT1) using the Tideways MCP Server's REST API. Despite specifying parameters like environment: "UAT1" and status: "all" in their request, the API appears to default to environment: "production" and status: "open", hindering their ability to fetch the desired deprecation data. The user is also unsure if the deprecation search itself is functioning correctly.

Possible Root Cause

Without further information from the Tideways team or community, it's difficult to pinpoint the exact root cause. However, several possibilities exist:

• Parameter Handling Bug: The MCP Server might have a bug in how it parses or applies the environment and status parameters from the API request. This could lead to the server ignoring the provided values and using default settings instead.
• Configuration Issue: There might be a misconfiguration on the server-side that forces the environment to "production" regardless of the request parameters. This could be an environment variable or a setting within the MCP Server's configuration files.
• API Documentation Error: The API documentation could be inaccurate regarding how to specify the environment and status parameters for deprecation searches. The user might be using the parameters correctly according to the documentation, but the API behaves differently in practice.
• Data Availability: It's also possible that there are simply no deprecation issues with the status "all" (which would include closed ones) in the UAT1 environment within the specified timeframe.

Solution and Workarounds

Until the Tideways team investigates and resolves the underlying issue, here are some potential workarounds and troubleshooting steps:

1. Verify Parameter Names and Values: Double-check the API documentation to ensure you are using the correct parameter names (e.g., environment, status) and allowed values (e.g., UAT1, all). Case sensitivity might be a factor.
2. Experiment with Different Status Values: Try explicitly requesting "open" and "closed" statuses separately to see if either returns results for the UAT1 environment. This can help determine if the problem lies specifically with the "all" status.
3. Check the Request Payload: Ensure that the JSON payload being sent to the API is correctly formatted and contains the desired parameters. Use a tool like curl or Postman to inspect the raw request and response. For example:

   
   {
     "organization": "<ORGNAME>",
     "application": "<APPNAME>",
     "environment": "UAT1",
     "service": "<SERVICENAME>",
     "range": {
       "startDate": "2025-11-19 09:36:17",
       "endDate": "2025-11-19 10:36:16",
       "minutes": 60
     },
     "page": 1,
     "status": "all",
     "issue_type": "deprecated"
   }
   

4. Contact Tideways Support: The most effective solution is to report the issue to the Tideways support team. Provide them with detailed information about your API requests, the expected behavior, and the actual results. Include the raw request and response data for easier debugging.
5. Inspect Server Logs (If Possible): If you have access to the MCP Server's logs, examine them for any error messages or warnings related to API requests or parameter handling. This might provide clues about the root cause of the issue.

Related Considerations

When working with different environments, it's crucial to have a clear understanding of your data and configuration management. Ensure that the UAT1 environment is properly configured with the necessary data for deprecation detection. Also, consider implementing robust error handling and logging in your application to catch and report API issues more effectively.