Claude LlamaParse connectorWhat Claude can do in your LlamaParse account.
The Claude LlamaParse connector exposes 22 tools. 15 read and process your documents, 7 upload files or build something in your account, 0 are undocumented. Below: what Claude can pull out of a PDF, what it creates, the region trap, and who controls it.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can use LlamaParse
LlamaParse is LlamaIndex's document platform: it parses files into clean text, extracts structured fields, classifies and splits documents, and keeps searchable indexes. Connected to Claude, it does that work when you ask in plain words. Drop a link to a long scanned report and Claude has it parsed, then answer from the result instead of a truncated copy.
Read a hard document properly. parseFile turns a file into markdown or plain text, and estimateFileComplexity tells Claude which pages of a PDF need the heavier parser and which the free parseWithLiteParse can handle.
Pull out the fields you need. generateExtractionConfig builds an extraction setup from a description and a sample file, then extractFile applies it, LlamaIndex notes that prompt-only extraction leaves the output schema underspecified and that an agent may only get a truncated version of a large document.
Keep a searchable library. Claude can gather files into a directory, index it with createIndex, then search it with retrieveFromIndex or grepFileFromIndex.
What Claude will not do here: an index never refreshes itself, so new files stay invisible until syncIndex runs. A few tools LlamaIndex documents (schema templates, project API keys) are not on the directory sheet. And nothing happens on its own: Claude calls these tools only while answering you. Our Integrations hub lists the other connectors we cover.
Five words before you connect
The vocabulary around this connector, without detours.
- Connector
- A link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named capability the connector gives Claude. Claude picks the ones it needs during an answer; the directory lists them by name.
- Authorization
- The service's own sign-in screen, where you grant the access Claude will use. Given once per person, and you can revoke it.
- Approval
- The confirmation Claude waits for before it changes something in an account, shown in the conversation at that moment.
- MCP
- The shared standard connectors are built on, which lets an assistant like Claude talk to an outside service.
Connect LlamaParse to Claude in three steps
- 01
Find LlamaParse
Open Claude's settings, go to Customize then Connectors, and search for LlamaParse. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector before members can each sign in.
- 02
Sign in to LlamaCloud
Click Connect on its row, then log in with your LlamaCloud account in the window it opens. If the connection breaks, Disconnect and connect again. LlamaIndex notes that one connection covers web, desktop and mobile.
- 03
Read the authorization screen
Check the authorization screen before you accept it. It belongs to LlamaIndex, not to Claude, and it sets what the access covers. Approval before each action stays Claude's default afterwards.
The 22 tools, split by what they do
LlamaParse gives Claude 22 tools: 15 that read your account, 7 that change something in it.
Every tool on the sheet is described by LlamaIndex. Names stay exactly as Claude shows them.
- 15 read
- 7 write
What Claude reads and processes (15)
15 toolsTools that read files, run parsing or extraction on them, or search what is already indexed.
classifyFile
Tells you which of your categories a document belongs to, using LlamaParse Classify. The categories travel with each call, so no saved configuration is needed first.
estimateFileComplexity
Scores a PDF page by page and says, for each page, which Parse tier it needs or whether the lighter parser is enough.
extractFile
Runs structured extraction on a file against an extraction configuration ID, returning the fields the configuration defines.
findFilesInIndex
Locates the files within an index that are relevant to a request, so Claude knows which documents to open next. The index has to be ready: while it is still building, it answers like an index with no match.
getIndexStatus
Reports whether an index has finished building. A query on an index that is not ready looks exactly like a query with no match, so this check matters.
getUserProjects
Lists the projects your LlamaCloud account can reach, so Claude can pick one by name and pass its ID to the other tools.
grepFileFromIndex
Searches indexed files for a pattern, the way grep scans text, and returns the matching passages. It works over the files of an index that has already been built, which listIndexes helps you find.
listDirectories
Lists the directories in a project, page by page. A directory is the folder of source documents an index is built over. Claude gets names and IDs to pass to the other tools.
listDirectory
Shows the files inside one directory, one page at a time, so Claude can confirm what an index would cover, or spot a file that is missing from the set.
listIndexes
Discovers the indexes you are able to query, the starting point before any search or retrieval. Claude needs an index's identity before it can look inside it.
parseFile
Runs a full Parse job over a file and returns clean markdown or plain text.
parseWithLiteParse
Uses LiteParse, a fast parser that costs no Parse credits, on a PDF. It works on PDFs only and does best on text-heavy pages with simple layouts.
readFileFromIndex
Reads the whole content of one file stored in an index, so Claude can work on the full text rather than fragments.
retrieveFromIndex
Performs hybrid retrieval over an index, mixing keyword-style and meaning-based matching, and returns the most relevant passages. To read one of those documents in full afterwards, readFileFromIndex takes over.
splitFile
Segments a document into logical sections with LlamaParse Split. Like classification, it takes its categories inline with the call, except on a server pinned to one Split configuration.
What Claude adds to your account (7)
7 toolsTools that upload files or set up directories, indexes and extraction configurations. No source describes their confirmation, so the general rule applies.
addFilesToDirectory
Approval: see the ruleAdds files you already uploaded to a directory, using their file IDs. Files go in one at a time, and the response says which succeeded so only failures are retried.
createDirectory
Approval: see the ruleMakes a new directory in your project, the folder that will hold the source documents of a future index.
createIndex
Approval: see the ruleIndexes a directory so its files become searchable. Indexing runs in the background, and the index cannot be queried until it reports ready.
generateExtractionConfig
Approval: see the ruleGenerates an extraction schema and rules from your description of the data you want, using a sample file, and returns the ID of the resulting configuration.
getUploadUrl
Approval: see the ruleReturns a temporary, authenticated address where a local file can be posted into the platform, the route for files that are not online. The source only describes the address it returns: the deposit itself happens when your client posts the file to it.
syncIndex
Approval: see the ruleRe-indexes a directory to pick up files added or changed since the last run. An index never refreshes by itself, so this is how it sees new documents.
uploadFileByUrl
Approval: see the ruleTakes a public file URL, fetches the file and stores it on the platform, ready for parsing or indexing.
What Claude checks with you first
By default, Claude stops and asks for confirmation before each action it takes on an account in someone's place.
No source describes a confirmation for any of the seven LlamaParse tools that upload files or create directories, indexes and extraction configurations, so the default rule applies to all of them. On Team and Enterprise, workspace owners decide whether members may let some actions through without a prompt each time, and they can restrict a connector for the whole organization. LlamaIndex adds that both ways of connecting resolve to the same account and the same permissions: Claude works with your LlamaCloud rights and nothing more.
Which plans this works on
No source publishes plan availability connector by connector: 0 of the 819 directory sheets shows it.
The published rule is general. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before members connect. LlamaIndex's documentation does not tie this connector to any Claude plan. For the current state on your account, the connector's sheet in the official directory is the place to check.
Where this connector stops
A connector is not an automation. Claude calls LlamaParse while it answers you; a new file in a folder does not get parsed or indexed by itself.
Only LlamaIndex documents this connector; no Claude help page covers it. Its documentation also describes schema templates, an extraction setup built from a schema and project API keys, none of which is on the directory sheet, so this page does not count them. The partner badge is not a security audit, and Anthropic says on every sheet that it does not pick the tools a publisher exposes or vouch for them.
Need help connecting LlamaParse to Claude?
A person reads every message.
