Cursor
http://127.0.0.1:11434/v1 with the key prismand Cursor's requests flow through your Prism providers. Cursor is not auto-configured — this is a manual, two-field change.Last updated Reviewed against Prism v0.3.26
Setup
Open Cursor's model settings
Settings → Models.Enable and set the base URL override
http://127.0.0.1:11434/v1. The /v1 suffix is required.Set the API key
prism. This is Prism's fixed local token — it is not a secret and never leaves your machine.Add your models
Base URL: http://127.0.0.1:11434/v1 API Key: prism Model: <your Prism model route key>
Which endpoints Cursor uses
| Cursor feature | Prism endpoint |
|---|---|
| Standard chat and agent requests | /v1/chat/completions |
| Completions with a Responses-style client | /v1/responses |
| Model discovery, where Cursor asks for it | /v1/models |
Prism accepts both Authorization: Bearer prism and x-api-key: prism, so whichever header Cursor sends works.
Aliasing Cursor's model names
Cursor sends whatever model name you selected. If that name is not in your Prism catalog, Prism serves your default model instead. To keep a familiar name in Cursor's picker while running a different upstream model, add an alias:
{
"aliases": {
"gpt-4o": "glm-5.1:cloud",
"claude-3-5-sonnet-20241022": "glm-5.1:cloud"
}
}See Model Remapping for the full alias rules.
MCP servers in Cursor
Cursor manages its own MCP servers, and Prism does not write that config. If you want Cursor to reach the MCP servers you enabled in Prism, add the gateway to Cursor's MCP config as a remote server pointing at http://127.0.0.1:11434/mcp with the header Authorization: Bearer prism. See MCP Gateway for the endpoint shape and the per-agent allowlist variant.
Verify it is working
Send a prompt in Cursor
Check the Stats tab
/v1.