metashape-mcp
Provides a Model Context Protocol (MCP) server embedded in Agisoft Metashape Professional (2.3+) to expose the full photogrammetry workflow—alignment, dense cloud, mesh, texture, DEM, orthomosaic, export, and network processing—as AI-callable MCP tools. Includes an optional stdio proxy for long-running operations and a local HTTP transport endpoint.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security posture is largely dependent on local-only access (127.0.0.1) and host environment isolation; no auth/authz or scope model is described. Tooling includes an 'execute_python' capability, which can be dangerous if misused by an agent. TLS details are not specified; the transport is HTTP to localhost by default, so enforce additional network controls if exposure is possible. Dependency hygiene is based only on declared dependencies (mcp[cli], fastmcp) and cannot be confirmed for vulnerabilities from provided data.
⚡ Reliability
Best When
You want an AI agent to drive Metashape end-to-end via MCP on a local machine (or controlled environment) where long-running tool calls must not be cut off by typical client HTTP timeouts.
Avoid When
When you cannot trust the agent/client code to invoke expensive operations (dense/mesh/texturing), or when network exposure beyond localhost is required without additional security controls.
Use Cases
- • Drone aerial survey processing (alignment → dense cloud → DEM → orthomosaic)
- • Close-range 3D reconstruction (mesh/texture → export)
- • Survey-grade workflows using GCPs and coded markers
- • Batch exporting multiple deliverables from completed projects
- • Remote/headless photogrammetry automation on servers/VMs/CI
Not For
- • Interactive artistic use where manual GUI workflows are preferred over automation
- • Environments where Metashape must not be controlled programmatically or where running embedded Python is disallowed
- • Use cases requiring multi-tenant access control (no explicit per-user auth described)
Interface
Authentication
No authentication/authorization mechanism is described in the provided README. The server is advertised as listening on localhost (127.0.0.1); security would rely on network isolation and the client/host environment.
Pricing
No pricing information found; project is MIT licensed and appears to be a self-hosted integration (requires Agisoft Metashape license).
Agent Metadata
Known Gotchas
- ⚠ Long-running photogrammetry operations can exceed typical MCP-over-HTTP/client timeouts; README recommends using the provided stdio proxy with no timeout limits.
- ⚠ Server is intended to run embedded inside Metashape; operations assume Metashape environment state (projects/chunks) is set up correctly before tool calls.
- ⚠ Runs on a selected port; multiple sessions require per-session port coordination to avoid collisions.
- ⚠ The 'execute_python' / arbitrary scripting capability increases risk if the agent prompts are not tightly controlled.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for metashape-mcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.