7shifts MCP integration for AI agents.
Connect AI agents to 7shifts through 7 structured actions, including get company, list companies, and list departments. Review authentication, inputs, workfl…
- ACTION CONTRACTS
- 7
- 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 7shifts integration exposes
The 7shifts Agent App exposes 7 provider-backed actions for productivity work. Its current contract lets an authorized agent retrieve one 7shifts company by id, list 7shifts companies available to the access token, and list 7shifts departments for a company. 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 7shifts account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real 7shifts capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_companyREADRetrieve one 7shifts company by ID.
INPUTS: apiVersion / companyGuid / id
list_companiesREADList 7shifts companies available to the access token.
INPUTS: apiVersion / companyGuid / modified_since
list_departmentsREADList 7shifts departments for a company.
INPUTS: apiVersion / companyGuid / company_id / modified_since / location_id
list_locationsREADList 7shifts locations for a company.
INPUTS: apiVersion / companyGuid / company_id / modified_since / deleted
list_rolesREADList 7shifts roles for a company.
INPUTS: apiVersion / companyGuid / company_id / location_id / department_id
list_usersREADList 7shifts users for a company.
INPUTS: apiVersion / companyGuid / company_id / modified_since / location_id
retrieve_identityREADRetrieve the 7shifts identity associated with the access token.
INPUTS: apiVersion / companyGuid
INPUT CONTRACTS
Know what the action needs before it runs.
get_company
apiVersionOPTIONAL- The 7shifts API version to send as x-api-version.
companyGuidOPTIONAL- The 7shifts company GUID to send as x-company-guid.
idREQUIRED- The 7shifts company ID.
list_companies
apiVersionOPTIONAL- The 7shifts API version to send as x-api-version.
companyGuidOPTIONAL- The 7shifts company GUID to send as x-company-guid.
modified_sinceOPTIONAL- A date in YYYY-MM-DD format.
list_departments
apiVersionOPTIONAL- The 7shifts API version to send as x-api-version.
companyGuidOPTIONAL- The 7shifts company GUID to send as x-company-guid.
company_idREQUIRED- The 7shifts company ID.
modified_sinceOPTIONAL- A date in YYYY-MM-DD format.
location_idOPTIONAL- The 7shifts location ID.
list_locations
apiVersionOPTIONAL- The 7shifts API version to send as x-api-version.
companyGuidOPTIONAL- The 7shifts company GUID to send as x-company-guid.
company_idREQUIRED- The 7shifts company ID.
modified_sinceOPTIONAL- A date in YYYY-MM-DD format.
deletedOPTIONAL- Whether to include deleted locations.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Company
Retrieve one 7shifts company 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_companyVerify with List Companies
List 7shifts companies available to the access token. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_companiesSAFETY BOUNDARY
Operate 7shifts with explicit limits
- Authorize 7shifts with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned 7shifts 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 7shifts rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the 7shifts task completed successfully.
CONNECTION MODEL
API key
7shifts long-lived access token sent with the Authorization: Bearer header. Create or view access tokens in Company Settings > Developer Tools, as described in the 7shifts authentication docs: https://developers.7shifts.com/reference/authentication.
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
- 7
- 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 7shifts.