Skip to content
Back to search

geoserver-mcp

A Model Context Protocol (MCP) server implementation that connects LLMs to the GeoServer REST API

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/mahdin75--geoserver-mcp/badge.svg)](/listings/mahdin75--geoserver-mcp)

HTML

<a href="/listings/mahdin75--geoserver-mcp"><img src="/api/listings/mahdin75--geoserver-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Choose the installation method that best suits your needs:

Installing via Smithery

To install GeoServer MCP Server for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@mahdin75/geoserver-mcp):

npx -y @smithery/cli install @mahdin75/geoserver-mcp --client claude

๐Ÿ› ๏ธ Installation (Docker)

The Docker installation is the quickest and most isolated way to run the GeoServer MCP server. It's ideal for:

- Quick testing and evaluation - Production deployments - Environments where you want to avoid Python dependencies - Consistent deployment across different systems

1. Run geoserver-mcp:

docker pull mahdin75/geoserver-mcp
docker run -d mahdin75/geoserver-mcp

2. Configure the clients:

If you are using Claude Desktop, edit `claude_desktop_config.json` If you are using Cursor, Create `.cursor/mcp.json`

{
  "mcpServers": {
    "geoserver-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "GEOSERVER_URL=http://localhost:8080/geoserver",
        "-e",
        "GEOSERVER_USER=admin",
        "-e",
        "GEOSERVER_PASSWORD=geoserver",
        "-p",
        "8080:8080",
        "mahdin75/geoserver-mcp"
      ]
    }
  }
}

๐Ÿ› ๏ธ Installation (pip)

The pip installation is recommended for most users who want to run the server directly on their system. This method is best for:

- Regular users who want to run the server locally - Systems where you have Python 3.10+ installed - Users who want to customize the server configuration - Development and testing purposes

1. Install uv package manager.

pip install uv

2. Create the Virtual Environment (Python 3.10+):

**Linux/Mac:**

uv venv --python=3.10

**Windows PowerShell:**

uv venv --python=3.10

3. Install the package using pip:

uv pip install geoserver-mcp

4. Configure GeoServer connection:

**Linux/Mac:**

export GEOSERVER_URL="http://localhost:8080/geoserver"
export GEOSERVER_USER="admin"
export GEOSERVER_PASSWORD="geoserver"

**Windows PowerShell:**

$env:GEOSERVER_URL="http://localhost:8080/geoserver"
$env:GEOSERVER_USER="admin"
$env:GEOSERVER_PASSWORD="geoserver"

5. Start the server:

If you are going to use Claude desktop you don't need this step. For cursor or your own custom client you should run the following code.

**Linux:**

source .venv/bin/activate

geoserver-mcp

or

source .venv/bin/activate

geoserver-mcp --url http://localhost:8080/geoserver --user admin --password geoserver --debug

**Windows PowerShell:**

.\.venv\Scripts\activate
geoserver-mcp

or

.\.venv\Scripts\activate
geoserver-mcp --url http://localhost:8080/geoserver --user admin --password geoserver --debug

6. Configure Clients:

If you are using Claude Desktop, edit `claude_desktop_config.json` If you are using Cursor, Create `.cursor/mcp.json`

**Windows:**

{
  "mcpServers": {
    "geoserver-mcp": {
      "command": "C:\\path\\to\\geoserver-mcp\\.venv\\Scripts\\geoserver-mcp",
      "args": [
        "--url",
        "http://localhost:8080/geoserver",
        "--user",
        "admin",
        "--password",
        "geoserver"
      ]
    }
  }
}

**Linux:**

{
  "mcpServers": {
    "geoserver-mcp": {
      "command": "/path/to/geoserver-mcp/.venv/bin/geoserver-mcp",
      "args": [
        "--url",
        "http://localhost:8080/geoserver",
        "--user",
        "admin",
        "--password",
        "geoserver"
      ]
    }
  }
}

๐Ÿ› ๏ธ Development installation

The development installation is designed for contributors and developers who want to modify the codebase. This method is suitable for:

- Developers contributing to the project - Users who need to modify the source code - Testing new features - Debugging and development purposes

1. Install uv package manager.

