How to connect Search api MCP with VS Code

Trusted by teams at
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Search api logo
VS Code logo
divider

How to connect Search api MCP with VS Code

VS Code is the most popular code editor out there. With its recent AI makeover, it can do more than just help you write code. You can connect your applications to it and let LLMs automate many of the mundane tasks in your workflow.

In this guide, I will explain how to connect Search api with VS Code in the most secure and robust way possible via Composio.

Also integrate Search api with

Why use Composio?

Composio provides:

  • Access to 1,000+ managed apps from a single MCP endpoint. This makes it convenient for agents to run cross-app workflows.
  • Programmatic tool calling. Allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool response handling outside the LLM context. This minimizes context bloat from large tool responses.
  • Dynamic just-in-time access to thousands of tools across hundreds of apps. Composio loads the tools your agent needs, so LLMs are not overwhelmed by tools they do not need.

Integrate Search api MCP with VS Code

1. Install with one click

Click the button below to add Composio to VS Code. You will be prompted to authorize. This requires VS Code 1.99+ with GitHub Copilot.

+Install in VS Code

2. Or add manually

Open or create .vscode/mcp.json in your project root and add the following configuration:

bash
{
  "servers": {
    "composio": {
      "type": "http",
      "url": "https://connect.composio.dev/mcp"
    }
  }
}

3. Authorize

Click the install button to authorize VS Code to connect to Composio. VS Code will detect OAuth and prompt you to sign in.

VS Code MCP server install screen for Composio

A browser window will open to authorize.

Composio authorization browser window

4. Authenticate Search api and start working

Back in VS Code chat, ask the agent to connect to Search api or give it any Search api-related task.

For example, ask it to:

  • "Get the top Google search results for "climate change""
  • "Extract featured snippets for "best project management tools""
  • "Retrieve recent news headlines about AI ethics"

It will prompt you to authenticate and authorize access to Search api.

That is it. Composio tools are now available in VS Code, and your Search api account is ready to use.

Supported Tools & Triggers

Tools
Get Account InfoTool to retrieve account usage statistics including monthly usage, remaining credits, hourly limits, and subscription period information.
Get Cached Search by IDTool to retrieve cached search results by search ID in JSON format.
Get Cached Search HTML by IDTool to retrieve cached search results by search ID in HTML format.
Get LocationsTool to get available locations for geo-localized search queries.
SearchTool to perform unified search across 40+ search engines including Google, Bing, Yahoo, DuckDuckGo, YouTube, Amazon, and more.

Way Forward

Now that Search api is connected, extend your setup by connecting the other apps you already use every day, so your agent can run true cross-app workflows end to end.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.
  • Connect HubSpot or Salesforce to log customer context, update records, and draft follow-ups.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single MCP endpoint, your agent can coordinate multiple tools safely and reliably in one conversation.

How to build Search api MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Search api MCP with ChatGPT

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Search api MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Search api MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Search api MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Search api MCP with Claude Cowork

Codex logo

Codex

Use Search api MCP with Codex

Cursor logo

Cursor

Use Search api MCP with Cursor

OpenClaw logo

OpenClaw

Use Search api MCP with OpenClaw

Hermes logo

Hermes

Use Search api MCP with Hermes

CLI logo

CLI

Use Search api MCP with CLI

Google ADK logo

Google ADK

Use Search api MCP with Google ADK

LangChain logo

LangChain

Use Search api MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Search api MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Search api MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Search api MCP with LlamaIndex

CrewAI logo

CrewAI

Use Search api MCP with CrewAI

OpenCode logo

OpenCode

Use Search api MCP with OpenCode

FAQ

What are the differences in Tool Router MCP and Search api MCP?

With a standalone Search api MCP server, the agents and LLMs can only access a fixed set of Search api tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Search api and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with VS Code?

Yes, you can. VS Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Search api tools.

Can I manage the permissions and scopes for Search api while using Tool Router?

Yes, absolutely. You can configure which Search api scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Search api data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