model-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MODEL_MCP_ENDPOINTS | No | Comma-separated list of local endpoint base URLs. Defaults to common Ollama, LM Studio, and LocalAI localhost URLs. | |
| MODEL_MCP_TIMEOUT_MS | No | Timeout for each endpoint discovery request. Default is 2000. | 2000 |
| MODEL_MCP_ALLOW_REMOTE | No | Allows non-loopback endpoints when set to 'true'. Default is 'false'. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_local_modelsA | Discover models from configured localhost model runtimes such as Ollama, LM Studio, and LocalAI. |
| get_model_endpoint_configA | Return the local MCP and model endpoint configuration to share with Copilot or another MCP client. |
| describe_model_endpointA | Inspect one configured endpoint by id and report whether it is reachable and which models it exposes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| local-model-endpoints | Reachability and model metadata for configured localhost model runtimes. |
| copilot-mcp-config | Example MCP client configuration that lets Copilot start this server. |
TDQS
Scored across 3 tools
Each tool targets a distinct concern: discovering models, retrieving shareable config, and inspecting a specific endpoint. There is no meaningful overlap—list_local_models is about discovery, get_model_endpoint_config is about config export, and describe_model_endpoint is about state inspection of one endpoint.
All tool names follow the same verb_noun convention with consistent snake_case. The verbs list, get, and describe are distinct actions that map to each tool's purpose without stylistic drift.
Three tools is well-scoped for a server whose purpose is to discover, inspect, and share local model endpoint information. Each tool earns its place without redundancy or bloat.
The server covers the full intended workflow: discover local models, inspect a specific endpoint's reachability and models, and retrieve the configuration for sharing with a client. Since it is an inspection/discovery server, not a management API, there are no obvious missing operations.