🧪 Foundry MCP Playground

Created By
Ravindrabantua year ago
Overview

What is Foundry MCP Playground?

Foundry MCP Playground is a streamlined development environment designed for rapid prototyping with the MCP Server that interacts with Azure AI Foundry, allowing users to explore and utilize advanced AI models.

How to use Foundry MCP Playground?

To use Foundry MCP Playground, create a new repository from the provided template, open it in GitHub Codespaces or VS Code, and follow the setup instructions to enable Agent Mode and start using the MCP Server.

Key features of Foundry MCP Playground?

  • One-click setup for rapid prototyping.
  • Integration with Azure AI Foundry for accessing state-of-the-art AI models.
  • Tools for managing and querying knowledge using Azure AI Search.
  • Observability features for evaluating text and agent responses.

Use cases of Foundry MCP Playground?

  1. Prototyping AI-based solutions using Azure AI models.
  2. Exploring and comparing different AI models from Azure AI Foundry.
  3. Building applications that utilize AI for various tasks such as UX analysis and model evaluation.

FAQ from Foundry MCP Playground?

  • Can I use Foundry MCP Playground for any AI model?

Yes! It supports a variety of models available in Azure AI Foundry.

  • Is there a cost associated with using Foundry MCP Playground?

No, it is free to use as it is a template provided on GitHub.

  • What tools are available in this environment?

The environment comes pre-equipped with tools that can be used in natural language prompts while coding.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Ravindrabantu
Star
0
Language
Dockerfile
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago