Lumos MCP integration for AI agents.
Connect AI agents to Lumos through 4 structured actions, including get access request, get appstore app, and list access requests. Review authentication, inp…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Lumos integration exposes
The Lumos Agent App exposes 4 provider-backed actions for security and productivity work. Its current contract lets an authorized agent get a single lumos access request by id, get a single appstore app from lumos by app id, and list access requests in lumos with optional user and status filters. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Lumos account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Lumos capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_access_requestREADGet a single Lumos access request by ID.
INPUTS: id / expand
get_appstore_appREADGet a single AppStore app from Lumos by app ID.
INPUTS: app_id / expand
list_access_requestsREADList access requests in Lumos with optional user and status filters.
INPUTS: target_user_id / requester_user_id / user_id / statuses / sort
list_appstore_appsREADList AppStore apps in Lumos with optional search and visibility filters.
INPUTS: app_id / name_search / exact_match / all_visibilities / expand
INPUT CONTRACTS
Know what the action needs before it runs.
get_access_request
idREQUIRED- The ID of the access request to retrieve.
expandOPTIONAL- Access request fields to expand. Lumos currently supports tasks and custom_fields.
get_appstore_app
app_idREQUIRED- The ID of the AppStore app to retrieve.
expandOPTIONAL- App fields to expand. Lumos currently supports custom_attributes.
list_access_requests
target_user_idOPTIONAL- Filter requests by the ID of the target user.
requester_user_idOPTIONAL- Filter requests by the ID of the requesting user.
user_idOPTIONAL- Filter requests by the ID of the user.
statusesOPTIONAL- Filter requests by their Lumos status values.
sortOPTIONAL- Sort access requests by created date.
list_appstore_apps
app_idOPTIONAL- Filter apps by the ID of the app.
name_searchOPTIONAL- Search against name, app instance identifier, and app class ID.
exact_matchOPTIONAL- Whether the name_search filter should be an exact match.
all_visibilitiesOPTIONAL- Whether to include apps regardless of AppStore visibility. Only available to admins.
expandOPTIONAL- App fields to expand. Lumos currently supports custom_attributes.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Access Request
Get a single Lumos access request by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_access_requestVerify with Get Appstore App
Get a single AppStore app from Lumos by app ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_appstore_appSAFETY BOUNDARY
Operate Lumos with explicit limits
- Authorize Lumos with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Lumos data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Lumos rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Lumos task completed successfully.
CONNECTION MODEL
API key
Lumos API token sent as a Bearer token. Create and manage API keys in Lumos API settings: https://developers.lumos.com/docs/rest-api.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Lumos.