Skip to content
Last updated

🔨 In Development — This section is still being developed and may change.
Force a refresh of the cached tool definitions for a personal connector configuration. This fetches the latest tools from the MCP server and updates the cache.
POSThttps://api.freddy.aitronos.com/v1/personal-connectors/configurations/{config_id}/refresh

This endpoint invalidates the current tool cache and fetches fresh tool definitions from the MCP server. Use this when:

  • The MCP server has been updated with new tools
  • You suspect the cache is stale or incorrect
  • You want to ensure you have the latest tool definitions

Path Parameters

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

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

Response

{
  "success": true,
  "message": "Tool cache refreshed successfully.",
  "details": {
    "configurationId": "pconf_abc123",
    "toolsDiscovered": 8,
    "previousToolCount": 6,
    "newTools": ["clickup_update_task_status", "clickup_add_attachment"],
    "removedTools": [],
    "cachedAt": "2025-10-07T12:45:00Z",
    "expiresAt": "2025-10-07T13:45:00Z"
  }
}

Cache Invalidation

When you refresh a configuration:

  1. Old Cache Deleted: The existing cached tool definitions are immediately invalidated
  2. Fresh Fetch: New tool definitions are fetched from the MCP server
  3. New Cache Created: The fresh tools are cached with a new expiration time (1 hour by default)
  4. Active Sessions Updated: Any active assistant sessions using this configuration will receive the updated tools on their next request

Response Details

The response includes useful information about what changed:

  • toolsDiscovered - Total number of tools now available
  • previousToolCount - Number of tools before refresh
  • newTools - Array of newly discovered tool names
  • removedTools - Array of tools that are no longer available
  • cachedAt - When the new cache was created
  • expiresAt - When the new cache will expire

Use Cases

  • After MCP Server Update: Refresh after deploying a new version of an MCP server
  • New Features: Get access to newly added tools immediately
  • Troubleshooting: Clear potentially corrupted cache data
  • Development: Refresh frequently during connector development
  • Scheduled Maintenance: Refresh as part of regular maintenance routines

Rate Limiting

⚠️ Note: This endpoint bypasses the cache and makes a direct request to the MCP server. Excessive use may impact MCP server performance. Use sparingly and only when necessary.