MCP Troubleshooting
Verification Needed
MCP troubleshooting details will be added when the MCP server is available.
This page will cover common issues and solutions when working with the eCourtDate MCP server.
Anticipated Common Issues
Connection Failures
- Symptom: The MCP client cannot connect to the eCourtDate MCP server.
- Possible causes: Incorrect server URL, network connectivity issues, firewall blocking the connection.
- Solution: Verify the server URL in your MCP client configuration. Check that your network allows outbound connections to the MCP server endpoint.
Authentication Errors
- Symptom: The MCP server rejects your connection with an authentication error.
- Possible causes: Invalid or expired
client_id/client_secret, incorrect credential configuration. - Solution: Verify your credentials in the eCourtDate Console. Ensure they are correctly configured in your MCP client. See MCP Authentication for details.
Tool Execution Failures
- Symptom: An MCP tool call returns an error instead of the expected result.
- Possible causes: Invalid input parameters, insufficient permissions, server-side errors.
- Solution: Check the error message for details. Verify that your API credentials have the necessary permissions for the requested operation. Review the tool's input schema to ensure parameters are correct.
Timeout Errors
- Symptom: MCP requests take too long and time out.
- Possible causes: Network latency, large data queries, server load.
- Solution: Try narrowing your query (e.g., add date filters or limit result counts). Check your network connection stability.
Diagnostic Steps
- Verify your MCP client is using the correct server URL and transport protocol.
- Test your API credentials independently using the REST API to confirm they are valid.
- Check the MCP client logs for detailed error messages.
- Try a simple tool call (e.g., listing resources) to isolate the issue.
Contact Support
For MCP issues that cannot be resolved through the steps above, contact eCourtDate support at help@ecourtdate.com.