Developer toolchain Overview

The Palantir platform comes with a set of developer tools that enable you to build on top of the Ontology and unlock value with new workflows, applications, and functionality. With Palantir's developer toolchain, you can access the full power of the Ontology directly from your development environment.

In addition to the data connection and application building tools described elsewhere, the Palantir developer toolchain provides:

• Core APIs and SDKs that open up the Ontology to your applications.
• Development environments and developer-centric functionality to accelerate your workflows.
• Palantir MCP to enable AI IDEs and AI agents to use Palantir context and take action throughout Foundry.
• Ontology MCP to expose ontology resources as MCP tools for external AI agents.
• Compute modules to containerize your code and scale your deployments.

Central to Palantir's developer offerings are the APIs and SDKs that open up the platform and allow you to build applications that integrate directly with the Palantir platform and your Ontology data.

The Ontology SDK (OSDK) enables developers to generate SDKs from their ontologies in Python, Java, and TypeScript. OSDK lets you access object types, apply actions to update data in the Ontology, call functions, and run AIP Logic functions for AIP-enabled enrollments. The in-platform Developer Console includes Ontology-specific documentation for the entities chosen for your application. Applications use the OAuth flow as a public or confidential client to access the data.

Palantir's APIs support users building on the Palantir platform by enabling programmatic management of platform access and the data backing your Ontology. API references are also available in-platform via the Developer Console.

Available Palantir APIs include:

• Datasets — Read, write, and manage datasets, including branches, transactions, files, and views.
• Filesystem — Manage spaces, projects, folders, and resource roles.
• Administration — Manage users, groups, organizations, hosts, and markings.
• Orchestration — Trigger builds, inspect jobs, and configure schedules.
• Connectivity — Manage connections, virtual tables, and file or table imports from external sources.
• SQL Queries — Execute SQL against datasets.
• Media Sets [Beta] — Upload, retrieve, and manage media sets and their items.

See the full API documentation for the complete list of endpoints, including models, audit logs, data health checks, streams, checkpoints, and Notepad.

Palantir's platform SDKs are publicly available for Python ↗ and TypeScript ↗, and are expanded as new APIs become available. These SDKs are usable alongside Ontology SDKs with the same Palantir platform clients.

In addition to development tools focused on data connection such as Pipeline Builder and Code Repositories, Code Workspaces allows you to use familiar IDEs like VS Code while building on top of the Palantir platform. VS Code workspaces are integrated with Developer Console, allowing you to rapidly build React applications. You can create a VS Code workspace from the in-platform Developer Console.

Palantir's developer-focused functionality aims to accelerate the process of building on the platform. Features like Global Branching help create a safe, streamlined environment for development of end-to-end workflows.

Palantir MCP is an implementation of the Model Context Protocol ↗ that allows AI IDEs and AI agents to autonomously build end-to-end applications in the Palantir platform - from data integration through ontology configuration and application development. In addition, you can use Palantir MCP to allow external AI systems to query documentation, metadata, and data, as well as perform high-level tasks on the platform. Developers can use Palantir MCP to automate auxiliary tasks while they stay focused on the system they are building.

Ontology MCP (OMCP) is a Developer Console feature that exposes your application's ontology resources as Model Context Protocol (MCP) tools, enabling external AI agents to interact with your ontology. While Palantir MCP is designed for ontology builders and development workflows, Ontology MCP is designed for ontology consumers: external AI agents that need to safely read and write data to production ontology data.

Ontology MCP exposes object types, action types, and query functions as MCP tools, and integrates with desktop agents and headless agent frameworks.

The Compute Modules feature enables you to deploy interactive containers on the Palantir platform, allowing you to bring in your existing code base (regardless of language) and run it inside the platform. With Compute Modules, for example, you could bring a third-party machine learning model into the platform and integrate it into your workflow.

For more information about Compute Modules, you can watch this official Build with AIP: Compute Modules ↗ video and reference the documentation.

Custom endpoints enable developers to configure and deploy user-defined API endpoints with their own URL patterns, request and response shapes, and specifications, while leveraging Foundry's back-end capabilities. These endpoints are backed by the ontology through actions and functions.