Mapulus
for LuumenAI
Read your Mapulus maps and locations from the terminal
Pull location context into the work you are already doing. Ask for the maps you can reach with MAPULUS_LIST_MAPS, open one with MAPULUS_GET_MAP_DETAILS, or match a site from your own records using MAPULUS_FIND_LOCATION_WITH_EXTERNAL_ID. Read-only, over an API key. Answers come back right away.
The Mapulus toolbox
3 tools, all read-only. They answer instantly, and every call is logged.
- ReadFind Location by External IDFind locations by their external identifier.
- ReadGet Map DetailsRetrieve detailed information about a map.
- ReadList MapsRetrieves a paginated list of all maps accessible to the authenticated user.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
No. Every one of the 3 tools LuumenAI has for Mapulus is read-only, so it can answer questions from Mapulus but cannot change anything in it. Read actions still follow the configured access and approval policy, and are recorded on the audit trail.
You decide. Access is granted per agent, skill, and team, and per environment — production is not staging.
Every call to Mapulus is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Mapulus to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.