MCP servers · atlasent

AtlaSent MCP Server

MCP server that asks AtlaSent to authorize an AI agent's consequential tool calls before they change a real system.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

The server adds an authorize-before-execute step to any MCP-compatible AI agent. Before a tool call such as a production deploy, a data export or an access grant runs, the agent asks AtlaSent for a decision. With an API key (remote mode), risky actions wait for a person to approve them, other actions run normally, and each decision gets a signed record that names the approver when an approval was relied on. The server also exposes AtlaSent's authorization functions as MCP tools that an agent can call.

It suits teams that connect agents such as Claude, Cursor or Windsurf to systems where an action cannot easily be undone. Local mode uses built-in rules: production actions without approvals are denied, destructive actions outside a change window are held, and sign, grant, export and publish actions are held or denied. Local permits are unsigned, so this mode is intended for development, CI and trying things out.

Local mode runs with npx and needs no account or API key. Remote mode needs an API key and a short configuration entry in the MCP host. The repository also offers source and Docker runs, and a Claude Code plugin that holds or refuses destructive commands without an account.

Limitations and requirements

Local mode is a credential-free demo that protects nothing, and its default rule allows action types it does not recognise. Local permits are unsigned and the server refuses to fall back to local mode when NODE_ENV=production, so it is not a production enforcement boundary. Signed records, audit evidence and organization-specific policies require an AtlaSent API key. Hosted decisions, shared policies and team approvals are available on AtlaSent plans. Enterprise adoption runs through a design partner program.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    AtlaSent MCP Server

    AtlaSent for AI agents: with an API key, actions wait for approval with signed proof. No key: demo.

    v2.21.0
    As shown on registry.modelcontextprotocol.io when we last read it
  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    AtlaSent MCP Server

    Atlasent for AI agents: with an API key, actions wait for approval with signed proof. No key: demo.

    v2.16.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
neondatabase

Neon MCP Server (Postgres)

Neon's MCP server for managing Neon Postgres in plain language: create projects and branches, run queries and prepare schema migrations from your editor.

663 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
supabase-community

Supabase MCP Server

Supabase's MCP server that connects an AI assistant to your Supabase project to design tables, run queries, read configuration and look up documentation.

Data & databasesSoftware development
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
modelcontextprotocol

MCP reference servers

Seven small example servers maintained by the Model Context Protocol project: files, Git, web fetching, memory, time, step-by-step thinking and a test server.

92K GitHub starsSoftware development
Updated 17 Nov 2026