Web search inside Cursor
Point Cursor at the hosted Search1API MCP server and the agent can search the web, read pages, and check what is trending while it works on your code, without leaving the editor or writing an integration.
What the agent gets
Five tools, no code
Search, news, page reading, sitemap discovery, and trending topics arrive as tools the model can call on its own.
Docs it has not memorized
Cursor can look up the current API surface of a dependency instead of guessing from its training data.
Full page text when snippets are thin
A search can return the top results as complete page content in the same request, which is usually what a code question needs.
Add it to Cursor
The Directory listing installs it for you. If you prefer to edit configuration by hand, this is the block Cursor expects.
mcp.json β json
Worth knowing
Search1API is published in the Cursor Directory, which hands the install off to the desktop app. Review the configuration Cursor shows you before approving it.
The server also supports OAuth 2.1, so a client that discovers the authorization flow does not need a key in the file.
Tool calls bill as ordinary API calls: 1 credit per search, plus 1 for each page successfully retrieved.
What people do with it
Check a breaking change in a dependency before upgrading it.
Read the linked issue or RFC without switching to a browser.
Find a working example on GitHub for an unfamiliar library.
FAQ
Do I need to install anything locally?
No. The MCP server is hosted, so Cursor connects over HTTP. There is no local process to start or keep running.
Where does the configuration go?
Cursor reads MCP servers from its mcp.json. The one-click install from the Directory writes it for you; otherwise add the block above to the file yourself.
How much does it cost?
New accounts get 100 credits free with no card. A search or news request is 1 credit, and each page successfully retrieved adds 1 more.