IndoorAtlas (Indoor Positioning) MCP Server for Claude Desktop 10 tools — connect in under 2 minutes
Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install IndoorAtlas (Indoor Positioning) and 2,500+ MCP Servers from a single visual interface.
{
"mcpServers": {
"indooratlas-indoor-positioning": {
// Your Vinkius token. get it at cloud.vinkius.com
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About IndoorAtlas (Indoor Positioning) MCP Server
Connect your IndoorAtlas account to any AI agent and take full control of your smart building infrastructure and indoor positioning services through natural conversation.
Claude Desktop is the definitive way to connect IndoorAtlas (Indoor Positioning) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
What you can do
- Venue Management — List all registered indoor venues and retrieve detailed metadata including geographic anchor points and floor counts directly from your agent
- Floorplan Orchestration — Upload new floor plans as GeoJSON and manage geo-referencing to real-world coordinates for accurate indoor positioning
- Map Generation — Trigger the radio map generation process to compute positioning models from signal fingerprint data and floor geometry
- Analytics & Sessions — Retrieve historical positioning sessions and trace data to analyze occupancy patterns, dwell times, and path optimization
- Wi-Fi Positioning — Determine indoor location from Wi-Fi scans using the Positioning API to receive estimated coordinates and floor levels
- Calibration Audit — Inspect fingerprinting walk paths to assess calibration coverage and identify areas needing additional signal mapping
The IndoorAtlas (Indoor Positioning) MCP Server exposes 10 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect IndoorAtlas (Indoor Positioning) to Claude Desktop via MCP
Follow these steps to integrate the IndoorAtlas (Indoor Positioning) MCP Server with Claude Desktop.
Open Claude Desktop Settings
Go to Settings → Developer → Edit Config to open claude_desktop_config.json
Add the MCP Server
Paste the configuration above into the mcpServers section
Restart Claude Desktop
Close and reopen Claude Desktop to load the new server
Start using IndoorAtlas (Indoor Positioning)
Look for the 🔌 icon in the chat. your 10 tools are now available
Why Use Claude Desktop with the IndoorAtlas (Indoor Positioning) MCP Server
Claude Desktop by Anthropic provides unique advantages when paired with IndoorAtlas (Indoor Positioning) through the Model Context Protocol.
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
IndoorAtlas (Indoor Positioning) + Claude Desktop Use Cases
Practical scenarios where Claude Desktop combined with the IndoorAtlas (Indoor Positioning) MCP Server delivers measurable value.
Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation
Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language
Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary
Learning and training: new team members can explore API capabilities conversationally without needing to read documentation
IndoorAtlas (Indoor Positioning) MCP Tools for Claude Desktop (10)
These 10 tools become available when you connect IndoorAtlas (Indoor Positioning) to Claude Desktop via MCP:
create_venue
The venue serves as the top-level container for floor plans and positioning data. After creation, upload floor plan images and calibrate for positioning accuracy. Create a new indoor venue in the IndoorAtlas platform by specifying the building name, geographic coordinates of the entrance, and initial configuration parameters for indoor positioning deployment
get_fingerprint_paths
Returns GeoJSON LineString features representing calibration paths. Use to assess calibration coverage and identify areas of the floor that need additional fingerprinting for better positioning accuracy. Retrieve the fingerprinting walk paths recorded for a specific floor plan as GeoJSON, showing the routes surveyors walked while collecting Wi-Fi/BLE signal data for positioning calibration
get_session_data
Returns the complete position trace as a series of timestamped fixes. Use for path visualization, behavioral analysis, and positioning quality assessment. Large sessions may contain thousands of position fixes. Retrieve the full positioning trace data for a specific IndoorAtlas session, including timestamped coordinate fixes, floor transitions, accuracy metrics, and sensor readings throughout the session duration
get_venue_details
Returns the venue configuration including coordinate reference, building dimensions, and mapping completeness metrics. Use to inspect a venue before deploying positioning or wayfinding features. Retrieve detailed metadata for a specific IndoorAtlas venue including its geographic anchor point, floor count, total mapped area, calibration status, and associated floor plan identifiers
list_floorplans
Returns an array of floor plan metadata objects ordered by floor number. Each entry includes the plan dimensions, pixel-to-meter scale, and whether radio map generation has been completed. List all floor plans uploaded to a specific IndoorAtlas venue, returning floor plan IDs, floor numbers, dimensions, geo-alignment status, and map generation readiness for each level of the building
list_positioning_sessions
Returns a paginated list of positioning sessions. Each session represents a continuous period of indoor tracking by a single device. Use for occupancy analytics, dwell time analysis, and path optimization studies. List historical indoor positioning sessions recorded by IndoorAtlas, returning session IDs, start/end times, venue associations, and device information for analytics and path replay
list_venues
Returns an array of venue objects. Each venue represents a physical building that has been set up for indoor positioning. Use to discover available venues before requesting floor plans or positioning data. List all indoor venues registered in your IndoorAtlas organization, returning venue IDs, names, geographic coordinates, and configuration status for each mapped building or facility
position_from_wifi_scan
Returns estimated coordinates with uncertainty radius. Use for server-side positioning when mobile SDK integration is not feasible. Determine indoor position from a Wi-Fi access point scan using the IndoorAtlas Positioning API, submitting observed signal strengths to receive a calculated latitude, longitude, floor level, and accuracy estimate
trigger_map_generation
This is a critical step — positioning will not work on a floor until map generation completes successfully. The process is asynchronous and may take several minutes depending on floor plan complexity. Trigger the IndoorAtlas radio map generation process for a specific floor plan, initiating the server-side computation that creates the positioning model from fingerprint data and floor plan geometry
upload_floorplan_geojson
After upload, trigger map generation to enable positioning on this floor. Upload a new floor plan to an IndoorAtlas venue as a GeoJSON document, geo-referencing the indoor map image to real-world coordinates for accurate positioning overlay
Example Prompts for IndoorAtlas (Indoor Positioning) in Claude Desktop
Ready-to-use prompts you can give your Claude Desktop agent to start working with IndoorAtlas (Indoor Positioning) immediately.
"List all indoor venues in my IndoorAtlas account"
"Check the calibration paths for the 3rd floor of the 'Retail Mall'"
"List the most recent positioning sessions recorded today"
Troubleshooting IndoorAtlas (Indoor Positioning) MCP Server with Claude Desktop
Common issues when connecting IndoorAtlas (Indoor Positioning) to Claude Desktop through the Vinkius, and how to resolve them.
Server not appearing after restart
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).Authentication error
Tools not showing in chat
IndoorAtlas (Indoor Positioning) + Claude Desktop FAQ
Common questions about integrating IndoorAtlas (Indoor Positioning) MCP Server with Claude Desktop.
How does Claude Desktop discover MCP tools?
claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.What happens if the MCP server is temporarily unavailable?
Can I connect multiple MCP servers simultaneously?
mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.Is there a limit on the number of tools per server?
Does Claude Desktop support Streamable HTTP transport?
Connect IndoorAtlas (Indoor Positioning) with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect IndoorAtlas (Indoor Positioning) to Claude Desktop
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.