working with this repository.
## Project Overview
This is a collection of **Model Context Protocol (MCP) servers** for managing infrastructure components. Each MCPserver provides AI assistants with direct API access
command standalone (no consumer wrapper needed). |
| `dart run fluttersdk_artisan:mcp` | Stdio JSON-RPC MCPserver entry. Reads `~/.artisan/state.json` for VM Service URI; soft-fails when no Flutter
Copilot Instructions - Sitecore MCPServer
## Project Context
Dit is een **Model Context Protocol (MCP) server** voor Sitecore integratie. Het project maakt het mogelijk om vanuit AI assistenten (Claude, GitHub Copilot
fields in `AGENTS.md`
> before your first agent session.
> Project-specific commands, HPC paths, and MCPservers are listed in
> `AGENTS.md` §"Key commands" and §"MCPservers configured for this project
Keep reviews focused on current PR quality, not rehashing known future work.
---
## Project Overview
MCPserver exposing FOAAS (Fuck Off As A Service) via Docker. Uses stdio transport
Responsible for the FusionAL execution engine (`C:\Users\puddi\projects\FusionAL\core\`). Manages dynamic MCPserver registration, sandboxed code execution, and AI-generated server deployment. FusionAL is the platform
Task Anchor Enforcement Protocol
This project includes a Task Anchor MCPserver that enforces ADHD executive function constraints. Connect to it via MCP if supported, otherwise follow the manual protocol
Instructions for GoBE Backend
## Project Overview
**GoBE** is a modular and secure HTTP backend server built with Go and Gin framework. The project emphasizes zero-configuration security, interface segregation
points below are stateless clients that reach it over local HTTP.
- `cascade-mcp` — the MCPserver exposing 23 tools; this is how you, the agent, drive everything.
- `cascade
like `python -m unittest tests.test_notebook_sync...` do not work unless the layout changes.
## MCPservers
This project is Azure/Fabric/ADME-focused. When MCP tools are available, use Azure MCP for Azure
Health**: `npm run health` or `http://localhost:3000/health`
**View Logs**: `docker-compose logs -f mcp-server`
**Debug Tools**: Use `testing/test_container_tools.js` for tool validation
Remember: This is a production-ready infrastructure
server (tool catalogue, decision tree, token economy, error codes):
> [`docs/AGENT_CONTRACT.md`](../docs/AGENT_CONTRACT.md).
## Overview
MCPserver bridging pdfnative 1.8.0 (pinned `^1.8.0`) to AI clients over stdio or Streamable
HTTP, on the MCP
token budget analyser
ep2-hooks/ Hook scripts (bash + Python) for Claude Code settings.json
ep3-mcp-server/ FastMCP server with two tools, pytest suite
ep4-context-management/ State templates, PreCompact hook
make rebuild-orchestrator
make rebuild-registry
make rebuild-streamlit-app-v2
make rebuild-sandbox-mcp-server
```
---
## Testing
**All tests run inside Docker containers** via Makefile targets. Do not run pytest
machine-specific notes, MCP config, secrets, and personal prompt files in ignored local locations such as `tools/local/`
- prefer direct local runtime for frontend and dev-server projects unless a repo
Session Context (Email MCP)
You have access to an email server with 32+ tools for sending, receiving,
searching, and managing email across SMTP/IMAP, SendGrid, Mailgun, Resend,
and local test servers
have access to opencode-cli-mcp: it orchestrates opencode agent runs, sessions, and system diagnostics through opencode serve.
**Before starting work:**
1. Check server status: opencode_system(action="status