How do I run the server?
Run `dotnet build` followed by `dotnet run`. The server starts on a local HTTP URL (e.g., `http://localhost:5168`). Use the URL to connect an MCP client or test tool.
@garrardkitchen
基本情報
In this example, you host a MCP Server using HTTP Transport and use the MCP Explorer to debug/test it. There are few basic Tools: Azure, WhoIs and GitLab Tools, including 2x elicitations examples too
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"mcp-server-example-garrardkitchen": {
"command": "docker",
"args": [
"run",
"--rm",
"-it",
"\\"
]
}
}
}ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
MCP Server Example is a basic implementation of an MCP (Model Context Protocol) server built with .NET. It provides tools, resources, and prompts for interacting with MCP clients, and demonstrates integration with external services like Azure and GitLab. It is intended for developers who want to test, debug, or extend an MCP server.
Build and run the server with dotnet build and dotnet run. It listens on a local HTTP URL (e.g., http://localhost:5168). Connect via MCP Explorer X or the MCP Inspector using Streamable HTTP transport. For GitLab tools, configure a Personal Access Token (PAT) and domain using .NET user secrets with dotnet user-secrets set "GitLab:Token" and dotnet user-secrets set "GitLab:Domain".
User-Agent headers for all requests.Run `dotnet build` followed by `dotnet run`. The server starts on a local HTTP URL (e.g., `http://localhost:5168`). Use the URL to connect an MCP client or test tool.
Set a GitLab Personal Access Token and domain using .NET user secrets: `dotnet user-secrets set "GitLab:Token" <token>` and `dotnet user-secrets set "GitLab:Domain" <domain>`.
You can skip GitLab configuration; only the GitLab tools will be unavailable. All other tools, resources, and prompts work without it.
Run the MCP Explorer X Docker container (instructions provided for macOS, Linux, Windows) and add the server as a connection using the local URL (Streamable HTTP). Then browse and invoke tools from the browser UI.
No explicit authentication is built into the server itself. Azure tools rely on your local Azure CLI credentials mounted into the container, and GitLab tools use a manually configured PAT.

Model Context Protocol Servers

Health by Dr Brad works out a health plan from your own results: which screening is due at your age, and evidence-based suggestions, each with the reason and the published guideline or study behind it. Your record is one
A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
🚀 The fast, Pythonic way to build MCP servers and clients.
A search tool helps dev to solve the naming things problem.
コメント