Skip to content
/
Test connection
Last updated

Test Personal Connector Configuration

🔨 In Development — This section is still being developed and may change.
Test the connection to a personal connector's MCP server and verify that credentials are valid. This endpoint performs a health check without executing any tools.
POSThttps://api.freddy.aitronos.com/v1/personal-connectors/configurations/{config_id}/test

This endpoint attempts to connect to the MCP server associated with this configuration and verifies that:

  • The server is reachable
  • Authentication credentials are valid
  • The server is responding correctly

This is useful for troubleshooting connection issues or verifying a new configuration before using it.

Path Parameters

config_id string required The ID of the personal connector configuration to test (e.g., pconf_abc123).

Bash
curl https://api.freddy.aitronos.com/v1/personal-connectors/configurations/pconf_abc123/test \
  -X POST \
  -H "Authorization: Bearer $FREDDY_API_KEY"

Response

{
  "status": "healthy",
  "message": "Connection successful. MCP server is responding correctly.",
  "details": {
    "serverUrl": "http://clickup-mcp:8000",
    "serverType": "http",
    "responseTimeMs": 145,
    "serverVersion": "1.0.0",
    "availableTools": 8
  },
  "testedAt": "2025-10-07T12:30:00Z"
}

Health Status Values

The status field can have the following values:

  • healthy - Server is reachable, credentials are valid, and the server is responding correctly
  • unhealthy - Server is unreachable, credentials are invalid, or the server is not responding correctly

Automatic Health Updates

When you test a configuration:

  • The configuration's healthStatus field is automatically updated based on the test result
  • The lastSyncAt field is updated to the current timestamp
  • If unhealthy, the lastError field is populated with the error message

Use Cases

  • Initial Setup: Test a new configuration after creation to ensure it works
  • Troubleshooting: Diagnose connection issues when a connector isn't working
  • Credential Rotation: Verify new credentials after updating them
  • Monitoring: Periodically check the health of your connectors
  • Pre-Deployment: Test configurations before enabling them in production
Previous page
Next page