developer-toolsapi_key

Mapulus

Mapulus is a platform that enables users to create, manage, and analyze interactive maps, integrating with various applications to automate tasks and leverage location insights.

Verdict

Mapulus MCP lets your team query and manage location data from Mapulus maps without leaving Switchy. @mention it to list maps, retrieve location details by external ID, or pull metadata for a specific map. Useful for teams building location-aware features, managing field operations, or analyzing spatial datasets. The MCP exposes read-only tools — you can query locations and maps but not create or update them. Best for product managers validating location coverage, developers debugging integrations, or ops teams auditing map configurations.

Common use cases

  • Validate location coverage before a feature launch
  • Debug missing map data during integration work
  • Audit map configurations across multiple projects
  • Cross-reference external IDs with location metadata
  • Generate location reports for field operations

Integration

Vendor
Mapulus
Category
developer-tools
Auth
API_KEY
Tools
4
Composio slug
mapulus

Tools

  • Find Location by External ID

    Tool to retrieve locations by external id. use after obtaining an external identifier to find the matching location(s).

  • Get Map Details

    Tool to retrieve detailed information about a map. use when you have a map id and need full map metadata.

  • List Locations

    Tool to list all locations. use after authentication to retrieve a paginated list of locations.

  • List Maps

    Tool to list all maps accessible to the user. use after authentication to retrieve maps with pagination and optional filtering.

Setup

Setup guide

  1. 11. In Switchy, open Settings and navigate to Integrations. 2. Find Mapulus in the MCP catalog and click Connect. 3. You'll be prompted to enter your Mapulus API key — generate one from your Mapulus account dashboard under API Settings. 4. Paste the key into Switchy and click Authorize. 5. Switchy confirms the connection and shows which maps your key can access. 6. Open any Space and type '@Mapulus list maps' to verify the integration works. 7. If you see your maps returned, the setup is complete. 8. To test location queries, grab an external ID from one of your maps and run '@Mapulus find location by external id [your-id]'. 9. The MCP responds with location details inline, ready for your next prompt.

What teammates see: by default, memories from Mapulus are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

List All Maps

@Mapulus list all maps accessible to this account and show their IDs and names in a table
Open in a Space →

Get Map Metadata

@Mapulus get detailed information for map ID [map-id] including all metadata fields and creation date
Open in a Space →

Find Location by ID

@Mapulus find the location with external ID [external-id] and return its coordinates and all associated attributes
Open in a Space →

List Recent Locations

@Mapulus list the first 20 locations and show their names, coordinates, and external IDs in a table
Open in a Space →

Compare Map Coverage

@Mapulus get details for maps [map-id-1] and [map-id-2] then compare their location counts and coverage areas
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@Mapulus list all maps in my account and show me which ones were updated in the last 30 days

Output

Found 12 maps in your Mapulus account. 3 were updated in the last 30 days: 'Store Locations Q1 2024' (updated 8 days ago, 47 locations), 'Distribution Centers' (updated 12 days ago, 8 locations), and 'Sales Territory Map' (updated 19 days ago, 203 locations). The remaining 9 maps have not been modified since early December. All maps are currently active and accessible.

Notes

This example demonstrates the List Maps tool combined with AI filtering logic. The MCP returns paginated map metadata; the AI parses timestamps to identify recent updates. Requires valid API_KEY authentication. Response time depends on total map count in the account.

Prompt

@Mapulus find the location with external ID 'STORE-4782' and tell me its current coordinates and address

Output

Located STORE-4782 in your Mapulus data: coordinates are 40.7489, -73.9680 (Midtown Manhattan). The registered address is 450 Lexington Avenue, New York, NY 10017. This location is tagged as 'retail-flagship' and was last updated 6 weeks ago. It appears on 2 maps: 'NYC Retail Locations' and 'East Coast Store Network'.

Notes

This example uses the Find Location by External ID tool to retrieve a specific location record. External IDs must match your account's naming convention exactly. The MCP returns raw location data; the AI formats it into readable context. Useful when syncing location data from external systems.

Prompt

@Mapulus pull all locations from the 'West Coast Warehouses' map and calculate the average distance between them

