Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

reactivate_provider

Restores access for a deactivated provider in the LumbreTravel MCP Server by specifying the provider's ID, enabling renewed API integration and services management.

Instructions

Reactivar un proveedor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID del proveedor a reactivar

Implementation Reference

  • MCP tool handler for 'reactivate_provider': extracts id from args, calls apiService.reactivateProvider(id), and returns JSON response.
    case 'reactivate_provider': { const { id } = args as { id: string } const provider = await this.apiService.reactivateProvider(id) return { content: [{ type: 'text', text: JSON.stringify(provider, null, 2) }] } }
  • Tool registration and schema definition in listTools(): defines name, description, and input schema requiring 'id'.
    { name: 'reactivate_provider', description: 'Reactivar un proveedor.', inputSchema: { type: 'object', properties: { id: { type: 'string', description: 'ID del proveedor a reactivar' } }, required: ['id'] } },
  • ApiService method that performs the actual API call to reactivate a provider by ID via PUT request.
    async reactivateProvider (id: string) { const headers = await this.getHeaders() const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/provider/reactivate`, { method: 'PUT', headers, body: JSON.stringify({ id }) }) return await this.handleResponse<any>(response) }

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lumile/lumbretravel-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server