Can AI agents automate Palantir platform?

The Palantir platform (Foundry and AIP) is automatable today through its documented Foundry REST API and first-party MCP. The API is HTTPS REST with JSON request and response bodies on a customer enrollment hostname. Development calls may use a user-generated bearer token from Account Settings. Production applications must use OAuth 2.0: authorization-code to act for a user, or client-credentials to act as a service user, with scopes such as api:ontologies-read and api:ontologies-write. Official Ontology SDK bindings exist for TypeScript, Python, and Java, and the API getting-started page also shows Foundry platform SDKs. Access is enrollment-gated; AIP Developer Tier is a trial path, not an open public API. Palantir MCP is a first-party Model Context Protocol server that platform administrators must enable in Control Panel. It installs via npx palantir-mcp with a Foundry user token and exposes documented tools for Compass, datasets, SQL, ontology types, object queries, OSDK, Developer Console, and documentation search. Palantir MCP can change ontology types and query objects; vendor docs state it cannot write ontology instance data. Ontology MCP is a separate first-party Developer Console feature that exposes an application's objects, actions, and queries as MCP tools over the application's OAuth 2.0 client. Official MCP registry listings named Foundry IMS and FoundryNet are unrelated products. The Foundry CLI exists for SuperRepo bundle and deploy workflows and is marked beta. Zapier, Make, Power Automate, and n8n connectors were not established. Computer-use viability is unassessed. API scores 8 and is the best path because it is the documented machine contract; MCP is official but admin-gated and split across a builder server and a per-application consumer server.

Best path today: api · Overall automatability: 8/10