Migrate from your agents
Cursor
What runelay migrate brings from Cursor, and why its accounts ask for login again.
What comes along
| Read from | |
|---|---|
| MCP servers | ~/.cursor/mcp.json |
| Skills | ~/.cursor/skills and ~/.cursor/skills-cursor |
Servers that authenticate with headers arrive connected, because the headers are in mcp.json.
What stays behind
- Logins. Cursor stores its OAuth tokens encrypted, so runelay cannot read them. Every OAuth account from Cursor arrives as a connection that asks for login, and the CLI opens
/connectors/reconnectto go through them. The CLI prints this as a note on every run. - Memories and instructions. runelay does not read memories or rules from Cursor.
- Servers with a
command(stdio) stay in Cursor.
Wiring runelay in
If ~/.cursor/mcp.json exists, runelay adds itself to mcpServers:
{
"mcpServers": {
"runelay": { "url": "<url>/v1/mcp", "headers": { "Authorization": "Bearer rnl_…" } }
}
}With --replace, the migrated servers are removed from mcp.json. See Connect agents.