list_users
List Users
Retrieve a bounded page of users for a team or organization. Returns user profiles including name, email, and last login information.
Ask your agent in plain language. Each of these maps to a real tool on the server.
list_users
Retrieve a bounded page of users for a team or organization. Returns user profiles including name, email, and last login information.
manage_connection
Get details, rename, verify, or delete a connection. Use "verify" to test whether stored credentials are still valid with the external service.
list_teams
Retrieve a bounded page of teams belonging to an organization. Teams are the primary container for scenarios, connections, and other Make resources.
list_organizations
Retrieve a bounded page of organizations that the authenticated user is a member of. Returns organization IDs, names, and zone information.
manage_scenario
Get details, update, activate, deactivate, run, clone, or delete an automation scenario. Run is asynchronous and can cause external effects or charges; activation can immediately execute interval schedules. Clone requires target organization, team, name, and an explicit module-state choice. Delete can retain a recoverable trash entry and history.
get_scenario_logs
Retrieve execution logs for a specific scenario. Shows recent execution history including timestamps, statuses, and operations consumed. Useful for debugging and monitoring scenario performance.
manage_data_store_records
List, get, create, update, or delete records within a Make data store. Get performs an exact-key scan capped at 1000 records and refuses incomplete absence. Update replaces the entire record. Delete acknowledges the exact native key receipt.
list_data_stores
Retrieve a bounded page of data stores for a team. Data stores persist structured data across scenario executions and enable data sharing between scenarios.
list_scenarios
Retrieve a list of automation scenarios from Make. Filter by team, organization, folder, or active status. Returns scenario names, IDs, scheduling details, and current state.
manage_hook
Get details, create, rename, enable, disable, ping, or delete a webhook (hook). Use "ping" to read native gone/attached/learning metadata without sending a payload. Use "enable"/"disable" to control whether the hook accepts incoming data.
create_scenario
Create a new automation scenario in a Make team. Provide blueprint JSON text and an explicit scheduling object. These legacy optional fields are required at runtime by the native API. Creation does not confirm activation or execution.
list_hooks
Retrieve a bounded page of webhooks (hooks) for a team. Hooks are incoming trigger endpoints that receive data from external services and can initiate scenario executions. Filter by type or assignment status.
get_usage
Retrieve usage statistics for an organization or team. Returns daily operations count, data transfer, and centicredits usage for the past 30 days.
list_connections
Retrieve a bounded page of connections for a given team. Connections represent authenticated links to external services used in scenarios.
manage_data_store
Get details, create, update, or delete a data store. Data stores persist structured data between scenario runs and enable data sharing across scenarios.
get_execution_status
Read native status and available outputs for one existing scenario execution. RUNNING or PAUSED is incomplete; reading does not resume, stop, or resend an execution. Prior external effects and charges remain.
list_data_structures
Discover native data structure IDs and field specifications for a team. Use these IDs with manage_data_store. Requires udts:read; call list_organizations then list_teams first.
get_current_user
Read the native connected Make user in the saved region. Does not infer an identity from a token or return organizations from another region.
download_blueprint
Prepare a bounded JSON file containing the existing scenario blueprint. This reads configuration only and does not export the whole organization, run a scenario, or generate a new blueprint. The file can contain private workflow configuration.
Every client uses the same Magic MCP URL, and so does any other MCP client. Add it once and sign in with SSO.
{"mcpServers": {"metorial": {"url": "<your-magic-mcp-url>"}}}
claude mcp add --transport http metorial <your-magic-mcp-url>
codex mcp add metorial --url <your-magic-mcp-url>codex mcp login metorial
One governed layer for every app your agents reach, not a separate connector per tool.
Manage no-code automation workflows (scenarios) on the Make platform. Create, run, activate, deactivate, clone, and delete scenarios. Manage scenario blueprints, execution logs, and consumption statistics. Create and verify app connections. Manage data stores and their records, define data structures, and handle webhooks. Organize teams, users, and organizations with role-based access. Build and manage custom app integrations via the SDK. Access analytics, audit logs, and incomplete executions for debugging. Manage AI agents, encryption keys, devices, and notification preferences.
Common questions about connecting Make to AI agents with Metorial.