Polars Docs MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| host | No | Host address for HTTP/SSE transports | 127.0.0.1 |
| path | No | URL path for streamable-http transport | /mcp |
| port | No | Port number for HTTP/SSE transports | 8111 |
| transport | No | Transport method: stdio, streamable-http, sse | stdio |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_polars_versionA | Get the currently installed Polars version information |
| list_polars_componentsA | List all available high‑level Polars API components |
| search_polars_apiA | Search Polars API methods and documentation. Finds exact matches first, then falls back to fuzzy search. |
| verify_polars_apiB | Verify if a given Polars API name or signature is valid. |
| debug_polars_componentsA | Debug tool to show what components are discovered and their types |
| list_all_modern_data_stacksB | List all modern data stacks that can be used with Polars. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
All six tools have clearly distinct purposes: version info, component listing, debugging components, searching API, verifying API, and listing compatible data stacks. No overlapping functionality that would cause confusion.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_polars_components, search_polars_api). No mixing of conventions or inconsistent verb styles.
Six tools is well-scoped for a documentation-focused MCP server. Each tool addresses a distinct need (version, components, search, verification, etc.) without being too few or too many.
The surface covers the main documentation tasks: version checking, component listing, API search, verification, and debugging. A minor gap might be a specific function for fetching detailed documentation for a single API method, but search_polars_api likely covers that.