> ## Documentation Index
> Fetch the complete documentation index at: https://magica.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate to Spiral

> The Magica API and MCP server shut down on December 1, 2026. Move your integration to Spiral with one prompt.

> [!WARNING]
>
> The Magica REST API and MCP server shut down on **December 1, 2026**. New API
> keys and new MCP connections are paused. Your existing keys and connections
> keep working until then.

Spiral ([spiral.ai](https://spiral.ai)) runs every model and tool you use
through the Magica API, plus many more, with one API key, a hosted MCP server
at `https://api.spiral.ai/mcp` and a command-line tool.

## Move with your agent

**1. Send the prompt to your agent**

Copy this prompt into the coding agent that works on your integration
(Claude Code, Cursor, Codex or another).

```text Migration prompt wrap theme={null}
Migrate this project from the Magica API and MCP server to Spiral. The Magica API and MCP server shut down on December 1, 2026.

1. Read https://spiral.ai/llms.txt and https://spiral.ai/SKILL.md to learn how Spiral works.
2. Find every place that uses Magica: the base URL https://inference.magica.com/v1, the MCP server https://inference.magica.com/v1/mcp, gx_ API keys, MAGICA_* environment variables, and MCP client configs (Claude, Cursor, Codex, ChatGPT, VS Code and others).
3. Help me sign in to Spiral and create an API key at https://spiral.ai/start, or connect the Spiral MCP server at https://api.spiral.ai/mcp with browser sign-in. Store the new key where the Magica key was stored. Never print or commit it.
4. For each Magica model or tool in use, find the Spiral equivalent with Spiral's catalog search, check its input schema and price, and update the calls. Spiral has every Magica model and tool, plus many more.
5. Replace the Magica MCP server with Spiral's in every MCP config.
6. Run one low-cost test call through Spiral, then show me what changed and anything you could not migrate.

Remove the Magica key only after I confirm everything works.
```

**2. Your agent will handle the migration setup**

It finds your Magica calls and MCP configs, helps you sign in to Spiral,
swaps each model for its Spiral equivalent, and runs a test call. Remove
your Magica key once you have checked the result.

The same prompt is in Magica under **Settings → API Keys**.

## Credits

Magica credits don't carry over to Spiral. For a one-time credit transfer,
open a support ticket or email
[support@magica.com](mailto:support@magica.com) before December 1, 2026.

## What changes for callers until the shutdown

* New API keys and new MCP OAuth sign-ins (Claude, ChatGPT, Codex, the Magica
  CLI and others) are refused.
* Every REST API and MCP response carries `Deprecation`, `Sunset` and `Link`
  headers that name the shutdown date and this guide.
* MCP clients receive the shutdown notice in the server instructions and at
  the end of every tool result, so the agent using them can tell you.

Magica's Agent, Projects and Tools in the app are not affected.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.