Potencia tu agente
Instalación del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
Aún no hay una versión empaquetada en el registro. Sigue el README del repositorio.
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDel publicador
A Model Context Protocol (MCP) server for interacting with Esri file geodatabases (FGDB) and enterprise geodatabases (via SDE connection files) through ArcPy. This server provides tools for querying, modifying, and managing geodatabase datasets via the MCP protocol.
Version: 0.1.0
See the tutorial for more information about the Model Context Protocol.
Model Context Protocol server for Esri Databases (SDE and GDB). Enables AI assistants to interact with FGDB/SDE databases through AI Agent for data querying, modification, and schema management.
.gdb directory) or an enterprise geodatabase using a full absolute path to an SDE connection file (.sde)mcp[cli] >= 1.21.0 - Model Context Protocol server frameworkpydantic >= 2.0.0 - Data validation (installed as dependency of mcp)ArcPy is provided by ArcGIS Pro and is only available in the ArcGIS Pro conda environment. It cannot be installed via pip. See the Installation section for setup instructions.
Clone the repository:
git clone <repository-url>
cd fgdb-mcp-server
Set up ArcPy environment:
Use the ArcGIS Pro conda environment directly:
# Activate ArcGIS Pro conda environment
& "C:\Program Files\ArcGIS\Pro\bin\Python\Scripts\proenv.bat"
conda activate arcgispro-py3
# Install your project dependencies
# Note: Run your terminal with Administrator privileges
pip install -e .
Verify ArcPy availability:
try:
import arcpy
print(f"ArcPy version: {arcpy.__version__}")
print("ArcPy is available!")
except ImportError:
print("ArcPy is not available")
C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\To use this server with an MCP client, add the following configuration to your MCP client's configuration file (typically mcp.json):
{
"mcpServers": {
"fgdb-mcp-server": {
"type": "stdio",
"command": "C:\\Program Files\\ArcGIS\\Pro\\bin\\Python\\envs\\arcgispro-py3\\python.exe",
"args": [
"C:\\{path to}\\fgdb-mcp-server\\fgdb_toolserver.py"
]
}
}
}
command: Update this path to match your ArcGIS Pro Python executable locationargs: Update the path to point to your fgdb_toolserver.py file location (use full absolute path)\\) or forward slashes (/) in JSON pathsExample with custom path:
{
"mcpServers": {
"fgdb-mcp-server": {
"type": "stdio",
"command": "C:\\Program Files\\ArcGIS\\Pro\\bin\\Python\\envs\\arcgispro-py3\\python.exe",
"args": [
"C:\\your\\custom\\path\\to\\fgdb_toolserver.py"
]
}
}
}
The server runs as an MCP server using stdio transport, which allows it to be used with MCP-compatible clients.
Connect to a geodatabase (file GDB or SDE connection file):
set_database_connection(gdb_path="C:\\data\\mygeodatabase.gdb")
set_database_connection(gdb_path="C:\\Connection Files\\server.sde")
List available feature classes:
list_all_feature_classes()
Inspect domains (optional):
list_domains()
list_datasets_by_domain(domain="StatusDomain")
Query data:
select(dataset="MyFeatureClass", where="OBJECTID > 100", limit=100, page=1)
Modify data (with confirmation):
# First attempt - returns confirmation token
insert(dataset="MyFeatureClass", rows=1, fields=["Name"], values=["Test"])
# Confirm the operation
confirm_operation(token="...", endpoint="insert", request={...})
The server can be configured using environment variables:
FGDB_MAX_SELECT_LIMIT: Maximum number of records to return in a single select query (default: 50000)FGDB_LOG_FILE: Path to the log file (default: fgdb_server.log)FGDB_LOG_LEVEL: Logging level - DEBUG, INFO, WARNING, ERROR (default: INFO)FGDB_LOG_MAX_BYTES: Maximum log file size in bytes before rotation (default: 10485760 = 10MB)FGDB_LOG_BACKUP_COUNT: Number of backup log files to keep (default: 5)FGDB_API_VERSION: Current API version (default: v1)FGDB_SUPPORTED_VERSIONS: Comma-separated list of supported API versions (default: v1)FGDB_FEATURE_EXPERIMENTAL: Enable experimental features (default: false)Note: Mutating operations (insert, update, delete, add_field, delete_field) do not use feature flags. They are controlled by the safety confirmation system, which requires explicit user confirmation for each operation.
# Database settings
$env:FGDB_MAX_SELECT_LIMIT = "20000"
# Logging settings
$env:FGDB_LOG_LEVEL = "DEBUG"
$env:FGDB_LOG_FILE = "logs/fgdb_server.log"
# API versioning
$env:FGDB_API_VERSION = "v1"
$env:FGDB_SUPPORTED_VERSIONS = "v1"
# Feature flags - experimental features (optional)
$env:FGDB_FEATURE_EXPERIMENTAL = "false"
This server currently supports API Version 1 (v1). All endpoints are part of the v1 API.
Note: Product version (0.1.0) and API version (v1) are independent:
The API version can be configured via environment variables:
# Set the default API version (default: v1)
$env:FGDB_API_VERSION = "v1"
# Specify supported API versions (comma-separated, default: v1)
$env:FGDB_SUPPORTED_VERSIONS = "v1"
The server supports feature flags for experimental features. Mutating operations (insert, update, delete, add_field, delete_field) do not use feature flags - they are controlled by the safety confirmation system, which requires explicit user confirmation for each operation.
Mutating operations are protected by the safety confirmation system:
Feature flags can be set via environment variables:
# Enable experimental features (if any)
$env:FGDB_FEATURE_EXPERIMENTAL = "true"
The server provides 13 MCP tools for geodatabase operations:
All endpoints below are part of the v1 API:
set_database_connection (v1): Establishes a connection using a full absolute path to either a file geodatabase (directory ending in .gdb) or an SDE connection file (file ending in .sde). ArcPy uses that path as the workspace.list_all_feature_classes (v1): Lists all feature classes available in the connected geodatabasedescribe (v1): Returns metadata and schema information for a specified dataset (feature class or table)count (v1): Returns the total number of records in a specified datasetlist_domains (v1): Lists all domains in the connected geodatabase with details (name, type, coded values or numeric range)list_datasets_by_domain (v1): Lists feature classes and tables (including inside feature datasets) that have at least one field assigned the given domain; returns dataset paths and matching field namesselect (v1): Queries records from a dataset with optional filtering, field selection, and pagination support
insert (v1): Inserts new records into a dataset (requires confirmation for medium-risk operations)update (v1): Updates existing records based on WHERE clause (requires confirmation for medium-risk operations)delete (v1): Deletes records from a dataset based on WHERE clause (requires confirmation for high-risk operations)add_field (v1): Adds a new field to a dataset schema (requires confirmation for medium-risk operations)delete_field (v1): Deletes a field from a dataset schema (requires confirmation for high-risk operations)confirm_operation (v1): Confirms and executes pending high-risk or medium-risk operations using a confirmation tokenThe server implements a safety system that requires confirmation for medium and high-risk operations:
When a confirmation is required, the operation returns a confirmation token that must be used with the confirm_operation tool to execute the operation.
The server uses standardized exception handling:
DatabaseConnectionError: Database connection issuesOperationBlockedError: Operations blocked by safety checksValidationError: Input validation failuresArcPyError: ArcPy-related errorsConfigurationError: Configuration errorsAll errors are logged and returned with descriptive messages.
The server provides comprehensive logging:
fgdb_server.log (configurable)Logs include:
We welcome contributions from the open source community! This project is designed to be extensible and maintainable.
fgdb-mcp-server/
├── fgdb_toolserver.py # Main MCP server and tool definitions
├── fgdb_mcp_server/ # Package directory
│ └── __init__.py # Package initialization and main entry point
├── gdb_ops/
│ ├── __init__.py
│ ├── gdb.py # FileGDBBackend - ArcPy operations
│ └── gdb_tools.py # GDBTools - Business logic layer
├── utils/
│ ├── __init__.py
│ ├── config.py # Configuration management
│ ├── exceptions.py # Custom exception classes
│ ├── safety.py # Safety manager for confirmation workflow
│ ├── utility.py # Utility functions
│ └── validation.py # Input validation utilities
├── dtos/
│ ├── __init__.py
│ └── requestobjects.py # Data transfer objects
├── tests/ # Test suite
│ ├── conftest.py # Pytest configuration
│ ├── test_*.py # Unit and integration tests
│ └── README.md # Test documentation
├── pyproject.toml # Project configuration and dependencies
├── LICENSE
├── SECURITY.md
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
└── README.md
The server follows a layered architecture:
fgdb_toolserver.py): Tool definitions and MCP protocol handlinggdb_tools.py): Operation orchestration and safety checksgdb.py): ArcPy operations and geodatabase accessutils/): Configuration, exceptions, and safety managementThis separation of concerns makes the codebase maintainable and testable.
Please report bugs, request features, or ask questions by opening an issue on GitHub. Include:
This project is licensed under the MIT License.
Copyright (c) 2025 Boustead Geospatial Technologies
See the LICENSE file for the full license text.
For questions, issues, or contributions, please use the GitHub issue tracker.
Model Context Protocol server for Esri Databases (SDE and GDB). Enables AI assistants to interact with FGDB/SDE databases through AI Agent for data querying, modification, and schema management.
Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
Fgdb se ejecuta localmente por stdio.
Última comprobación: 2026-11-05. Model Context Protocol server for Esri Databases (SDE and GDB). Enables AI assistants to interact with FGDB/SDE databases through AI Agent for data querying, modification, and schema management.
