ActAs

Your agent, connected.

ActAs keeps an agent’s identity and resources independent of the model running it.

Create an identity

Sign into your workspace and subscribe to Pro; creating identities, inboxes, accounts and connections requires an active subscription. Then create an agent, and choose its owner and optional product. Create its email address in the Email tab. Accounts, encrypted credentials and the inbox belong to that identity. Existing resources are not automatically migrated.

Connect the CLI

Requires Node.js 22 or newer. Download the CLI package and install it:

npm install -g ./actas-cli.tgz

Open the agent’s Connection tab, choose permissions and resources, then download the private connection file.

actas connect ./actas-identity.json

actas identity
actas resources

The connection token is stored locally. Delete the downloaded copy after importing it. Revoke the client in Access to disable that connection.

Connect an MCP client

Remote: no install

Add https://actas.dev/mcp as a Streamable HTTP server in a client that supports bearer headers. Use the token from your scoped ActAs connection in the Authorization bearer header, saved through the client’s protected credential settings. Never put the token in a URL or prompt. OAuth is not offered.

The remote endpoint shares the 19 stdio tools and checks current API grants on every call. Browser steps, private verification handles and local executable consumers require the local runtime.

Stored passwords and TOTP codes are withheld unless you explicitly configure ActAs-MCP-Secret-Output: allow. Hosted clients may retain secret tool results in chat history. Management tokens additionally require ActAs-MCP-Management: allow. Prefer a narrowly scoped identity connection. Read the security and setup details.

Local stdio client

Install from npm with npx -y actas@0.4.0 mcp, or use the actas-mcp alias. Read the MIT client source.

Use ActAs from Claude Desktop, Cursor or another stdio MCP client. The client is MIT licensed. Read the plain-text quickstart or download the configuration template.

Download the ActAs MCP package. Requires Node.js 22 or newer and an active Pro subscription.

npm install -g ./actas-mcp.tgz

Or use the published package with npx, without a global install. Add this to your client’s MCP settings and replace the connection path with the absolute path to your private identity connection:

{
  "mcpServers": {
    "actas": {
      "command": "npx",
      "args": [
        "-y",
        "actas@0.4.0",
        "mcp"
      ],
      "env": {
        "ACTAS_CONNECTION_FILE": "/absolute/path/to/actas-identity.json"
      }
    }
  }
}

Grant only the resources the agent needs. Some tools return sensitive credentials or codes to the authorized agent. Keep the connection out of prompts, URLs and source control; revoke it in Access to stop future requests.

Prepare signup or login

In the agent’s Accounts tab, choose Add account. Enter the exact website origin and a page that requires login, then select the agent’s inbox. For a new account, ActAs generates and stores a password. For an existing account, choose login and provide its existing password.

Download the account connection and import it separately from the identity connection:

actas configure ./actas-account.json
actas signup https://example.com/signup
actas login https://example.com/login

Your browser agent follows the returned steps and reports what the website actually shows. ActAs supplies the assigned credentials through a protected local helper, keeping their values out of model context during browser transfer. The account connection grants access only to that account, credential and inbox. Delete the downloaded copy after importing it.

A pending account record is preparation, not registration. Read verification mail in the assigned inbox; automatic extraction requires an explicit sender and link or code rule. Resume with the same operation and account mapping, and reconcile uncertain submissions before retrying. Unsupported challenges remain pending.

Use workspace secrets

Open Secrets to see your workspace’s keys by folder. Add a key such as /topagent/x/API_KEY, then give an agent folder access. A folder grant includes its subfolders and future keys. The agent’s connection must also permit the chosen actions.

actas secret list --path /topagent
actas secret set /topagent/x/API_KEY
actas run --path /topagent/x --keys API_KEY -- your-command

Secret values belong at the private Terminal prompt. ActAs delivers selected values directly to the command’s environment. Revealing or copying a value in the web app requires the workspace owner and is recorded in Activity.

To give folder access from an owner connection:

actas grant add identity:AGENT_ID /topagent read --folder
actas grant add identity:AGENT_ID /topagent reveal --folder

Folder access and connection permissions both apply. Disconnect an agent’s connection to stop its access. Use Settings for workspace management connections.

Send email

Enable “Can send email” on the agent’s Inbox page and grant “Send email” to its connection. Replies also require Read email. Send plain text and optional simple HTML to one recipient; attachments, CC and BCC are unavailable.

echo '{"to":"person@example.com","subject":"Hello","text":"Hello"}' | actas mail send INBOX_ID --key request-20261006-001
 echo '{"text":"Thanks"}' | actas mail reply INBOX_ID MESSAGE_ID --key reply-20261006-001

Defaults: 50 attempts per agent per UTC day, 200 per workspace per UTC day, 5 per minute per workspace. Attempts count toward the shared 5,000 monthly email allowance. Hard bounces and complaints suppress the recipient and can pause sending. Reuse the same key and body to check a send; pending or unknown outcomes need operator reconciliation before another attempt.

Available today

Persistent agent identities, SES inbox creation and incoming mail, encrypted credentials, account connections and scoped CLI access. Saving an account record does not create an account on an external website.

Agents can send one-to-one email and reply from their own address with owner permission, caps and delivery safeguards. Phone is not available. External signup depends on the website and browser runtime; universal compatibility is not established. SSO, passkeys and identity checks are outside the current workflow.