Skip to main content
Glama
Foundry MCP Server

Foundry MCP Server

by qwert666

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

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

Available Tools

5 tools
execute_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

    B3.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI assistants to query databases, execute SQL, and manage Metabase resources like dashboards, cards, and collections through natural language.
      22
      MIT
    • -
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that bridges AI assistants with SQL databases, enabling natural language querying across multiple database types with built-in optimization and security.
      3
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An 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