2,500+ MCP servers ready to use
Vinkius

IndoorAtlas (Indoor Positioning) MCP Server for Mastra AI 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools SDK

Mastra AI is a TypeScript-native agent framework built for modern web stacks. Connect IndoorAtlas (Indoor Positioning) through Vinkius and Mastra agents discover all tools automatically. type-safe, streaming-ready, and deployable anywhere Node.js runs.

Vinkius supports streamable HTTP and SSE.

typescript
import { Agent } from "@mastra/core/agent";
import { createMCPClient } from "@mastra/mcp";
import { openai } from "@ai-sdk/openai";

async function main() {
  // Your Vinkius token. get it at cloud.vinkius.com
  const mcpClient = await createMCPClient({
    servers: {
      "indooratlas-indoor-positioning": {
        url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
      },
    },
  });

  const tools = await mcpClient.getTools();
  const agent = new Agent({
    name: "IndoorAtlas (Indoor Positioning) Agent",
    instructions:
      "You help users interact with IndoorAtlas (Indoor Positioning) " +
      "using 10 tools.",
    model: openai("gpt-4o"),
    tools,
  });

  const result = await agent.generate(
    "What can I do with IndoorAtlas (Indoor Positioning)?"
  );
  console.log(result.text);
}

main();
IndoorAtlas (Indoor Positioning)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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.

Mastra's agent abstraction provides a clean separation between LLM logic and IndoorAtlas (Indoor Positioning) tool infrastructure. Connect 10 tools through Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution. deployable to any Node.js host in one command.

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 Mastra AI 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 Mastra AI via MCP

Follow these steps to integrate the IndoorAtlas (Indoor Positioning) MCP Server with Mastra AI.

01

Install dependencies

Run npm install @mastra/core @mastra/mcp @ai-sdk/openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.ts and run with npx tsx agent.ts

04

Explore tools

Mastra discovers 10 tools from IndoorAtlas (Indoor Positioning) via MCP

Why Use Mastra AI with the IndoorAtlas (Indoor Positioning) MCP Server

Mastra AI provides unique advantages when paired with IndoorAtlas (Indoor Positioning) through the Model Context Protocol.

01

Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure. add IndoorAtlas (Indoor Positioning) without touching business code

02

Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation

03

TypeScript-native: full type inference for every IndoorAtlas (Indoor Positioning) tool response with IDE autocomplete and compile-time checks

04

One-command deployment to any Node.js host. Vercel, Railway, Fly.io, or your own infrastructure

IndoorAtlas (Indoor Positioning) + Mastra AI Use Cases

Practical scenarios where Mastra AI combined with the IndoorAtlas (Indoor Positioning) MCP Server delivers measurable value.

01

Automated workflows: build multi-step agents that query IndoorAtlas (Indoor Positioning), process results, and trigger downstream actions in a typed pipeline

02

SaaS integrations: embed IndoorAtlas (Indoor Positioning) as a first-class tool in your product's AI features with Mastra's clean agent API

03

Background jobs: schedule Mastra agents to query IndoorAtlas (Indoor Positioning) on a cron and store results in your database automatically

04

Multi-agent systems: create specialist agents that collaborate using IndoorAtlas (Indoor Positioning) tools alongside other MCP servers

IndoorAtlas (Indoor Positioning) MCP Tools for Mastra AI (10)

These 10 tools become available when you connect IndoorAtlas (Indoor Positioning) to Mastra AI via MCP:

01

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

02

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

03

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

04

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

05

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

06

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

07

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

08

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

09

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

10

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 Mastra AI

Ready-to-use prompts you can give your Mastra AI agent to start working with IndoorAtlas (Indoor Positioning) immediately.

01

"List all indoor venues in my IndoorAtlas account"

02

"Check the calibration paths for the 3rd floor of the 'Retail Mall'"

03

"List the most recent positioning sessions recorded today"

Troubleshooting IndoorAtlas (Indoor Positioning) MCP Server with Mastra AI

Common issues when connecting IndoorAtlas (Indoor Positioning) to Mastra AI through the Vinkius, and how to resolve them.

01

createMCPClient not exported

Install: npm install @mastra/mcp

IndoorAtlas (Indoor Positioning) + Mastra AI FAQ

Common questions about integrating IndoorAtlas (Indoor Positioning) MCP Server with Mastra AI.

01

How does Mastra AI connect to MCP servers?

Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
02

Can Mastra agents use tools from multiple servers?

Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
03

Does Mastra support workflow orchestration?

Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.

Connect IndoorAtlas (Indoor Positioning) to Mastra AI

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.