# Test Personal Connector Configuration

div
strong
🔨 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.

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`).

Test connection

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


```python
import requests
import os

api_key = os.environ.get("FREDDY_API_KEY")
headers = {"Authorization": f"Bearer {api_key}"}

response = requests.post(
    "https://api.freddy.aitronos.com/v1/personal-connectors/configurations/pconf_abc123/test",
    headers=headers
)

print(response.json())
```


```javascript
const response = await fetch('https://api.freddy.aitronos.com/v1/personal-connectors/configurations/pconf_abc123/test', {
  method: 'POST',
  headers: {
    'Authorization': `Bearer ${process.env.FREDDY_API_KEY}`
  }
});

const data = await response.json();
console.log(data);
```

## Response

200 OK - Healthy

```json
{
  "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"
}
```

200 OK - Unhealthy

```json
{
  "status": "unhealthy",
  "message": "Authentication failed. Invalid API key.",
  "details": {
    "serverUrl": "http://clickup-mcp:8000",
    "serverType": "http",
    "responseTimeMs": 89,
    "errorCode": "invalid_credentials",
    "errorMessage": "The provided API key is invalid or has been revoked."
  },
  "testedAt": "2025-10-07T12:30:00Z"
}
```

200 OK - Unreachable

```json
{
  "status": "unhealthy",
  "message": "Unable to connect to MCP server. Server may be down or unreachable.",
  "details": {
    "serverUrl": "http://clickup-mcp:8000",
    "serverType": "http",
    "errorCode": "connection_timeout",
    "errorMessage": "Connection timed out after 30 seconds."
  },
  "testedAt": "2025-10-07T12:30:00Z"
}
```

Errors

```json
{
  "error": {
    "type": "not_found_error",
    "message": "Personal connector configuration with ID 'pconf_abc123' not found.",
    "code": "configuration_not_found"
  }
}
```


```json
{
  "error": {
    "type": "authentication_error",
    "message": "Invalid API key",
    "code": "invalid_api_key"
  }
}
```

## 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