---
title: Changelog: June 2026 | Developer Documentation
description: LlamaParse changes shipped in June 2026.
---

[All recent changes](/llamaparse/changelog/index.md) · [RSS](/llamaparse/changelog/rss.xml)

## [Per-product MCP endpoints](/llamaparse/changelog/2026-06/#2026-06-30-mcp-per-product-endpoints/index.md)

[Jun 30, 2026](/llamaparse/changelog/2026-06/#2026-06-30-mcp-per-product-endpoints/index.md)

platform api

The LlamaParse MCP server now covers Extract and Index alongside Parse, Classify, and Split, with a scoped endpoint per product. This lets an agent get access to just the part of the platform it needs, and run several in parallel. See [MCP](/llamaparse/for-agents/mcp/index.md).

## [Usage tags for billing attribution](/llamaparse/changelog/2026-06/#2026-06-29-usage-tags/index.md)

[Jun 29, 2026](/llamaparse/changelog/2026-06/#2026-06-29-usage-tags/index.md)

platform api

Enterprise organizations can now tag parse and extract requests with custom labels, carried through to usage metrics. This lets billing data be sliced by team, environment, or customer. See [Usage tags](/llamaparse/general/usage_tags/index.md).

## [Label parse jobs with your own metadata](/llamaparse/changelog/2026-06/#2026-06-29-parse-user-metadata/index.md)

[Jun 29, 2026](/llamaparse/changelog/2026-06/#2026-06-29-parse-user-metadata/index.md)

parse apisdk

Parse jobs now accept a `user_metadata` object at creation, for whatever context your application needs to keep with the job. It’s returned unchanged on every get and list response, and can’t be changed after the job is created. See [Configuring Parse](/llamaparse/parse/guides/configuring-parse/index.md).

## [Go, Java, and CLI SDKs](/llamaparse/changelog/2026-06/#2026-06-26-go-java-cli-sdks/index.md)

[Jun 26, 2026](/llamaparse/changelog/2026-06/#2026-06-26-go-java-cli-sdks/index.md)

platform sdk

LlamaParse now ships official SDKs for Go and Java, plus a command-line client, alongside the existing Python and TypeScript SDKs. All are generated from the same API definition, so they share the same surface and stay in step with new releases. See the [API reference](/reference/index.md).

## [Parse jobs can use a saved configuration](/llamaparse/changelog/2026-06/#2026-06-17-parse-saved-configurations/index.md)

[Jun 17, 2026](/llamaparse/changelog/2026-06/#2026-06-17-parse-saved-configurations/index.md)

parse api

The parse API now accepts a `configuration_id`, so a saved configuration can be applied to a job directly instead of repeating every option in the request. The other APIs already supported this; Parse now matches them. See the [parse request reference](/reference/resources/parsing/methods/create/index.md).

[← July 2026](/llamaparse/changelog/2026-07/index.md)