Migrate LiteLLM to Merge Gateway

Name: Migrate LiteLLM to Merge Gateway
Availability: InStock
Author: Merge

Detect LiteLLM usage and guide migration to Merge Gateway SDK.

1|Updated Mar 17, 2026

Search Tags:#typescript #python #migration #sdk #migrate #litellm #merge-gateway

Ready to run

npx skills add https://github.com/merge-api/merge-gateway-skills --skill migrate-litellm-to-merge-gateway

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Migrate LiteLLM to Merge Gateway
Source: https://github.com/merge-api/merge-gateway-skills/tree/main/skills/migrate-litellm
Command: npx skills add https://github.com/merge-api/merge-gateway-skills --skill migrate-litellm-to-merge-gateway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate LiteLLM to Merge Gateway to replace self-hosted LiteLLM proxy or the LiteLLM Python library with the managed Merge Gateway.

Core Features & Use Cases

Detects LiteLLM deployment patterns (proxy or library) and maps them to a Merge Gateway migration plan
Guides transitions for both Python and TypeScript/Node codebases, including environment variable updates and model naming
Preserves behavior while migrating to provider-prefixed models and the Gateway SDK, with optional cleanup of LiteLLM infrastructure

Quick Start

Run /migrate-litellm to begin the migration workflow.

Frequently Asked Questions about Migrate LiteLLM to Merge Gateway

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate LiteLLM proxy to a managed gateway?▼

This workflow detects existing LiteLLM proxy deployments and guides replacement with the Merge Gateway SDK, covering environment variable updates and provider-prefixed model naming for a seamless migration.

Can I migrate the LiteLLM Python library in a Node project?▼

Yes, you can migrate the LiteLLM Python library in a Node project. The workflow provides specific migration plans for both Python and TypeScript/Node codebases, updating environment variables and replacing library calls with the Gateway SDK.

What is the process for replacing LiteLLM usage with a gateway SDK?▼

Replacing LiteLLM usage with a gateway SDK involves detecting current LiteLLM integration patterns, mapping them to a migration plan, and enforcing provider-prefixed models with required API key integration.

Does migrating from LiteLLM require changing model naming conventions?▼

Yes, migrating from LiteLLM requires changing model naming conventions. The migration process enforces provider-prefixed models to preserve behavior while transitioning your codebase to the new Gateway SDK.

How to handle LiteLLM infrastructure cleanup after gateway migration?▼

To handle LiteLLM infrastructure cleanup after gateway migration, the workflow flags existing LiteLLM infrastructure components for optional removal once your codebase successfully transitions to the Gateway SDK.