About Foundry
Foundry is an MCP server published by qwert666 in the AI category: a Model Context Protocol server for interacting with Foundry.
The repository has 11 stars and 6 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.
Install
git clone https://github.com/qwert666/mcp-server-foundryThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Foundry
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 3 days ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- ✓License declaredUsable under a stated license.
- !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
1 check has not been run yet.
README
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
Prerequisites
- Python 3.9+
- mcp
- pyarrow
- pandas
- foundry-platform-sdk
Environment Variables 🌍
The server requires few configuration variables to run:
| Variable | Description | Default |
|---|---|---|
HOSTNAME |
Your hostname of your Foundry instance | required |
TOKEN |
A user token that you can generate in your profile page | required* |
CLIENT_ID |
A service user that is created in developer console | required* |
CLIENT_SECRET |
A secret associated with the service user | required* |
SCOPES |
Oauth scopes | None |
ONTOLOGY_ID |
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-foundry
Contributing
- 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
README fetched from the repository 3 days ago. The original is authoritative.