pip install uv

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md ยท README ยท 698 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. [![PyPI](https://img.shields.io/pypi/v/geoserver-mcp)](https://pypi.org/project/geoserver-mcp/) [![Downloads](https://static.pepy.tech/personalized-badge/geoserver-mcp?period=total&units=international_system&left_color=grey&right_color=blue&left_text=PyPI%20downloads)](https://pepy.tech/project/geoserver-mcp)
  2. # GeoServer MCP Server
  3. <p align="center">
  4. A Model Context Protocol (MCP) server implementation that connects Large Language Models (LLMs) to the GeoServer REST API, enabling AI assistants to interact with geospatial data and services.
  5. </p>
  6. <div align="center">
  7. <img src="docs/geoserver-mcp.png" alt="GeoServer MCP Server Logo" width="400"/>
  8. </div>
  9. > Version 0.5.0 (Beta) is under active development and will be released shortly. We are open to contributions and welcome developers to join us in building this project.
  10. ## ๐ŸŽฅ Demo
  11. <div align="center">
  12. <img src="docs/demo/list_workspaces.png" alt="GeoServer MCP Server Demo" width="400"/>
  13. </div>
  14. ## ๐Ÿ“‹ Table of Contents
  15. - [Features](#-features)
  16. - [Deployment Options](#-deployment-options)
  17. - [Prerequisites](#-prerequisites)
  18. - [Installation](#๏ธ-installation)
  19. - [Docker Installation](#๏ธ-installation-docker)
  20. - [pip Installation](#๏ธ-installation-pip)
  21. - [Development Installation](#๏ธ-development-installation)
  22. - [File Storage and `--storage` Usage](#file-storage-and---storage-usage)
  23. - [Available Tools](#๏ธ-available-tools)
  24. - [Resource Endpoints](#๏ธ-resource-endpoints)
  25. - [Workspace Management](#๏ธ-workspace-management)
  26. - [Datastore & Coveragestore Management](#๏ธ-datastore--coveragestore-management)
  27. - [Layer Management](#๏ธ-layer-management)
  28. - [Layer Group Management](#๏ธ-layer-group-management)
  29. - [User & User Group Management](#๏ธ-user--user-group-management)
  30. - [Feature Type & Attribute Management](#๏ธ-feature-type--attribute-management)
  31. - [Style Management](#๏ธ-style-management)
  32. - [System & Service Operations](#๏ธ-system--service-operations)
  33. - [Style XML Utilities](#๏ธ-style-xml-utilities)
  34. - [Client Development](#๏ธ-client-development)
  35. - [List Workspaces](#list-workspaces)
  36. - [Get Layer Information](#get-layer-information)
  37. - [Query Features](#query-features)
  38. - [Generate Map](#generate-map)
  39. - [Planned Features](#-planned-features)
  40. - [Contributing](#-contributing)
  41. - [License](#-license)
  42. - [Related Projects](#-related-projects)
  43. - [Support](#-support)
  44. - [Badges](#-badges)
  45. ## ๐Ÿš€ Features
  46. - ๐Ÿ” Query and manipulate GeoServer workspaces, layers, and styles
  47. - ๐Ÿ—บ๏ธ Execute spatial queries on vector data
  48. - ๐ŸŽจ Generate map visualizations
  49. - ๐ŸŒ Access OGC-compliant web services (WMS, WFS)
  50. - ๐Ÿ› ๏ธ Easy integration with MCP-compatible clients
  51. ## ๐Ÿš€ Deployment Options
  52. GeoServer MCP can run in two ways. They share the same product idea (MCP tools over GeoServer) but are **separate artifacts**. The Python package is unchanged.
  53. ```text
  54. GeoServer MCP
  55. โ”‚
  56. โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
  57. โ”‚ โ”‚
  58. Python MCP Server GeoServer Extension
  59. โ”‚ โ”‚
  60. โ–ผ โ–ผ
  61. GeoServer GeoServer
  62. โ”‚ โ”‚
  63. โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
  64. โ”‚
  65. MCP Interface
  66. โ”‚
  67. โ–ผ
  68. AI Agents
  69. ```
  70. ### Python MCP Server
  71. Run GeoServer MCP separately (pip, Docker, or Smithery). The process speaks MCP to the agent and calls the GeoServer REST API. This is the original, currently published deployment.
  72. See [Installation](#๏ธ-installation) below.
  73. ### GeoServer Extension
  74. Install the GeoServer MCP Extension directly into GeoServer and expose a remote MCP endpoint at `/geoserver/mcp`. No Python sidecar is required. Targets GeoServer **2.28.x**.
  75. See [`extension/README.md`](extension/README.md) for architecture, installation, configuration, security, and client examples.
  76. ## ๐Ÿ“‹ Prerequisites
  77. - Python 3.10 or higher
  78. - Running GeoServer instance with REST API enabled
  79. - MCP-compatible client (like Claude Desktop or Cursor)
  80. - Internet connection for package installation
  81. ## ๐Ÿ› ๏ธ Installation
  82. Choose the installation method that best suits your needs:
  83. ### Installing via Smithery
  84. To install GeoServer MCP Server for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@mahdin75/geoserver-mcp):
  85. ```bash
  86. npx -y @smithery/cli install @mahdin75/geoserver-mcp --client claude
  87. ```
  88. ### ๐Ÿ› ๏ธ Installation (Docker)
  89. The Docker installation is the quickest and most isolated way to run the GeoServer MCP server. It's ideal for:
  90. - Quick testing and evaluation
  91. - Production deployments
  92. - Environments where you want to avoid Python dependencies
  93. - Consistent deployment across different systems
  94. 1. Run geoserver-mcp:
  95. ```bash
  96. docker pull mahdin75/geoserver-mcp
  97. docker run -d mahdin75/geoserver-mcp
  98. ```
  99. 2. Configure the clients:
  100. If you are using Claude Desktop, edit `claude_desktop_config.json`
  101. If you are using Cursor, Create `.cursor/mcp.json`
  102. ```json
  103. {
  104. "mcpServers": {
  105. "geoserver-mcp": {
  106. "command": "docker",
  107. "args": [
  108. "run",
  109. "-i",
  110. "--rm",
  111. "-e",
  112. "GEOSERVER_URL=http://localhost:8080/geoserver",
  113. "-e",
  114. "GEOSERVER_USER=admin",
  115. "-e",
  116. "GEOSERVER_PASSWORD=geoserver",
  117. "-p",
  118. "8080:8080",
  119. "mahdin75/geoserver-mcp"
  120. ]
  121. }
  122. }
  123. }
  124. ```
  125. ### ๐Ÿ› ๏ธ Installation (pip)
  126. The pip installation is recommended for most users who want to run the server directly on their system. This method is best for:
  127. - Regular users who want to run the server locally
  128. - Systems where you have Python 3.10+ installed
  129. - Users who want to customize the server configuration
  130. - Development and testing purposes
  131. 1. Install uv package manager.
  132. ```bash
  133. pip install uv
  134. ```
  135. 2. Create the Virtual Environment (Python 3.10+):
  136. **Linux/Mac:**
  137. ```bash
  138. uv venv --python=3.10
  139. ```
  140. **Windows PowerShell:**
  141. ```bash
  142. uv venv --python=3.10
  143. ```
  144. 3. Install the package using pip:
  145. ```bash
  146. uv pip install geoserver-mcp
  147. ```
  148. 4. Configure GeoServer connection:
  149. **Linux/Mac:**
  150. ```bash
  151. export GEOSERVER_URL="http://localhost:8080/geoserver"
  152. export GEOSERVER_USER="admin"
  153. export GEOSERVER_PASSWORD="geoserver"
  154. ```
  155. **Windows PowerShell:**
  156. ```powershell
  157. $env:GEOSERVER_URL="http://localhost:8080/geoserver"
  158. $env:GEOSERVER_USER="admin"
  159. $env:GEOSERVER_PASSWORD="geoserver"
  160. ```
  161. 5. Start the server:
  162. If you are going to use Claude desktop you don't need this step. For cursor or your own custom client you should run the following code.
  163. **Linux:**
  164. ```bash
  165. source .venv/bin/activate
  166. geoserver-mcp
  167. ```
  168. or
  169. ```bash
  170. source .venv/bin/activate
  171. geoserver-mcp --url http://localhost:8080/geoserver --user admin --password geoserver --debug
  172. ```
  173. **Windows PowerShell:**
  174. ```bash
  175. .\.venv\Scripts\activate
  176. geoserver-mcp
  177. ```
  178. or
  179. ```bash
  180. .\.venv\Scripts\activate
  181. geoserver-mcp --url http://localhost:8080/geoserver --user admin --password geoserver --debug
  182. ```
  183. 6. Configure Clients:
  184. If you are using Claude Desktop, edit `claude_desktop_config.json`
  185. If you are using Cursor, Create `.cursor/mcp.json`
  186. **Windows:**
  187. ```json
  188. {
  189. "mcpServers": {
  190. "geoserver-mcp": {
  191. "command": "C:\\path\\to\\geoserver-mcp\\.venv\\Scripts\\geoserver-mcp",
  192. "args": [
  193. "--url",
  194. "http://localhost:8080/geoserver",
  195. "--user",
  196. "admin",
  197. "--password",
  198. "geoserver"
  199. ]
  200. }
  201. }
  202. }
  203. ```
  204. **Linux:**
  205. ```json
  206. {
  207. "mcpServers": {
  208. "geoserver-mcp": {
  209. "command": "/path/to/geoserver-mcp/.venv/bin/geoserver-mcp",
  210. "args": [
  211. "--url",
  212. "http://localhost:8080/geoserver",
  213. "--user",
  214. "admin",
  215. "--password",
  216. "geoserver"
  217. ]
  218. }
  219. }
  220. }
  221. ```
  222. ### ๐Ÿ› ๏ธ Development installation
  223. The development installation is designed for contributors and developers who want to modify the codebase. This method is suitable for:
  224. - Developers contributing to the project
  225. - Users who need to modify the source code
  226. - Testing new features
  227. - Debugging and development purposes
  228. 1. Install uv package manager.
  229. ```bash
  230. pip install uv
  231. ```
  232. 2. Create the Virtual Environment (Python 3.10+):
  233. ```bash
  234. uv venv --python=3.10
  235. ```
  236. 3. Install the package using pip:
  237. ```bash
  238. uv pip install -e .
  239. ```
  240. 4. Configure GeoServer connection:
  241. **Linux/Mac:**
  242. ```bash
  243. export GEOSERVER_URL="http://localhost:8080/geoserver"
  244. export GEOSERVER_USER="admin"
  245. export GEOSERVER_PASSWORD="geoserver"
  246. ```
  247. **Windows PowerShell:**
  248. ```powershell
  249. $env:GEOSERVER_URL="http://localhost:8080/geoserver"
  250. $env:GEOSERVER_USER="admin"
  251. $env:GEOSERVER_PASSWORD="geoserver"
  252. ```
  253. 5. Start the server:
  254. If you are going to use Claude desktop you don't need this step. For cursor or your own custom client you should run the following code.
  255. **Linux:**
  256. ```bash
  257. source .venv/bin/activate
  258. geoserver-mcp
  259. ```
  260. or
  261. ```bash
  262. source .venv/bin/activate
  263. geoserver-mcp --url http://localhost:8080/geoserver --user admin --password geoserver --debug
  264. ```
  265. **Windows PowerShell:**
  266. ```bash
  267. .\.venv\Scripts\activate
  268. geoserver-mcp
  269. ```
  270. or
  271. ```bash
  272. .\.venv\Scripts\activate
  273. geoserver-mcp --url http://localhost:8080/geoserver --user admin --password geoserver --debug
  274. ```
  275. 6. Configure Clients:
  276. If you are using Claude Desktop, edit `claude_desktop_config.json`
  277. If you are using Cursor, Create `.cursor/mcp.json`
  278. **Windows:**
  279. ```json
  280. {
  281. "mcpServers": {
  282. "geoserver-mcp": {
  283. "command": "C:\\path\\to\\geoserver-mcp\\.venv\\Scripts\\geoserver-mcp",
  284. "args": [
  285. "--url",
  286. "http://localhost:8080/geoserver",
  287. "--user",
  288. "admin",
  289. "--password",
  290. "geoserver"
  291. ]
  292. }
  293. }
  294. }
  295. ```
  296. **Linux:**
  297. ```json
  298. {
  299. "mcpServers": {
  300. "geoserver-mcp": {
  301. "command": "/path/to/geoserver-mcp/.venv/bin/geoserver-mcp",
  302. "args": [
  303. "--url",
  304. "http://localhost:8080/geoserver",
  305. "--user",
  306. "admin",
  307. "--password",
  308. "geoserver"
  309. ]
  310. }
  311. }
  312. }
  313. ```
  314. ## File Storage and --storage Usage
  315. GeoServer MCP server supports an optional `--storage` flag to specify a base directory for all file read/write operations, such as uploading shapefiles, GeoTIFFs, or exporting results.
  316. ### Overview
  317. - The `--storage` flag sets the root folder for file operations from all data-related tools.
  318. - You may supply **relative paths** (relative to storage root) or **absolute paths** (bypassing the storage root) as arguments to relevant tools.
  319. - If `--storage` is not set, paths are resolved as provided by the user (relative to working directory or absolute).
  320. ### CLI Example
  321. ```sh
  322. python -m geoserver_mcp.main --storage D:/my/data/dir
  323. ```
  324. This sets `D:/my/data/dir` as the base path for all files.
  325. **Example tool call in Python:**
  326. ```python
  327. # Will read from D:/my/data/dir/roads.zip if --storage is set to D:/my/data/dir
  328. create_shp_datastore('workspace', 'datastore_name', 'roads.zip')
  329. ```
  330. Absolute paths (e.g. 'C:/input/other.shp') are always used as-is.
  331. ### When Running in Docker
  332. If using Docker, ensure the storage directory is mounted as a volume, e.g.:
  333. ```sh
  334. docker run -v D:/my/data:/opt/data ...
  335. ```
  336. Then launch the server with:
  337. ```sh
  338. python -m geoserver_mcp.main --storage /opt/data
  339. ```
  340. ### Best Practices
  341. - Use relative paths when interacting with the API/tools as it keeps your setup portable.
  342. - For remote or container deployment, always ensure your file data is accessible within the container (use Docker volumes if needed).
  343. - Check tool docstrings for which arguments use the storage system.
  344. The `--storage` system streamlines file management for all users and makes deployment much more flexible!
  345. ## ๐Ÿ› ๏ธ Available Tools
  346. This section details all the available tools and resources exposed by the GeoServer MCP server. These tools allow LLMs to interact with GeoServer's REST API for comprehensive geospatial data management.
  347. ### ๐ŸŒ Resource Endpoints
  348. Resource endpoints provide direct access to GeoServer resources via a URI pattern.
  349. | Resource URI | Description |
  350. | :----------------------------------------------- | :------------------------------------- |
  351. | `geoserver://catalog/workspaces` | List available workspaces |
  352. | `geoserver://catalog/layers/{workspace}/{layer}` | Get information about a specific layer |
  353. | `geoserver://services/wms/{request}` | Handle WMS resource requests |
  354. | `geoserver://services/wfs/{request}` | Handle WFS resource requests |
  355. ### ๐Ÿ“ฆ Workspace Management
  356. | Tool | Description |
  357. | :----------------- | :------------------------------------- |
  358. | `list_workspaces` | List available workspaces in GeoServer |
  359. | `create_workspace` | Create a new workspace in GeoServer |
  360. ### ๐Ÿ“ Datastore & Coveragestore Management
  361. | Tool | Description |
  362. | :---------------------- | :----------------------------------------------- |
  363. | `create_datastore` | Create a new datastore in the given workspace |
  364. | `create_featurestore` | Create a new featurestore in the given workspace |
  365. | `create_gpkg_datastore` | Create a GeoPackage (GPKG) datastore |
  366. | `create_shp_datastore` | Create an ESRI Shapefile datastore |
  367. | `create_coveragestore` | Create a new coveragestore in a workspace |
  368. | `delete_coveragestore` | Delete a coveragestore from a workspace |
  369. | `get_coveragestore` | Get details about a single coveragestore |
  370. | `get_coveragestores` | Get all coveragestores for a workspace |
  371. | `get_datastore` | Get a specific datastore by name |
  372. | `get_datastores` | List all datastores in the given workspace |
  373. ### ๐Ÿ—บ๏ธ Layer Management
  374. | Tool | Description |
  375. | :---------------- | :--------------------------------------------------------- |
  376. | `get_layer_info` | Get detailed information about a layer |
  377. | `list_layers` | List layers in GeoServer, optionally filtered by workspace |
  378. | `create_layer` | Create a new layer in GeoServer |
  379. | `delete_resource` | Delete a resource from GeoServer (generic) |
  380. ### ๐Ÿงฉ Layer Group Management
  381. | Tool | Description |
  382. | :----------------------------- | :-------------------------------------------------------------------- |
  383. | `create_layergroup` | Create a new layer group with specific layers and (optionally) styles |
  384. | `get_layergroup` | Get a layer group from a workspace |
  385. | `get_layergroups` | List all layer groups in a workspace |
  386. | `add_layer_to_layergroup` | Add a specific layer to a layer group |
  387. | `remove_layer_from_layergroup` | Remove a layer from a group |
  388. | `delete_layergroup` | Delete a layer group from a workspace |
  389. | `update_layergroup` | Update a layer group's details and configuration |
  390. ### ๐Ÿ‘ฅ User & User Group Management
  391. | Tool | Description |
  392. | :------------------- | :--------------------------------------- |
  393. | `create_user` | Create a new user for GeoServer security |
  394. | `delete_user` | Delete a user by name |
  395. | `get_all_users` | List all users in the GeoServer instance |
  396. | `modify_user` | Modify an existing user's properties |
  397. | `create_usergroup` | Create a new user group |
  398. | `delete_usergroup` | Delete a user group |
  399. | `get_all_usergroups` | Return all user groups |
  400. ### ๐Ÿ“Š Feature Type & Attribute Management
  401. | Tool | Description |
  402. | :----------------------------- | :-------------------------------------------------- |
  403. | `query_features` | Query features from a vector layer using CQL filter |
  404. | `publish_featurestore` | Publish an existing featurestore |
  405. | `publish_featurestore_sqlview` | Publish a featurestore using a SQL view definition |
  406. | `edit_featuretype` | Edit the settings of a feature type in a store |
  407. | `get_featuretypes` | List all feature types in a given store |
  408. | `get_feature_attribute` | Get feature attribute schema/details |
  409. ### ๐ŸŽจ Style Management
  410. | Tool | Description |
  411. | :-------------------------------- | :---------------------------------------------- |
  412. | `create_style` | Create a new SLD style in GeoServer |
  413. | `publish_style` | Assign/publish a style to a layer |
  414. | `create_catagorized_featurestyle` | Create a categorized style for features |
  415. | `create_classified_featurestyle` | Create a classified style for features |
  416. | `create_coveragestyle` | Create a raster coverage style |
  417. | `create_outline_featurestyle` | Create a simple outline-only style for features |
  418. ### โš™๏ธ System & Service Operations
  419. | Tool | Description |
  420. | :---------------------------------------- | :-------------------------------------------------------------------- |
  421. | `get_manifest` | Get GeoServer manifest metadata/details |
  422. | `get_status` | Obtain general server status |
  423. | `get_system_status` | Get system status overview/info from GeoServer |
  424. | `get_version` | Fetch GeoServer version string |
  425. | `reload_geoserver` | Reload catalog and config from disk |
  426. | `reset_geoserver` | Reset all GeoServer caches/connections |
  427. | `update_service` | Update selected OGC service options |
  428. | `publish_time_dimension_to_coveragestore` | Add or update a time dimension for a coverage store (for time series) |
  429. ### ๐Ÿ“ Style XML Utilities
  430. | Tool | Description |
  431. | :----------------------------------- | :---------------------------------------- |
  432. | `style_catagorize_xml` | Generate SLD for categorized vector style |
  433. | `style_classified_xml` | Get SLD XML for classified vector style |
  434. | `style_coverage_style_colormapentry` | Generate color map entries for raster SLD |
  435. | `style_coverage_style_xml` | Generate XML for raster/coverage SLD |
  436. | `style_outline_only_xml` | XML for outline-only style for a geometry |
  437. ## ๐Ÿ› ๏ธ Client Development
  438. If you're planning to develop your own client to interact with the GeoServer MCP server, you can find inspiration in the example client implementation at `examples/client.py`. This example demonstrates:
  439. - How to establish a connection with the MCP server
  440. - How to send requests and handle responses
  441. - Basic error handling and connection management
  442. - Example usage of various tools and operations
  443. The example client serves as a good starting point for understanding the protocol and implementing your own client applications.
  444. Also, here is the example usgage:
  445. ### List Workspaces
  446. ```
  447. Tool: list_workspaces
  448. Parameters: {}
  449. Response: ["default", "demo", "topp", "tiger", "sf"]
  450. ```
  451. ### Get Layer Information
  452. ```
  453. Tool: get_layer_info
  454. Parameters: {
  455. "workspace": "topp",
  456. "layer": "states"
  457. }
  458. ```
  459. ### Query Features
  460. ```
  461. Tool: query_features
  462. Parameters: {
  463. "workspace": "topp",
  464. "layer": "states",
  465. "filter": "PERSONS > 10000000",
  466. "properties": ["STATE_NAME", "PERSONS"]
  467. }
  468. ```
  469. ### Generate Map
  470. ```
  471. Tool: generate_map
  472. Parameters: {
  473. "layers": ["topp:states"],
  474. "styles": ["population"],
  475. "bbox": [-124.73, 24.96, -66.97, 49.37],
  476. "width": 800,
  477. "height": 600,
  478. "format": "png"
  479. }
  480. ```
  481. ## ๐Ÿ”ฎ Planned Features
  482. - [ ] Coverage and raster data management
  483. - [ ] Security and access control
  484. - [ ] Advanced styling capabilities
  485. - [ ] WPS processing operations
  486. - [ ] GeoWebCache integration
  487. ## ๐Ÿค Contributing
  488. We welcome contributions! Here's how you can help:
  489. 1. Fork the repository
  490. 2. Create a feature branch (`git checkout -b feature/AmazingFeature`)
  491. 3. Commit your changes (`git commit -m 'Add some AmazingFeature'`)
  492. 4. Push to the branch (`git push origin feature/AmazingFeature`)
  493. 5. Open a Pull Request
  494. Please ensure your PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
  495. ## ๐Ÿ“„ License
  496. This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
  497. ## ๐Ÿ”— Related Projects
  498. - [Model Context Protocol](https://github.com/modelcontextprotocol/python-sdk) - The core MCP implementation
  499. - [GeoServer REST API](https://docs.geoserver.org/latest/en/user/rest/index.html) - Official GeoServer REST documentation
  500. - [GeoServer REST Python Client](https://github.com/gicait/geoserver-rest) - Python client for GeoServer REST API
  501. ## ๐ŸŒ See Also: GIS MCP
  502. For broader geospatial data automation and even more GIS-related MCP features, see [GIS MCP by mahdin75](https://github.com/mahdin75/gis-mcp).
  503. ## ๐Ÿ“ž Support
  504. For support, please Open an [issue](https://github.com/mahdin75/geoserver-mcp/issues)
  505. ## ๐Ÿ† Badges
  506. <div align="center">
  507. <a href="https://glama.ai/mcp/servers/@mahdin75/geoserver-mcp">
  508. <img width="380" height="200" src="https://glama.ai/mcp/servers/@mahdin75/geoserver-mcp/badge" alt="GeoServer Server MCP server" />
  509. </a>
  510. <br/><br/><br/>
  511. <a href="https://mcp.so/server/Geoserver%20MCP%20Server/mahdin75">
  512. <img src="https://mcp.so/logo.png" alt="MCP.so Badge" width="150"/>
  513. </a>
  514. <br/><br/><br/>
  515. [![MseeP.ai Security Assessment Badge](https://mseep.net/pr/mahdin75-geoserver-mcp-badge.png)](https://mseep.ai/app/mahdin75-geoserver-mcp)
  516. </div>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If itโ€™s helped, pass it on.