Output

Retrieved 11 locations from the 'West Coast Warehouses' map. Calculating pairwise distances: the average distance between any two warehouses is approximately 287 miles. The most isolated facility is in Spokane, WA (avg 412 miles from others). The tightest cluster is in Southern California—3 warehouses within 45 miles of each other. This suggests potential consolidation opportunities in the LA metro area.

Notes

This example chains Get Map Details and List Locations, then applies AI reasoning to compute geographic insights. The MCP provides coordinates; the AI calculates distances using haversine formulas. Useful for logistics planning, but note that straight-line distances differ from driving routes.

Use-case deep-dives

Field service dispatch coordination

When Mapulus wins for teams routing 20+ service calls daily

A 6-person field service team routing HVAC technicians across metro Atlanta uses Mapulus to sync location data between their CRM and dispatch board. The List Locations tool pulls the day's service addresses into a shared workspace, then Find Location by External ID matches each ticket to the right site when a customer calls with a follow-up. This works because the team already stores external IDs in their ticketing system—if you're starting from scratch addresses without structured location metadata, you'll spend a week cleaning data before Mapulus adds value. The API key auth means any team member can query locations without OAuth friction. Buy this if your dispatch volume justifies maintaining a location database; skip it if you're routing fewer than 15 calls a week.

Real estate portfolio tracking

Mapulus handles multi-property ops teams under 50 locations

A 3-person property management company tracking 22 rental units across two cities uses Mapulus to centralize inspection schedules and maintenance logs. The Get Map Details tool surfaces property clusters by neighborhood, and List Maps lets the team filter by acquisition year when planning capital improvements. Each property's external ID links back to their accounting system, so Find Location by External ID bridges financial records to physical sites during month-end close. This setup breaks down past 50 properties—pagination through List Locations gets slow, and the 4-tool limit means no bulk update or geocoding features. If your portfolio is growing fast or you need address validation, you'll outgrow this MCP in six months. It's ideal for stable portfolios where location lookup speed matters more than advanced spatial analysis.

Retail site selection research

When Mapulus supports early-stage location scouting

A 2-person retail startup evaluating 8 potential storefront locations uses Mapulus to organize site visit notes and demographic overlays. The List Maps tool groups candidate sites by metro area, and Get Map Details pulls traffic counts and zoning data the team manually entered during initial research. Find Location by External ID ties each site back to the commercial real estate listing ID, so the team can cross-reference lease terms without switching tools. This works for early-stage research with under 20 sites—beyond that, the lack of bulk import or automated geocoding becomes a bottleneck. If you're comparing 50+ locations or need drive-time analysis, you need a full GIS platform. Buy Mapulus if you're in the scrappy research phase and want lightweight location tracking without enterprise spatial software.

Frequently asked

What does the Mapulus MCP do in Switchy?

It lets your AI agents query and retrieve location data from your Mapulus account. The MCP can list maps, fetch map metadata, browse all locations, and look up specific locations by external ID. Think of it as giving your team's AI direct read access to your Mapulus spatial database without writing API calls.

Do I need admin access to connect Mapulus?

You need a Mapulus API key with read permissions on the maps and locations you want the AI to access. Mapulus uses API key authentication, so whoever generates the key controls which data the MCP can see. If your Mapulus account restricts API key creation to admins, yes—you'll need admin help.

Can the Mapulus MCP create or edit locations?

No. The four tools are read-only: list maps, get map details, list locations, find location by external ID. If your AI needs to write data back to Mapulus, you'll need to use Mapulus's REST API directly or build a custom integration.

Why use this instead of calling the Mapulus API myself?

The MCP wraps Mapulus's API so your AI can query location data in natural language without you writing fetch logic or managing tokens per request. If you're already piping Mapulus data into your app via API, this won't replace that—it's for ad-hoc AI queries, not production data pipelines.

Who on my team should connect the Mapulus MCP?

Whoever owns your Mapulus API keys and understands which maps contain sensitive location data. Once connected in Switchy, any team member in that workspace can ask the AI to query those maps, so treat the connection like you would sharing a read-only database credential.

Data last verified 607 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.