Action1 MCP Server

Action1 is an MCP integration. Action1 MCP server — endpoint inventory, patch visibility, and policy automation via REST API.

Packages and local setup

The published oci package is ghcr.io/wyre-technology/action1-mcp:v1.1.5. Its declared MCP transport is stdio.

The package declares ACTION1_CLIENT_ID (required): Action1 OAuth client ID; ACTION1_CLIENT_SECRET (required): Action1 OAuth client secret; ACTION1_TENANT: Action1 tenant identifier (subdomain). Provide this or ACTION1_BASE_URL.; ACTION1_BASE_URL: Action1 base URL (e.g. https://your-instance.action1.com). Provide this or ACTION1_TENANT.; MCP_TRANSPORT: Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.; AUTH_MODE: Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.; LOG_LEVEL: Log verbosity: debug, info, warn, error.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.1.5 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.