App as MCP server
Claude Desktop, VS Code, or another device can use FeatureServer, DuckDB, routing, TAK, and ImageServer tools from this phone. Token is generated in-app. Restrict tools or expose everything.
Local AI · DDIL
AI Server
Android on-device model packs with an in-process OpenAI-compatible API. No Ollama. No separately hosted sidecar.
In-app AI GeoAgent
Android. The phone owns the models. Download a pack on the device, chat locally, and call map and TAK tools, no Ollama, no cloud sidecar, and it keeps working in DDIL.
- OpenAI-compatible chat, models, and embeddings so existing clients can point at the EUD
- Gemma 3 1B for smaller phones, Qwen 2.5 1.5B for mid-range, Phi-4 mini when you have about 8 GB RAM
- Tools: query local features, export imagery and elevation, run DuckDB SQL, route, and search TAK GeoChat
- Native AI screen plus the GeoLibre WebTAK panel share the same GeoAgent
- GeoChat entity extraction so names and places in traffic become structured data on the COP
MCP Model Context Protocol
Android. From the hub: AI → MCP Servers. The app speaks MCP both ways, expose tools to a laptop agent, or let GeoAgent call extra servers.
App as MCP client
Presets for filesystem, GeoPackage/SQLite, DuckDB, fetch, and a local knowledge graph, or any remote HTTP MCP server. Offline presets stay on-device.