mlx-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MLX_API_KEY | No | API key for secured backends | |
| MLX_TIMEOUT | No | Request timeout in seconds | 30 |
| MLX_BASE_URL | No | Backend URL | http://localhost:8080 |
| MLX_DEFAULT_MODEL | No | Model name — required for Ollama |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chatB | Send a message to the local LLM and return the response with token usage. |
| quick_testB | Run a predefined diagnostic prompt to sanity-check the loaded model. |
| health_checkA | Check whether the configured LLM backend is reachable. |
| list_modelsA | List available models on the configured backend. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_config | Current server configuration (API key is not exposed). |
| get_usage_docs | Setup and usage documentation. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: chat for conversation, health_check for backend connectivity, list_models for available models, and quick_test for a diagnostic check. No overlap.
Tool names use different patterns: chat is a bare verb, health_check is noun_verb, list_models is verb_noun, and quick_test is adjective_noun. While readable, there is no consistent convention.
With 4 tools, the server is well-scoped for its purpose of local LLM interaction. Each tool serves a necessary function without bloat.
Core interactions (chat, health, model listing, diagnostic) are covered. Minor gaps exist, such as lack of model configuration or streaming support, but the set is sufficient for basic use.