Skip to main content
Glama
AIE8-MCP-Server

AIE8-MCP-Server

AI Makerspace: MCP Session Repo for Session 13

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.

Related MCP server: Tavily Web Search MCP Server

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:

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

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

Installation

  1. Clone the repository:

    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!

🏗️ Activity #2:

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

You can find details here!

Available Tools

8 tools
generate_passwordC

Generate a random password with specified length and character options

Inputs: length, include_symbols.

get_card_by_idB

Get a specific Magic: The Gathering card by its Scryfall ID

Inputs: card_id (required).

get_random_cardB

Get a random Magic: The Gathering card from Scryfall

Inputs: no named parameters.

get_set_infoC

Get information about a Magic: The Gathering set by its code

Inputs: set_code (required).

roll_diceC

Roll the dice with the given notation

Inputs: notation (required), num_rolls.

search_card_by_nameC

Search for a Magic: The Gathering card by name using Scryfall API

Inputs: card_name (required), fuzzy.

search_cardsC

Search for Magic: The Gathering cards using Scryfall's search API

Inputs: query (required), page.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct resource/action targets, and the generic utilities are separate from the MTG tools. The only notable overlap is search_card_by_name versus search_cards, since a name query can be expressed as a Scryfall search, but the descriptions provide enough separation.

    Naming Consistency4/5

    All names use lowercase snake_case and mostly follow a verb_noun pattern. Minor deviations include web_search (noun_verb) and variation between search_card_by_name and search_cards, but the convention is still predictable.

    Tool Count5/5

    Eight tools is a well-scoped count for a mixed lookup/utility server. Each tool has a distinct purpose, and there is no obvious bloat or missing obvious companion tool.

    Completeness4/5

    The MTG surface covers core read operations: lookup by ID, lookup by name, general search, random card, and set info. Minor gaps include listing/searching sets broadly, card rulings, and set+number lookup, but these are workable around via search or web_search.

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server that enables web search capabilities using the Tavily API, allowing AI models to retrieve current information from the internet through natural language commands.
      3
      -
    • F
      license
      B
      quality
      D
      maintenance
      Enables web search capabilities through the Tavily API. Allows users to search the web for information using natural language queries via the MCP protocol.
      4
      1
      -
    • F
      license
      C
      quality
      D
      maintenance
      Enables web search capabilities through the Tavily API via the Model Context Protocol. Allows users to perform web searches and retrieve information from the internet through natural language queries.
      5
      -
    • F
      license
      C
      quality
      D
      maintenance
      Enables web search capabilities through the Tavily API. Allows users to search the web for information using natural language queries through the MCP protocol.
      3
      -