Skip to main content
The hosted MCP server lets compatible agents use LangSearch without a custom HTTP integration.

Choose your client

Replace YOUR_LANGSEARCH_API_KEY before connecting. Merge the configuration into the existing file rather than replacing other servers. For Codex, keep the key available in the environment where you launch the client.
Terminal
Terminal
.cursor/mcp.json
MCP: Open User Configuration, or workspace .vscode/mcp.json
.gemini/settings.json
opencode.json
~/.codeium/mcp_config.json
MCP Servers → Configure MCP Servers
.roo/mcp.json
Zed settings.json

Verify the connection

  1. Save the configuration or run the command in your installed client.
  2. Start or reload the LangSearch MCP connection and complete any client trust prompt.
  3. Check that the client lists the server’s tools.
  4. Ask your agent to search the web for a specific topic and include source links.

Troubleshooting

  • Unauthorized: check the API key and the Authorization: Bearer ... header.
  • No tools listed: confirm the endpoint ends in /mcp, then restart the connection and inspect the client log.
  • Rate limited: check account usage. Creating another connection does not create another allowance.
Client settings differ: VS Code uses servers, Cursor uses mcpServers, and other clients may use different fields. Keep the format for your selected client. Prefer installation instructions for your agent? Use the Agent Skill.