LifeClaw

ai.agentese.lifeclawPublished by lifeclaw.agentese.aiOfficial publisherv1.0.0Updated Oct 25, 2026

Call you, a person, or a business; find places, book or inquire by phone, and return the answer.

VerifiedStreamable HTTPWeb executableLocation & LifestyleCommunication & Collaboration

Overview

AI-generated overview

LifeClaw is a remote MCP server that lets an assistant place phone calls, find or book places, and bring back the answers.

What you can do
Call the user, a specified person, or a business by phone. Find places and make bookings or inquiries by phone. Return the answers obtained from those calls to the assistant.
When to use it
Use it when the assistant needs to make phone calls on the user's behalf, such as reaching a person or a business, or finding and booking a place by phone. Suited to bringing the results of phone inquiries back into the conversation.
Requirements
Needs a connection to the remote endpoint with OAuth authentication, plus a Bearer API key supplied in the Authorization header. The key is obtained from the service's token settings page.
Before you install
Requires an API key in the Authorization header, which should be kept private. The server places real phone calls to people or businesses, which may incur call charges or contact third parties; call content and recipient details are sent to the provider.

Installation

In SourceWeft

  1. Open LifeClaw in the dashboard and add it to a workspace.
  2. Connect the required 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/ai.agentese.lifeclaw%2Flifeclaw/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "lifeclaw": {
      "type": "http",
      "url": "https://api-v2.lifeclaw.agentese.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 14, 2026

Score

67% 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
  • 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.