MCP-Plugin-dotnet
by IvanMurzak
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PLUGIN_PORT | No | The port the SignalR hub listens on. | 8080 |
| MCP_PLUGIN_TOKEN | No | Bearer token required from connecting plugins. | |
| MCP_AUTHORIZATION | No | Authorization mode: none or required. | none |
| MCP_PLUGIN_WEBHOOK_TOKEN | No | Security token sent in each webhook request header. | |
| MCP_PLUGIN_CLIENT_TIMEOUT | No | Timeout for plugin operations (ms). | 10000 |
| MCP_PLUGIN_WEBHOOK_HEADER | No | Header name for the security token. | X-Webhook-Token |
| MCP_PLUGIN_WEBHOOK_TIMEOUT | No | HTTP delivery timeout in milliseconds. | 10000 |
| MCP_PLUGIN_CLIENT_TRANSPORT | No | Transport method: stdio or streamableHttp. | streamableHttp |
| MCP_PLUGIN_WEBHOOK_TOOL_URL | No | Endpoint to receive tool call events. | |
| MCP_PLUGIN_WEBHOOK_PROMPT_URL | No | Endpoint to receive prompt retrieval events. | |
| MCP_PLUGIN_IDLE_TIMEOUT_SECONDS | No | streamableHttp only: idle window before an MCP session is evicted from the in-memory tracker. | 600 |
| MCP_PLUGIN_WEBHOOK_RESOURCE_URL | No | Endpoint to receive resource access events. | |
| MCP_PLUGIN_MAX_IDLE_SESSION_COUNT | No | streamableHttp only: hard ceiling on retained idle MCP sessions. | 1000 |
| MCP_PLUGIN_WEBHOOK_CONNECTION_URL | No | Endpoint to receive client connect/disconnect events. | |
| MCP_PLUGIN_WEBHOOK_AUTHORIZATION_URL | No | Endpoint that authorizes/denies connections. | |
| MCP_PLUGIN_WEBHOOK_AUTHORIZATION_FAIL_OPEN | No | When true, allow connections if webhook times out or errors. When false, deny on failure. | false |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/IvanMurzak/MCP-Plugin-dotnet'
If you have feedback or need assistance with the MCP directory API, please join our Discord server