model-mcp
Discovers local Ollama instances and exposes their endpoint metadata, reachability, and available model IDs to MCP clients.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@model-mcp what local models are available?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
model-mcp
model-mcp is a Model Context Protocol (MCP) server that discovers local model runtimes and exposes their endpoint metadata to MCP clients such as Copilot.
It checks common localhost endpoints for:
Ollama (
http://127.0.0.1:11434/api/tags)LM Studio (
http://127.0.0.1:1234/v1/models)LocalAI or OpenAI-compatible local servers (
http://127.0.0.1:8080/v1/models)
The server does not proxy prompts or model completions. It advertises where local models are available so an MCP-aware client can inspect and use that configuration.
Install
Run from a source checkout
git clone https://github.com/shakerg/model-mcp.git
cd model-mcp
npm install
npm run buildIn the GitHub Copilot app, add a local/stdio MCP server. Use the absolute path to the checkout:
{
"servers": {
"local-models": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/model-mcp/dist/index.js"]
}
}
}You can also run the checkout directly with npm start; it communicates over stdio and normally waits silently for an MCP client.
Install from npm
If npm view model-mcp version returns the release you want, add a local/stdio MCP server in the GitHub Copilot app and let npx download and launch it:
{
"servers": {
"local-models": {
"type": "stdio",
"command": "npx",
"args": ["-y", "model-mcp@<published-version>"]
}
}
}Use the package's exact published version for reproducible installation.
Install from Docker
Images are stored in this repository's GitHub Container Registry package. After the matching version is available, add a local/stdio server that keeps stdin open and maps the cross-platform Docker host name:
{
"servers": {
"local-models": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"--add-host",
"host.docker.internal:host-gateway",
"ghcr.io/shakerg/model-mcp:<published-version>"
]
}
}
}The image defaults to the common model ports on host.docker.internal, allowing the container to discover Ollama, LM Studio, and LocalAI running on the host. Use MODEL_MCP_ENDPOINTS to override those endpoints.
Install from an MCP registry
After a release is listed in an MCP registry, supported Copilot clients can choose either the npm or Docker package instead of entering the command manually. The installer reads server.json and presents these optional environment fields:
MODEL_MCP_ENDPOINTSMODEL_MCP_TIMEOUT_MSMODEL_MCP_ALLOW_REMOTE
Leave a field unset to use its default. Registry installation is available only after the package or image version referenced by server.json has been published.
https://github.com/shakerg/model-mcp is a repository page, not a remote MCP endpoint. Do not enter it as an HTTP, SSE, or streamable HTTP server URL. This project is a local stdio server; treating the GitHub URL as an MCP endpoint sends protocol requests to a web page and results in HTTP errors such as 422 with an HTML response.
Related MCP server: mcp-file-system-lmstudio
Configuration
Set MODEL_MCP_ENDPOINTS to a comma-separated list of local endpoint base URLs when your model servers use different ports.
MODEL_MCP_ENDPOINTS="http://127.0.0.1:11434,http://127.0.0.1:1234" npm startBy default, only loopback hosts and Docker's host.docker.internal gateway are accepted. Set MODEL_MCP_ALLOW_REMOTE=true only when you intentionally want to expose other model endpoints through the MCP server.
Optional environment variables:
Variable | Default | Description |
| Common Ollama, LM Studio, and LocalAI localhost URLs | Comma-separated endpoint base URLs. |
|
| Timeout for each endpoint discovery request. |
|
| Allows non-loopback endpoints when set to |
MCP capabilities
Tools
list_local_models- returns configured endpoints, reachability, and discovered model IDs.describe_model_endpoint- inspects one endpoint by ID, such asollamaorlm-studio.get_model_endpoint_config- returns an MCP configuration snippet that can be used by Copilot or another MCP client.
Resources
local-models://endpoints- JSON description of discovered endpoints and models.local-models://copilot-config- JSON MCP configuration example for launching this server.
Development
npm run test:package
npm run test:dockertest:package type-checks the source, validates server.json against its official MCP schema, creates the npm tarball, checks that dist/index.js is executable and included, installs the tarball into a clean temporary project, and completes an MCP initialize/list-tools exchange over stdio.
test:docker builds the production image and completes the same MCP initialize/list-tools exchange through docker run.
When Docker-related source changes merge to main, the Publish container GitHub Actions workflow builds linux/amd64 and linux/arm64 images and pushes both the package version and latest tags to this repository's GHCR package. The workflow rejects an existing version tag, so image changes require a version bump.
Publishing checklist
Publication requires maintainer access to npm, GitHub Container Registry, and the MCP registry:
Run
npm run test:package.Confirm the version matches in
package.json,server.json, andsrc/index.ts, and thatpackage.json#mcpNamematchesserver.json#name.Publish with the project owner's npm account or configured trusted publishing.
Confirm
npm view model-mcp versionreturns the released version.Merge the release PR to
mainto publish the multi-platform image, then make the GHCR package public if it does not inherit public visibility and verify its version tag.Only then publish
server.jsonto an MCP registry.
Available Tools
3 toolsdescribe_model_endpointDescribe model endpointA
Inspect one configured endpoint by id and report whether it is reachable and which models it exposes.
Inputs: endpointId (required).
get_model_endpoint_configGet model endpoint configurationA
Return the local MCP and model endpoint configuration to share with Copilot or another MCP client.
Inputs: no named parameters.
list_local_modelsList local modelsA
Discover models from configured localhost model runtimes such as Ollama, LM Studio, and LocalAI.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Agent-native registry to discover APIs, MCP servers and CLIs, with live health checks.
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
MCP-Native LLM Orchestration Agent
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Related MCP Servers
AlicenseAqualityBmaintenanceUnified MCP server for managing local model runtimes (Ollama, LM Studio, etc.), enabling provider-agnostic discovery, lifecycle management, hardware-fit checks, and delegated inference.22516 npmCreative Commons Attribution Non Commercial No Derivatives 4.0 International- AlicenseNot gradedqualityDmaintenanceExposes local LM Studio language models as MCP tools, enabling chat completions and model listing through a local OpenAI-compatible API without requiring API keys.MIT
- AlicenseNot gradedqualityBmaintenanceEnables local AI models to be used through MCP, exposing tools for coding assistance, code review, model listing, status checks, and benchmarking.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients to manage, run, and interact with local or cloud LLM models through exposed tools for listing, pulling, generating, chatting, embeddings, and web search/fetch. Supports Claude Desktop, Cline, and hybrid local/cloud setups.812 npmAGPL 3.0