LlamaCloud

LlamaCloud MCP Server

A MCP server connecting to multiple managed indexes on LlamaCloud

This is a TypeScript-based MCP server that creates multiple tools, each connected to a specific managed index on LlamaCloud. Each tool is defined through command-line arguments.

Features

Tools

Creates a separate tool for each index you define
Each tool provides a query parameter to search its specific index
Auto-generates tool names like get_information_index_name based on index names

Installation

To use with your MCP Client (e.g. Claude Desktop, Windsurf or Cursor), add the following config to your MCP client config:

1{
2  "mcpServers": {
3    "llamacloud": {
4      "command": "npx",
5      "args": [
6        "-y",
7        "@llamaindex/mcp-server-llamacloud",
8        "--index",
9        "10k-SEC-Tesla",
10        "--description",
11        "10k SEC documents from 2023 for Tesla",
12        "--index",
13        "10k-SEC-Apple",
14        "--description",
15        "10k SEC documents from 2023 for Apple"
16      ],
17      "env": {
18        "LLAMA_CLOUD_PROJECT_NAME": "<YOUR_PROJECT_NAME>",
19        "LLAMA_CLOUD_API_KEY": "<YOUR_API_KEY>"
20      }
21    }
22  }
23}

For Claude, the MCP config can be found at:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json

Tool Definition Format

In the args array of the MCP config, you can define multiple tools by providing pairs of --index and --description arguments. Each pair defines a new tool.

For example:

1--index "10k-SEC-Tesla" --description "10k SEC documents from 2023 for Tesla"

Adds a tool for the 10k-SEC-Tesla LlamaCloud index to the MCP server.

Development

Install dependencies:

1npm install

Build the server:

1npm run build

For development with auto-rebuild:

1npm run watch

To use the development version, replace in your MCP config npx @llamaindex/mcp-server-llamacloud with node ./build/index.js.

Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:

1npm run inspector

The Inspector will provide a URL to access debugging tools in your browser.