MCP.so
Sign In

MCP Haystack Demo

@oryx1729

Basic information

Category

Media & Design

Transports

stdio

Author

oryx1729

About MCP Haystack Demo

Demo for using MCP Servers in a Haystack Pipeline

MCP Haystack Demo config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-haystack-google-maps": {
      "command": "docker",
      "args": [
        "run",
        "-it",
        "--rm",
        "-p",
        "8000:8000",
        "-e",
        "GOOGLE_MAPS_API_KEY=$GOOGLE_MAPS_API_KEY",
        "supercorp/supergateway",
        "\\"
      ]
    }
  }
}

MCP Haystack Demo tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Haystack Demo?

MCP Haystack Demo is a Haystack Toolset that connects to remote MCP (Model Context Protocol) servers, with a focus on Google Maps API integration. It dynamically discovers and loads available tools from the server for use in Haystack pipelines.

How to use MCP Haystack Demo?

Install dependencies with uv, then start a Google Maps MCP server using Docker and connect via the MCPServer class. See the provided demo notebook for a complete example. Use ToolInvoker or ChatGenerator with the loaded toolset.

Key features of MCP Haystack Demo

  • Connect to remote MCP servers using SSE (Server-Sent Events)
  • Dynamically discover and load available tools from the MCP server
  • Seamless integration with Haystack pipelines

Use cases of MCP Haystack Demo

  • Integrating Google Maps API tools into a Haystack pipeline
  • Building a location-aware AI assistant using Haystack components
  • Demonstrating MCP server connectivity within the Haystack framework

Frequently asked questions

1

What transport does the MCP server use?

The MCP server uses SSE (Server-Sent Events) as the transport protocol.

2

How do I start the Google Maps MCP server?

Run `docker run -it --rm -p 8000:8000 -e GOOGLE_MAPS_API_KEY=$GOOGLE_MAPS_API_KEY supercorp/supergateway --stdio "npx -y @modelcontextprotocol/server-google-maps" --port 8000`.

3

What runtime dependencies are required?

The project relies on `uv` for installation and requires Haystack libraries that support the `MCPServer` and `SSEServerInfo` classes.

4

Is this a production-ready server?

No, this is a demo – it demonstrates connecting Haystack to MCP servers, specifically Google Maps. It should not be used in production without further hardening.

5

Where does the data (e.g., API keys) live?

The Google Maps API key is passed as an environment variable (`GOOGLE_MAPS_API_KEY`) to the Docker container. No data is stored locally by the server.

Comments

More Media & Design MCP servers