Security integration · Beta

Evaluate the Abnormal Security MCP server for your MSP stack.

The Stackyapper Abnormal Security connection is available for evaluation. Beta apps may change and should begin with a small set of read-only tools.

What is the Stackyapper Abnormal Security MCP integration?

The Stackyapper Abnormal Security integration lets compatible AI clients use approved Abnormal Security tools without receiving the provider credential.

What can the Abnormal Security integration do?

Cloud email threat, investigation case, abuse-mailbox, message, and remediation-status visibility.

Available tools depend on the provider account, workspace settings, and the signed-in user’s permissions.

Who is the Abnormal Security MCP integration for?

It is for MSP teams that need approved Abnormal Security context available to an AI assistant while keeping provider authorization inside the selected Stackyapper workspace.

What is the current support status?

Status	Beta
App review	In review
What that means	Available for evaluation, may change, and should begin with read-only tools.
Catalog category	Security
Catalog audience	msp
Credential handling	An administrator supplies and manages the Abnormal Security provider credential for the selected workspace.
Customer access	MSP workspace only

Start in a test workspace with one read-only tool and a request for no more than five records.

What can an MSP use it for?

Review approved Abnormal Security context during a security workflow.
Ask an authorized AI client to summarize permitted Abnormal Security results before a human decision.
Use the Abnormal Security connection alongside another permitted business system when the workflow needs that information.

Exact tools depend on provider authorization, credential ownership, workspace settings, and the signed-in user’s permissions.

What should I expect?

Provider scope	Cloud email threat, investigation case, abuse-mailbox, message, and remediation-status visibility.
Available tools	Compatible clients see only the tools available to the signed-in user in the selected workspace.
Write actions	If a write tool is available, Stackyapper applies its permissions and confirmation requirements before it runs.
API coverage	This page lists the capabilities Stackyapper currently supports, not every endpoint in the provider API.

How is Abnormal Security access controlled?

An administrator connects Abnormal Security in the intended Stackyapper workspace.
The administrator grants available tools to specific workspaces, groups, or people.
Stackyapper resolves the connection within the current credential and tenant scope.
Stackyapper checks permissions and safety controls again before every request.
Actions that require confirmation do not execute until the exact request is confirmed.

Does Abnormal Security send its API credential to Claude or ChatGPT?

No. Stackyapper keeps the encrypted provider credential secure and does not send it to the AI client.

How do I evaluate the Abnormal Security beta?

Create or select a non-production Stackyapper workspace.
Find Abnormal Security in the app catalog and request beta access if it is not enabled.
Use the provider authorization described above with the narrowest practical permissions.
Grant only the read-only tool needed for the evaluation.
Request no more than five records, confirm the result in Audit, and expand access only when the test succeeds.

Support boundaries

Stackyapper does not claim that every endpoint in the Abnormal Security API is exposed.
Provider plan, account configuration, API scopes, and upstream availability can limit results.
Administrators are responsible for correct provider permissions and user grants.
Support status and available tools can change as provider capabilities evolve.

Abnormal Security MCP questions

Is there a Abnormal Security MCP server?

Stackyapper has a beta Abnormal Security MCP connection available for evaluation. Beta apps may change and should begin with a small set of read-only tools.

Can I connect Abnormal Security to Claude or ChatGPT?

Stackyapper has a beta Abnormal Security connection for compatible MCP clients. It is available for evaluation and may change. Exact access depends on provider authorization and Stackyapper workspace permissions.

Does Stackyapper expose every Abnormal Security API endpoint?

No. This page lists the Abnormal Security capabilities Stackyapper currently supports.

Does Abnormal Security send its credential to the AI client?

No. Stackyapper keeps the encrypted Abnormal Security credential secure and does not send it to the AI client.

Stackyapper is an independent product. Provider availability and API capabilities can change.

Evaluate the Abnormal Security beta Read the app setup guide