SSyncDev

Sophos Central MCP Server

The Sophos Central partner, organization and tenant APIs, routed to the right tenant and region

Local serverstdio

What is the Sophos Central MCP Server?

Sophos Central MCP is an MCP integration. The Sophos Central partner, organization and tenant APIs, routed to the right tenant and region.

Packages and local setup

The published mcpb package is https://github.com/Servosity/msp-skills/releases/download/sophos-central-v0.1.9/sophos-central-mcp.mcpb, version 0.1.9. Its declared MCP transport is stdio.

The package declares SOPHOS_CENTRAL_CLIENT_ID (required): Client ID of a Sophos Central API credential (Partner Dashboard > Settings & Policies > API Credentials, or Global Settings > API Credentials Management).; SOPHOS_CENTRAL_CLIENT_SECRET (required): Client secret of that API credential. Sophos shows it only once, when the credential is created.; SOPHOS_CENTRAL_TENANT_ID: Optional. With a partner or organization credential, the customer tenant ID that tenant-scoped tools act on. Leave blank to let the fleet tools walk every customer; tools that take a tenant argument can still pick one per call.; SOPHOS_CENTRAL_BASE_URL: Optional. Leave blank: requests go to https://api.central.sophos.com and each tenant's regional host is found automatically.; SOPHOS_CENTRAL_TOKEN_URL: Optional. Leave blank to use https://id.sophos.com/api/v2/oauth2/token.; SOPHOS_CENTRAL_OAUTH_SCOPE: Optional. Leave blank to use the scope Sophos Central documents (token).; SOPHOS_CENTRAL_MCP_READ_ONLY: Optional. Set to 1 to make the MCP server refuse every non-GET call and hide the sync and export tools. It does not replace giving the API credential a read-only role.; SOPHOS_CENTRAL_NO_LOCAL_DATA: Optional. Set to 1 to keep no local copy of API responses: reads go to the API, the response cache is off, and sync and fleet refresh refuse to run. Leave blank to keep the local store.; SOPHOS_CENTRAL_MCP_HTTP_TOKEN: Required only when running the MCP server with --transport http (a remote or hosted deployment); callers must send a matching Authorization: Bearer header. Not needed for the default local stdio transport Claude Desktop uses.; SOPHOS_CENTRAL_USER_AGENT: Optional. Overrides the User-Agent the CLI sends to Sophos Central. Leave blank to use the built-in one.; PRINTING_PRESS_CLIENT_PROFILE: Only used when the MCP server is bound to a tenant-gated client profile. This connector registers no tenant-gated source, so leave it blank..

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. This profile uses version 0.1.9 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.

Configuration

VariableDescriptionRequired
SOPHOS_CENTRAL_CLIENT_IDClient ID of a Sophos Central API credential (Partner Dashboard > Settings & Policies > API Credentials, or Global Settings > API Credentials Management).Yes
SOPHOS_CENTRAL_CLIENT_SECRETClient secret of that API credential. Sophos shows it only once, when the credential is created.Yes
SOPHOS_CENTRAL_TENANT_IDOptional. With a partner or organization credential, the customer tenant ID that tenant-scoped tools act on. Leave blank to let the fleet tools walk every customer; tools that take a tenant argument can still pick one per call.Check documentation
SOPHOS_CENTRAL_BASE_URLOptional. Leave blank: requests go to https://api.central.sophos.com and each tenant's regional host is found automatically.Check documentation
SOPHOS_CENTRAL_TOKEN_URLOptional. Leave blank to use https://id.sophos.com/api/v2/oauth2/token.Check documentation
SOPHOS_CENTRAL_OAUTH_SCOPEOptional. Leave blank to use the scope Sophos Central documents (token).Check documentation
SOPHOS_CENTRAL_MCP_READ_ONLYOptional. Set to 1 to make the MCP server refuse every non-GET call and hide the sync and export tools. It does not replace giving the API credential a read-only role.Check documentation
SOPHOS_CENTRAL_NO_LOCAL_DATAOptional. Set to 1 to keep no local copy of API responses: reads go to the API, the response cache is off, and sync and fleet refresh refuse to run. Leave blank to keep the local store.Check documentation
SOPHOS_CENTRAL_MCP_HTTP_TOKENRequired only when running the MCP server with --transport http (a remote or hosted deployment); callers must send a matching Authorization: Bearer header. Not needed for the default local stdio transport Claude Desktop uses.Check documentation
SOPHOS_CENTRAL_USER_AGENTOptional. Overrides the User-Agent the CLI sends to Sophos Central. Leave blank to use the built-in one.Check documentation
PRINTING_PRESS_CLIENT_PROFILEOnly used when the MCP server is bound to a tenant-gated client profile. This connector registers no tenant-gated source, so leave it blank.Check documentation