Skip to main content
Glama
neeraj-somani

Tavily Web Search MCP Server

README.md
<p align = "center" draggable=”false” ><img src="https://github.com/AI-Maker-Space/LLM-Dev-101/assets/37101144/d1343317-fa2f-41e1-8af1-1dbb18399719" 
     width="200px"
     height="auto"/>
</p>

## <h1 align="center" id="heading">AI Makerspace: MCP Session Repo for Session 13</h1>

This project is a demonstration of the MCP (Model Context Protocol) server, which utilizes the Tavily API for web search capabilities. The server is designed to run in a standard input/output (stdio) transport mode.

## Project Overview

The MCP server is set up to handle web search queries using the Tavily API. It is built with the following key components:

- **TavilyClient**: A client for interacting with the Tavily API to perform web searches.

## Prerequisites

- Python 3.13 or higher
- A valid Tavily API key

## ⚠️NOTE FOR WINDOWS:⚠️

You'll need to install this on the *Windows* side of your OS. 

This will require getting two CLI tool for Powershell, which you can do as follows:

- `winget install astral-sh.uv`
- `winget install --id Git.Git -e --source winget`

After you have those CLI tools, please open Cursor *into Windows*.

Then, you can clone the repository using the following command in your Cursor terminal:

```bash
git clone https://AI-Maker-Space/AIE8-MCP-Session.git
```

After that, you can follow from Step 2. below!

## Installation

1. **Clone the repository**:
   ```bash
   git clone <repository-url>
   cd <repository-directory>
   ```

2. **Configure environment variables**:
Copy the `.env.sample` to `.env` and add your Tavily API key:
   ```
   TAVILY_API_KEY=your_api_key_here
   ```

3. 🏗️ **Add a new tool to your MCP Server** 🏗️

Create a new tool in the `server.py` file, that's it!

## Running the MCP Server

To start the MCP server, you will need to add the following to your MCP Profile in Cursor:

> NOTE: To get to your MCP config. you can use the Command Pallete (CMD/CTRL+SHIFT+P) and select "View: Open MCP Settings" and replace the contents with the JSON blob below.

```
{
    "mcpServers":  {
        "mcp-server": {
            "command" : "uv",
            "args" : ["--directory", "/PATH/TO/REPOSITORY", "run", "server.py"]
        }
    }
}
```

The server will start and listen for commands via standard input/output.

## Usage

The server provides a `web_search` tool that can be used to search the web for information about a given query. This is achieved by calling the `web_search` function with the desired query string.

## Activities: 

There are a few activities for this assignment!

### 🏗️ Activity #1: 

Choose an API that you enjoy using - and build an MCP server for it!

Answer: I am implementing polygon API tool in this MCP server.

### 🏗️ Activity #2: 

Build a simple LangGraph application that interacts with your MCP Server.

You can find details [here](https://github.com/langchain-ai/langchain-mcp-adapters)!

Answer: langgraph_agent.py file has been implemented for this.

TDQS

C2.9/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a completely distinct purpose with no overlap: get_stock_ohlc retrieves financial data, roll_dice performs a random number generation game, and web_search conducts internet queries. The domains are so different that an agent would never confuse them.

Naming Consistency2/5

The naming is inconsistent with mixed conventions: get_stock_ohlc uses snake_case with a verb_noun pattern, roll_dice uses snake_case but with a verb-only style, and web_search uses snake_case with a noun_verb pattern. There is no predictable naming scheme across the set.

Tool Count2/5

With only 3 tools, the server feels too thin for its apparent scope as a 'Tavily Web Search MCP Server'—web_search aligns with this, but get_stock_ohlc and roll_dice are unrelated utilities that don't fit cohesively. The count is low and the tools lack a unified domain focus.

Completeness2/5

For a web search server, the surface is severely incomplete: web_search covers basic queries, but there are no tools for advanced search features (e.g., filtering, pagination, or result analysis). The inclusion of unrelated tools like get_stock_ohlc and roll_dice creates gaps in the core domain without adding meaningful coverage.

Maintenance

ActivityInactive
ResponsivenessNo issues