Foundry MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Foundry MCP Server list datasets in the sales ontology"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Foundry MCP Server
A Model Context Protocol server for interacting with Foundry. It allows AI assistants to interact with datasets, ontology objects and functions.
Tools 🌟
list datasets
query datasets
list ontology objects
query ontology objects
list functions
execute functions
Related MCP server: mcp-ohmy-sql
Prerequisites
Python 3.9+
mcp
pyarrow
pandas
foundry-platform-sdk
Environment Variables 🌍
The server requires few configuration variables to run:
Variable | Description | Default |
| Your hostname of your Foundry instance | required |
| A user token that you can generate in your profile page | required* |
| A service user that is created in developer console | required* |
| A secret associated with the service user | required* |
| Oauth scopes | None |
| Your ontology id | required |
if token is not provided the server will try to authenticate using the oauth2 flow with client_id and client_secret
Usage
uv
first you need to clone the repository and add the config to your app
{
"mcpServers": {
"foundry": {
"command": "uv",
"args": [
"--directory",
"<path_to_mcp_server>",
"run",
"mcp-server-foundry"
],
"env": {
"HOSTNAME": "<hostname>",
"TOKEN": "<token>",
"CLIENT_ID": "<client_id>",
"CLIENT_SECRET": "<client_secret>",
"SCOPES": "<scopes>",
"ONTOLOGY_ID": "<ontology_id>"
}
}
}
}Development
To run the server in development mode:
# Clone the repository
git clone git@github.com:qwert666/mcp-server-foundry.git
# Run the server
npx @modelcontextprotocol/inspector uv --directory /path/to/mcp-foundry-server run mcp-server-foundryContributing
Fork the repository
Create your feature branch (git checkout -b feature/amazing-feature)
Commit your changes (git commit -m 'Add some amazing feature')
Push to the branch (git push origin feature/amazing-feature)
Open a Pull Request
License 📜
MIT License - see LICENSE file for details
Available Tools
5 toolsexecute_functionD
Execute a function using given parameters
Inputs: query_api_name (required), parameters (required).
list_functionsB
List all available functions
Inputs: no named parameters.
list_ontology_typesC
List all the ontology types
Inputs: no named parameters.
query_datasetC
Query a dataset using Spark SQL dialect e.g. "SELECT COUNT(*) FROM dataset_rid"
Inputs: query (required).
query_ontology_typeA
Query for objects in a given ontology type. Use list_ontology_types to get the list of available types
Inputs: where (required), object_type (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap. execute_function runs code, list_functions enumerates functions, list_ontology_types lists types, query_dataset queries datasets, and query_ontology_type queries specific ontology types. The descriptions clearly differentiate their scopes and usage contexts.
All tools follow a consistent verb_noun pattern using snake_case. The verbs (execute, list, query) are appropriately chosen for their actions, and the nouns (function, ontology_type, dataset) clearly indicate the target resources. No deviations or mixed conventions are present.
With 5 tools, this server is well-scoped for its apparent domain of data and function management in a Foundry context. Each tool serves a distinct and necessary purpose, covering listing, querying, and execution operations without bloat or redundancy.
The toolset provides solid coverage for querying and listing operations on functions, datasets, and ontology types, with execute_function enabling action. A minor gap exists in update/delete operations for these resources, but agents can likely work with the provided read/execute capabilities for common workflows.
Maintenance
Related MCP Connectors
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
MCP server that lets your AI assistant build and deploy apps, hosting each one at a live URL.
Hosted MCP server connecting AI assistants to 9,000+ apps and 40,000+ actions via Zapier.
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server that enables AI assistants to query databases, execute SQL, and manage Metabase resources like dashboards, cards, and collections through natural language.22MIT
- -licenseNot gradedqualityDmaintenanceAn MCP server that bridges AI assistants with SQL databases, enabling natural language querying across multiple database types with built-in optimization and security.3-
- AlicenseBqualityDmaintenanceA standalone MCP server that brings complete data science capabilities to AI assistants, enabling them to load data, train models, and track experiments through natural language.301MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI assistants the ability to connect to, query, profile, and monitor data sources — turning any LLM into an interactive data engineering copilot.MIT