Skip to content

MCP Server Catalog

Server Catalog Overview

We provide a set of MCP servers that are ready for use both locally and in the AI Refinery platform. We have selected a set of servers with two criteria in mind:

  • Servers that have different setup requirements, to provide the user some exposure to the possible ways that MCP servers may need to be configured.
  • Servers that support a wide range of tools, to showcase the remarkable capabilities that MCP servers provide to LLMs.

These servers include:

1) arXiv: An interface for the online paper repository, allowing for programmatically retrieving papers, downloading them locally, and reading them.

2) Azure: An interface to key Azure services like Azure Storage, Cosmos DB, and more.

3) DuckDuckGo: A server providing web search capabilities using DuckDuckGo.

4) filesystem: A server providing filesystem operations that are available through the command line.

5) Gmail: An interface with a Gmail account allowing for receiving and sending emails by specifying subject, content, and recipients.

6) Google Calendar: A server providing access to a Google Calendar, allowing you to read, create, update and search for calendar events.

7) python interpreter: A sandbox to run python code in an isolated environment.

8) timezone: A time and timezone management server that allows for time queries, time conversions, etc.

Please refer to the respective repositories for guidance on installing the required components for each server.

MCP Server Setup Summary

The table below summarizes each MCP server along with its default communication port and any additional authentication or setup requirements. Since the MCP Client Agent requires an SSE port for communication, the table also indicates which servers require additional SSE transportation.

MCP Server Default Port Requires SSE Transportation Additional Setup
arXiv STDIO Yes None
Azure STDIO & SSE No az login
DuckDuckGo STDIO Yes None
filesystem STDIO Yes None
Gmail STDIO Yes Google OAuth
Google Calendar STDIO Yes Google OAuth
python Interpreter STDIO & SSE Yes None
timezone STDIO Yes None

The STDIO and SSE ports are common communication methods used by MCP servers, as detailed in MCP Exposure Methods:. For servers that require additional SSE transportation, the mcp-proxy can be used, as described in MCP Exposure Compatibility:. A template of using mcp-proxy is listed below:

mcp-proxy --sse-port=PORT  --command_to_start_stdio --other_required_arguments
  • PORT: The desired SSE port, accessible via http://localhost:PORT.

  • command_to_start_stdio: The command used to start the MCP server in STDIO mode, such as:

    • npm run start <project_name>
    • npx <online_project_name>
    • uv <project_name>
    • uvx <online_project_name>