Skip to main content
Glama
mahdin75

GeoServer MCP Server

by mahdin75
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GEOSERVER_URLYesURL of your GeoServer instancehttp://localhost:8080/geoserver
GEOSERVER_USERYesUsername for GeoServer authenticationadmin
GEOSERVER_PASSWORDYesPassword for GeoServer authenticationgeoserver

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
list_workspacesB

List available workspaces in GeoServer.

create_workspaceC

Create a new workspace in GeoServer.

Args:
    workspace: Name of the workspace to create

Returns:
    Dict with status and result information
get_layer_infoC

Get detailed information about a layer.

Args:
    workspace: The workspace containing the layer
    layer: The name of the layer

Returns:
    Dict with layer metadata
list_layersB

List layers in GeoServer, optionally filtered by workspace.

Args:
    workspace: Optional workspace to filter layers

Returns:
    List of layer information dictionaries
create_layerC

Create a new layer in GeoServer.

Args:
    workspace: The workspace for the new layer
    layer: The name of the layer to create
    data_store: The data store to use
    source: The source data (file, table name, etc.)

Returns:
    Dict with status and layer information
delete_resourceC

Delete a resource from GeoServer.

Args:
    resource_type: Type of resource to delete (workspace, layer, style, etc.)
    workspace: The workspace containing the resource
    name: The name of the resource

Returns:
    Dict with status and result information
query_featuresB

Query features from a vector layer using CQL filter.

Args:
    workspace: The workspace containing the layer
    layer: The layer to query
    filter: Optional CQL filter expression
    properties: Optional list of properties to return
    max_features: Maximum number of features to return

Returns:
    GeoJSON FeatureCollection with query results
generate_mapB

Generate a map image using WMS GetMap.

Args:
    layers: List of layers to include (format: workspace:layer)
    styles: Optional styles to apply (one per layer)
    bbox: Bounding box [minx, miny, maxx, maxy]
    width: Image width in pixels
    height: Image height in pixels
    format: Image format (png, jpeg, etc.)

Returns:
    Dict with map information and URL
create_styleB

Create a new SLD style in GeoServer.

Args:
    name: Name for the style
    sld: SLD XML content
    workspace: Optional workspace for the style

Returns:
    Dict with status and style information

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
geoserver://catalog/workspaces
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 9 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity. The tools cover different operations like creation (create_layer, create_style, create_workspace), deletion (delete_resource), retrieval (get_layer_info, list_layers, list_workspaces), querying (query_features), and visualization (generate_map). There is no overlap in functionality.

Naming Consistency5/5

Tool names follow a consistent verb_noun pattern throughout, using snake_case. All tools start with a clear action verb (create, delete, generate, get, list, query) followed by a specific noun, making them predictable and readable.

Tool Count5/5

With 9 tools, this server is well-scoped for managing a GeoServer instance. It covers essential operations for workspaces, layers, styles, and maps without being overly complex or too sparse, making it efficient for agents to handle geospatial data tasks.

Completeness4/5

The tool set provides comprehensive coverage for core GeoServer operations, including CRUD for layers, styles, and workspaces, along with querying and map generation. A minor gap exists in updating resources (e.g., update_layer or update_style), but agents can work around this by deleting and recreating.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources