leookun/cursor-byok

What it solves

Cursor's built-in model options are tied to a fixed set of providers and billing plans, leaving you with little choice. cursor-byok removes that limit by letting you bring your own API keys, endpoints, and model IDs. It gives you back control over which models you use, so you can tap into the credits and providers you already have instead of Cursor's default channels.

How it works

cursor-byok runs as a local service on your machine. Cursor sends agent requests and tool results to this service, which then adapts the protocol and forwards them to the model API you've configured. It handles protocol translation (OpenAI- and Anthropic-compatible), request forwarding, tool-call coordination, and conversation state — all on your computer. Your API keys and settings stay stored locally, while the actual model requests go out to your chosen provider.

Who it's for

This is built for developers who use Cursor but want to use their own model subscriptions, credits, or self-hosted services. If you're tired of being restricted to the models Cursor offers and want the freedom to plug in any compatible API, this project is for you.

Highlights

• Bring your own model channels: configure your own endpoint, credentials, and model IDs.
• Support for both OpenAI- and Anthropic-compatible APIs, or a custom endpoint.
• Model management: add, duplicate, edit, reorder, and batch-test multiple configurations.
• Connection benchmarks: measure time-to-first-token, generation speed, and inspect raw provider responses.
• Keeps agent workflows intact: tool calling, Skills, MCP, and multi-turn conversations all still work.
• Session metrics: track token usage, cache hit rate, conversation turns, and estimated value.
• Cross-platform: runs on macOS, Windows, and Linux.