Hoop MCP integration for AI agents.
Connect AI agents to Hoop through 3 structured actions, including get current user, list connections, and list sessions. Review authentication, inputs, workf…
- ACTION CONTRACTS
- 3
- 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 Hoop integration exposes
The Hoop Agent App exposes 3 provider-backed actions for security and developer tools work. Its current contract lets an authorized agent get the hoop profile for the connected api key, list hoop connections with optional filters and pagination, and list hoop sessions with optional filters and pagination. 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 Hoop account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Hoop capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_userREADGet the Hoop profile for the connected API key.
list_connectionsREADList Hoop connections with optional filters and pagination.
INPUTS: agentId / tags / tagSelector / search / type
list_sessionsREADList Hoop sessions with optional filters and pagination.
INPUTS: user / connectionName / type / reviewApprover / reviewStatus
INPUT CONTRACTS
Know what the action needs before it runs.
list_connections
agentIdOPTIONAL- Filter by Hoop agent ID.
tagsOPTIONAL- Deprecated comma-separated Hoop tags filter.
tagSelectorOPTIONAL- Selector tags to filter on, such as key=value,key2!=value2.
searchOPTIONAL- Search by connection name, type, subtype, resource name, or status.
typeOPTIONAL- Filter by Hoop connection type.
list_sessions
userOPTIONAL- Filter by Hoop user subject ID.
connectionNameOPTIONAL- Filter by Hoop connection name.
typeOPTIONAL- Filter by Hoop connection type.
reviewApproverOPTIONAL- Filter by the review approver email.
reviewStatusOPTIONAL- Filter by review status.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current User
Get the Hoop profile for the connected API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_userVerify with List Connections
List Hoop connections with optional filters and pagination. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_connectionsSAFETY BOUNDARY
Operate Hoop with explicit limits
- Authorize Hoop with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Hoop 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.
- The sampled contract declares provider scopes including `userinfo:read`, `connections:read`, and `sessions:read`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Hoop task completed successfully.
CONNECTION MODEL
API key
Hoop managed API key used as a Bearer token.
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
- 3
- 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 Hoop.