AgentBrink

com.agentbrink.wwwPublished by www.agentbrink.comv1.0.0Updated Oct 24, 2026

Give your AI agent an identity: its own email, webhook, repo, secrets vault, memory and skills.

Overview

AI-generated overview

Remote MCP endpoint that gives an AI agent its own identity: email, webhook, repo, secrets vault, memory and skills.

What you can do
  • Connect an assistant to a hosted agent identity rather than a set of documented tools.
  • The agent gets its own email address and webhook endpoint for receiving messages and events.
  • It gets a repository and a secrets vault tied to that identity.
  • It keeps memory and skills across sessions under the same agent.
  • No tool list is published, so the exact operations are only visible after connecting.
When to use it
Worth considering when you want an assistant to act as a persistent, addressable agent with its own inbox, webhook, storage and memory, instead of borrowing your personal accounts. Less suitable if you need a documented, auditable tool surface before installing.
Requirements
A remote streamable HTTP endpoint; no local package or runtime. A bearer token in the Authorization header is required, created by registering an agent on the provider's site; the key is scoped to exactly that one agent.
Before you install
The connection is authenticated with a bearer API key that grants access to that agent's email, repository and secrets vault, so treat it as a sensitive credential. The server stores secrets and memory on the provider's side, and the agent can receive mail and webhook events from outside. Tool behavior is not documented in the manifest, so review what it can do after connecting.

Installation

In SourceWeft

  1. Open AgentBrink in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. 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/com.agentbrink.www%2Fmcp/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": {
    "agentbrink": {
      "type": "http",
      "url": "https://api.agentbrink.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% 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
  • Auth declaredRequired10 pts
  • 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.