Run History APIs MCP Server Integration
The Run History APIs, provided by Microsoft Azure Machine Learning Services, constitute a comprehensive suite of endpoints designed for managing and analyzing the lifecycle of machine learning experiments. This API collection serves as the foundational infrastructure for recording, retrieving, and organizing all metadata associated with ML runs, including parameters, metrics, outputs, and tags. Its core capabilities enable programmatic access to an experiment's audit trail, allowing developers and data scientists to fetch detailed run histories, update experiment metadata, manage tags for organization, ingest batch events and run updates, and query specific performance metrics. This API is essential for enterprise MLOps (Machine Learning Operations) workflows, providing the data backbone for experiment tracking, model reproducibility, performance monitoring, and compliance auditing across projects and teams.
Technical Integration & Multi-Client Support
The Run History APIs MCP Integration translates REST paths, operational endpoints, and tool schemas into standardized Model Context Protocol JSON-RPC 2.0 messages. This allows AI assistants like Claude Desktop, Cursor IDE, VS Code (Cline/Roo Code), and Zed Editor to run tool queries and execute functions seamlessly.
Add stdio configuration block to claude_desktop_config.json.
Configure workspace root at .cursor/mcp.json or Settings -> MCP.
Insert server JSON payload into cline_mcp_settings.json.
Specification & Compatibility Table
| Property | Specification Detail |
|---|---|
| Target Integration | Run History APIs (azure-com-machinelearningservices-runhistory) |
| Directory Category | developer tools |
| Protocol Spec | JSON-RPC 2.0 (stdio) |
| Canonical Path | /mcp/azure-com-machinelearningservices-runhistory/ |
Frequently Asked Questions
How do I access the full JSON configuration for Run History APIs?
Click 'Open Full Run History APIs MCP Config' above to view the complete parameter schema, environment variable setup, and copy-pasteable JSON configs for Claude Desktop, Cursor, and VS Code.
Does Run History APIs require authentication secrets?
Authentication depends on upstream API requirements. Check the environment variable table on the detail page to view required API keys and header tokens.
Related Integrations
GitHub API MCP
Access GitHub repositories, issues, pull requests, and more. Integrate GitHub workflows directly into your AI agent.
GitLab API MCP
Manage repositories, CI/CD pipelines, and merge requests through your AI agent.
Box Platform API MCP
The Box Platform API, provided by Box (box.com), is a robust and comprehensive RESTful service that enables deep integration with the Box cloud content management ecosystem. It serves as the programmatic backbone for enterprises and developers seeking to build custom applications and workflows that interact with content stored securely in Box. Its core capabilities extend far beyond basic file operations, encompassing a full spectrum of content lifecycle management. Developers can programmatically create, upload, download, search, and manage files and folders, but the API's true power lies in its enterprise-grade features. These include advanced collaboration management through invitations and permissions, granular user and group administration within an enterprise directory, and sophisticated security and compliance controls. Specific endpoint groups for managing collaboration whitelists and exempt targets allow for precise governance over external sharing policies, ensuring that content is only shared with approved domains. Furthermore, the API facilitates complex legal and compliance use cases, such as placing items on legal hold or applying retention policies, making it an indispensable tool for regulated industries and large organizations.
Asana MCP
This API serves as the programmatic backbone for the Asana work management platform, provided by Asana, Inc. It enables developers to interact programmatically with one of the world's leading enterprise collaboration and productivity suites. The core capabilities of this interface center around the CRUD (Create, Read, Update, Delete) operations for fundamental Asana objects. Specifically, the provided endpoints grant control over project attachments—allowing for the uploading, retrieval, and management of files associated with tasks and projects—and custom fields, which are pivotal for creating structured, data-rich workflows. These custom fields allow organizations to define unique data types (like dropdown menus, text fields, or dates) to standardize information capture across projects, moving beyond basic task lists to true operational tracking. Typical use cases span from enterprise project management offices (PMOs) needing to programmatically generate status reports and audit attachments, to development teams automating the creation of bug-tracking projects with predefined custom fields for severity and status, to operational leaders building dashboards that aggregate and analyze custom field data for resource allocation insights.
More in Developer Tools
Browse by Category
Explore MCP server integrations organized by platform and use case.