Actionlayer

io.actionlayerv0.7.1Updated Oct 9, 2026

Concierge for AI agents: takes action in the physical world — book, order, register, resolve.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an AI assistant take real-world actions such as booking, ordering, registering, and resolving tasks on the user's behalf.

What you can do
Actionlayer is described as a concierge for AI agents that takes action in the physical world, covering tasks like booking, ordering, registering, and resolving. It is offered as a remote endpoint and also as a local process, with a Python package run via uvx. The manifest does not list individual tools, so the exact operations available are not documented here.
When to use it
Consider it when an assistant needs to carry out real-world errands or transactions rather than just answer questions, for example making a booking or placing an order. It is less relevant if you only need read-only information or local developer tooling.
Requirements
An Actionlayer API key supplied as the ACTIONLAYER_API_KEY environment variable, obtained from the provider's settings page. An optional ACTIONLAYER_API_URL variable sets the API base URL. It can run as a remote endpoint or locally via the PyPI package with uvx, which needs a Python runtime and network access.
Before you install
The server is built to take action in the physical world, so operations such as booking, ordering, or registering may commit the user to real transactions or spending. It requires the ACTIONLAYER_API_KEY secret, which should be stored and shared carefully. The manifest declares no authentication details beyond that key, and no tool list is provided, so review what each action does before granting broad use.

Installation

In SourceWeft

  1. Open Actionlayer in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.actionlayer%2Factionlayer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "actionlayer": {
      "type": "http",
      "url": "https://api.actionlayer.io/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.7.1LatestSep 16, 2026

Score

15% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.