LlamaCloud RAG MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLAMA_CLOUD_API_KEY | Yes | Your LlamaCloud API key. | |
| LLAMA_CLOUD_PIPELINE_ID | No | Your LlamaCloud pipeline ID (or use LLAMA_CLOUD_PIPELINE_URL). | |
| LLAMA_CLOUD_PIPELINE_URL | No | Your LlamaCloud pipeline URL (alternative to PIPELINE_ID). | |
| LLAMA_CLOUD_ORGANIZATION_ID | Yes | Your LlamaCloud organization ID. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_ragB | Query the database documents in LlamaCloud and get comprehensive answers with sources |
| search_documentsA | Search for relevant documents in the knowledge base without generating an answer |
| get_index_infoA | Get detailed information about the LlamaCloud index and its current status |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_index_info retrieves index metadata, query_rag answers with sources, and search_documents finds documents without generating an answer. No overlap in functionality.
All tool names follow a consistent verb_noun snake_case pattern (get_index_info, query_rag, search_documents). The naming is predictable and intuitive.
With 3 tools, the surface is well-scoped for a RAG server: one for index status, one for querying, and one for searching. Neither too few nor too many.
The tools cover the core RAG workflow (index info, query, search). A minor gap is absence of document management or index modification, but that may be out of scope for a read-only RAG server.