mcp-geo-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEBUI_PORT | No | Port for the test UI | 8000 |
| OLLAMA_HOST | No | Local Ollama endpoint (ollama provider) | http://localhost:11434 |
| GEO_MCP_HOST | No | Bind host when transport is http | 0.0.0.0 |
| GEO_MCP_PORT | No | Port when transport is http | 9000 |
| OLLAMA_MODEL | No | Ollama model (must support tool calling); cloud model id for ollama-cloud | qwen2.5 |
| GEOSERVER_URL | Yes | Base URL of GeoServer, e.g. http://localhost:8080/geoserver | |
| GEOSERVER_USER | Yes | REST username for GeoServer | |
| OLLAMA_API_KEY | No | Ollama Cloud API key (required for ollama-cloud provider) | |
| ANTHROPIC_MODEL | No | Claude model (anthropic provider) | claude-sonnet-4-6 |
| GEO_LLM_PROVIDER | No | Agent LLM backend: ollama, ollama-cloud or anthropic | ollama |
| ANTHROPIC_API_KEY | No | Anthropic API key (required for anthropic provider) | |
| GEOSERVER_RETRIES | No | Retry attempts on connect/timeout/502/503/504 | 2 |
| GEOSERVER_TIMEOUT | No | HTTP timeout (seconds) | 30 |
| GEO_MCP_TRANSPORT | No | MCP transport: stdio or http | stdio |
| OLLAMA_CLOUD_HOST | No | Ollama Cloud endpoint (ollama-cloud provider) | https://ollama.com |
| GEOSERVER_PASSWORD | Yes | REST password for GeoServer | |
| GEO_MAP_OUTPUT_DIR | No | Where generated maps / downloaded PNGs are saved | ./maps |
| GEOSERVER_VERIFY_TLS | No | Verify TLS certificates | true |
| GEOSERVER_DEFAULT_SRS | No | SRS used when publishing without one | EPSG:4326 |
| GEOSERVER_RETRY_BACKOFF | No | Linear backoff factor (seconds × attempt) | 0.5 |
| GEOSERVER_DEFAULT_WORKSPACE | No | Workspace used when a tool omits one |
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
} |
| logging | {} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geoserver-agentB | Intelligent assistant that administers and queries a GeoServer instance: workspaces, PostGIS datastores, feature types, layers, SLD styles, and OGC WMS/WFS/WFS-T operations. |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The single tool serves all purposes.
With a single tool, naming is trivially consistent. The name 'geoserver-agent' clearly indicates its role.
One tool for a broad domain (GeoServer administration, queries, OGC operations) is too coarse. It would be better to split into multiple focused tools (e.g., workspaces, datastores, layers). The single agent obscures individual capabilities.
The tool claims to handle many GeoServer aspects (workspaces, datastores, feature types, layers, styles, OGC operations), so coverage is broad. However, because it's a single monolithic agent, it's unclear whether all operations are reliably exposed or if there are gaps. A proper tool set would make completeness more assessable.