How to Use the Bing Search MCP in CrewAI

Q: Can multiple CrewAI agents share Bing Search context?

Yes, through CrewAI's shared memory. When one agent runs searchentities, the resolved Knowledge Graph mapping is stored in the crew's memory, allowing other agents to reference those facts later.

Q: Can I limit CrewAI agents to specific domains?

Yes, by exposing only the customsearch tool to your crew. This forces the agents to search within your pre-configured whitelist domains instead of wandering off into the open web.

Equip your CrewAI agent teams with real-time Bing Search capabilities.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Bing Search MCP to CrewAI

Create your Vinkius account to connect Bing Search to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Bing Search with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Coordinate research tasks using this MCP Server

The `search_news` tool gathers syndicated global PR articles grouped by timestamp for your CrewAI researcher agents. A single agent gets overwhelmed trying to research, filter, and write. This division of labor prevents context window bloat. The researcher agent filters the raw news feed, passing only the most relevant timestamped clusters to the next agent in the hierarchy.

Extract structured local market intelligence with CrewAI

The `search_local` tool extracts physical store details and business listings over standard web nodes for your CrewAI team. Standard web scrapes often miss physical store details. The agent uses CrewAI's shared memory to compare these listings against your target criteria. It can then flag missing phone numbers or incorrect addresses before passing the list to your outreach agent using this MCP Server.

Track viral trends autonomously using CrewAI teams

The `trending_news` tool discovers macroscopic viral topics natively without relying on static keywords in CrewAI. Monitoring the web for breaking stories requires continuous, keyword-free tracking. Once a trend is identified, the agent passes the topic to a content creator agent. That agent then runs `search_web` to gather background context and draft a response, all without human intervention.

Setup guide

Set up Bing Search MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Bing Search tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Bing Search Analyst",
    goal="Access and analyze Bing Search data via MCP.",
    backstory="Expert analyst with direct Bing Search access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Bing Search transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Bing Search Analyst",
        goal="Access and analyze Bing Search data via MCP.",
        backstory="Expert analyst with direct Bing Search access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Bing Search transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Bing Search. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Bing Search now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Bing Search MCP in CrewAI

You configure this when defining your agents. Pass the MCP Server URL in the agent's parameters, allowing only your researcher agent to run `search_web` while keeping your writer agent focused on drafting.

Yes, through CrewAI's shared memory. When one agent runs `search_entities`, the resolved Knowledge Graph mapping is stored in the crew's memory, allowing other agents to reference those facts later.

CrewAI's execution loop handles tool failures gracefully. If `search_news` returns an error, the agent will attempt to re-run the query or log the failure for the moderator agent to handle.

Yes, by exposing only the `custom_search` tool to your crew. This forces the agents to search within your pre-configured whitelist domains instead of wandering off into the open web.

Absolutely. Every query sent by your CrewAI agents is processed in a secure V8 isolate sandbox. No search history or extracted web data is ever stored on Vinkius servers, keeping your competitive research private.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript