I’m trying to integrate Palantir Foundry MCP as a remote MCP server, with SnapLogic acting as the MCP client

Ask the Community
1

Hi everyone,

I’m trying to integrate Palantir Foundry MCP as a remote MCP server, with SnapLogic acting as the MCP client.

SnapLogic requires:

  • An HTTP(S) MCP endpoint URL

  • An authentication token (Bearer or similar)

My questions are:

  1. Does Palantir Foundry expose MCP over a public/accessible HTTP URL, similar to other remote MCP servers (for example GitHub MCP)?

  2. If yes, how can we identify the correct MCP endpoint URL (e.g. /mcp, /mcp/stream, etc.)?

  3. What is the recommended authentication mechanism for MCP access (OAuth2, Foundry token, service account token, etc.)?

  4. Are there any network or security prerequisites (allowlists, reverse proxy, gateway configuration) required to access MCP externally?

The goal is to connect Palantir MCP purely via URL + auth token, without deploying any local adapters, so that SnapLogic can consume Palantir tools as a remote MCP server.

Any guidance or official documentation pointers would be really helpful.

Thanks in advance!

2

Hey, welcome to the community!

You can look into enabling MCP Hub from the Control Panel, and then accessing it via <your_enrollment_prefix>.palantirfoundry.com/workspace/mcp-hub-app.

Not 100% sure on anything specific for SnapLogic, but the generic approach looks good.

Additional MCP docs can be found here. https://www.palantir.com/docs/foundry/palantir-mcp/overview

Happy building!
Ray

3

Hey Kunal, as far as I am aware:
Palantir MCP does not expose a public HTTP endpoint.

It’s designed to run locally via stdio (standard input/output) and connects to Foundry APIs using your token. The architecture is:

[MCP Client] → [Local MCP Server (stdio)] → [Foundry REST APIs (HTTPS)]

To expose any MCP server over HTTP, you need to either:
- Use/build an HTTP adapter (like https://github.com/sparfenyuk/mcp-proxy)
- Wait for vendors to offer hosted versions

https://www.palantir.com/docs/foundry/palantir-mcp/installation
https://www.palantir.com/docs/foundry/palantir-mcp/overview

1 Like
4

Hey,

We are working on a new capability named Ontology-MCP which will convert every Dev Console application to a remote streamableHttp MCP server. We have tested this with different agents including CopilotStudio, ADK, Claude and more.

See this demo during DevCon4.

If this is something you want to try I am happy to include you as an early adopter.

I will need to know which stack you are runing on and what is your enrollment id (can be found in Control Panel).

Feel free to ping me on ewitkon@palantir.com

5

Hey @ewitkon , thanks for sharing this sounds really interesting.

At the moment, our primary objective is to validate MCP access using MCP Inspector before moving to any downstream MCP clients like SnapLogic. As advised by the SnapLogic MCP expert, unless the MCP server works end-to-end with MCP Inspector, it won’t be consumable by external MCP clients either.

We’re specifically trying to understand:

  • What the exact MCP endpoint URL would look like for MCP Inspector

  • What authentication mechanism is supported (Foundry token, service account, OAuth, etc.)

Once we can successfully connect via MCP Inspector, we’d be very interested in evaluating this further and discussing early-adopter access.

Happy to share stack and enrollment details once we confirm this fits our validation path.
Thanks again!

6

Our MCP server works with MCP Inspector.

npx @modelcontextprotocol/inspector https://<REPLACE-WITH-YOUR-HOST>.palantirfoundry.com/mcp/third-party-application/<REPLACE-WITH-YOUR-DEV-CONSOLE-RID> \
  --header "Authorization: Bearer $FOUNDRY_TOKEN"

see below:

image
image5978×1328 509 KB

Please note that this is not yet deployed to your stack so will not work if you try.

Once you share your stack name and enrollment rid, I can enable it for you.

Can I get your permission to email you directly?