cursor-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CURSOR_API_KEY | No | Cursor API key (e.g. crsr_xxxx) used for login via automatic token exchange and refresh. Can alternatively be supplied by writing the key to ~/.cursor-search-mcp/key, or by using the browser-based OAuth (PKCE device flow) login instead. | |
| CURSOR_API_ENDPOINT | No | API base URL. | https://api2.cursor.sh |
| CURSOR_SEARCH_MODEL | No | Model used for search synthesis. | gpt-5.3-codex-low-fast |
| CURSOR_CLIENT_VERSION | No | Client version header. | cli-2026.10.01-e373342 |
| CURSOR_SEARCH_STATE_DIR | No | State directory (token is cached with 0600 permissions at ~/.cursor-search-mcp/auth.json). | ~/.cursor-search-mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cursor_loginA | Report Cursor login/token status. Credentials come from CURSOR_API_KEY, ~/.cursor-search-mcp/key, or a cached OAuth token. |
| cursor_oauth_loginA | Start OAuth browser login (no API key needed). Returns login_url for the user to open in a browser; then call cursor_oauth_wait with the returned uuid to complete the token exchange. |
| cursor_oauth_waitA | Wait for the user to finish OAuth browser authorization and exchange the token. Call after cursor_oauth_login's URL was opened. |
| cursor_web_searchA | Web search (Cursor server-side, pure protocol). Returns a synthesized answer with source links. Good for latest docs, releases, facts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The three auth-related tools have distinct roles: status check, OAuth initiation, and OAuth completion wait. An agent could briefly hesitate between cursor_login and cursor_oauth_login when unauthenticated, but the descriptions clarify the intended sequence.
All tools use a consistent cursor_ prefix and snake_case, with auth tools following a clear cursor_oauth_* subpattern. cursor_login and cursor_web_search are slightly less uniform in verb style but remain readable and predictable.
Four tools is reasonable for a narrow web-search server with an unavoidable OAuth lifecycle. The set is slightly auth-heavy (three auth tools to one search tool), but that reflects a legitimate setup flow rather than unnecessary bloat.
The auth lifecycle is well covered with status, initiation, and completion tools, and web search is present. Minor gaps like logout/token clearing or richer search options exist, but core workflows are covered.