Clawmanagerfleet MCP logo

Clawmanagerfleet MCP

Leases governed ClawManager agent instances over Streamable HTTP with bearer-token access, status checks, closure, and runtime receipts.

Install Clawmanagerfleet MCP

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://clawmanagerfleet.clauxel.com/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

The clawmanagerfleet-mcp MCP server provides hosted remote access to ClawManager for leasing governed AI agent instances. It exposes four Streamable HTTP tools for requesting instances, checking their status, closing them, and exporting runtime receipts. Production access requires a bearer token issued through the ClawManager Fleet Control website. Reach for it when an MCP client needs remote fleet-control operations without a locally maintained runner queue.

Use cases

  • Request governed ClawManager agent instances
  • Check leased agent instance status
  • Close agent instances remotely
  • Export runtime receipts for records

Key features

  • Streamable HTTP MCP endpoint
  • Bearer-token authentication
  • Agent instance request and closure tools
  • Instance status checks
  • Runtime receipt export
  • Usage logs and server-card metadata

Tools4

What Clawmanagerfleet MCP lets your agent do. Expand a tool for its parameters.

Self-reported~21 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

20/20 checks healthy over the last 90d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit5mo agoMost recent push to the default branch.
Tools exposed4Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Clawmanagerfleet MCP works

What clawmanagerfleet-mcp MCP server does

The clawmanagerfleet-mcp MCP server connects MCP clients to the hosted ClawManager Fleet Control service. Its purpose is to support governed AI agent instance workflows through a remote MCP endpoint rather than a locally installed runtime. The service is paid and production requests require an access token.

The available operations cover the main instance lifecycle and its associated records:

  • request_agent_instance requests an agent instance.
  • check_instance_status checks an instance's current status.
  • close_agent_instance closes an agent instance.
  • export_runtime_receipt exports a runtime receipt in JSON-oriented form.

The service also exposes usage logs, receipt-oriented JSON, public server-card metadata, and a registry name for discovery or directory use.

How it works

The service is hosted at https://clawmanagerfleet.clauxel.com/mcp and communicates through Streamable HTTP tool calls. An MCP client sends JSON-RPC requests to that endpoint and includes the issued credential in an HTTP authorization header:

http
Authorization: Bearer <token>

The token is obtained through the product website after choosing a plan and creating or requesting an API token. Browser visits to the MCP path without authentication return a JSON error rather than exposing internal details.

The clawmanagerfleet-mcp MCP server does not provide its production implementation in this repository. The repository serves as public documentation and a directory-submission reference for the hosted service.

Setup and configuration

To use the service, open the ClawManager Fleet Control website, select a plan, and obtain an API token. Configure an MCP client that supports remote Streamable HTTP servers with the MCP endpoint and bearer token, then send JSON-RPC requests to the service.

The published endpoint is:

text
https://clawmanagerfleet.clauxel.com/mcp

The public server card is available at https://clawmanagerfleet.clauxel.com/server-card.json. The documentation does not specify a local package, a command-line launch procedure, or named environment variables. It also does not identify particular MCP client products.

Tools and capabilities

The four exposed tools map to instance control and runtime records. Use request_agent_instance to initiate an instance request, check_instance_status to inspect an instance, and close_agent_instance to end one. Use export_runtime_receipt when a runtime receipt is needed from the service.

Beyond tool calls, the hosted service publishes server-card metadata and provides usage logs.

Limitations and notes

The clawmanagerfleet-mcp MCP server is a paid hosted service, so production use depends on a plan and a bearer token. It also does not provide the private production source code, detailed API schemas, rate limits, retention policies, or client-specific setup instructions.

Before integrating it into an automated workflow, verify the required token process, supported Streamable HTTP behavior in the chosen MCP client, and the exact request and response schemas from the service documentation or server card.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Clawmanagerfleet MCP

clawmanagerfleet-mcp is an MCP server that connects AI agent workflows to the hosted ClawManager Fleet Control service. Its main tools request agent instances, check instance status, close instances, and export runtime receipts. It uses Streamable HTTP, requires a production bearer token, and is offered as a paid remote service.

You do not install local production source from this repository; configure an MCP client with the hosted endpoint and bearer token. Choose a plan on the product website, create or request an API token, then add `https://clawmanagerfleet.clauxel.com/mcp` to a client that supports remote Streamable HTTP servers.

Authenticate with a bearer token issued through the ClawManager Fleet Control website. Include it on requests in the `Authorization: Bearer <token>` HTTP header. Production calls require this token, while unauthenticated browser requests to `/mcp` return a JSON error.

It provides four tools: `request_agent_instance`, `check_instance_status`, `close_agent_instance`, and `export_runtime_receipt`.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewClawmanagerfleet MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/clawmanagerfleet-mcp?style=directory)](https://allmcps.com/mcp/clawmanagerfleet-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/clawmanagerfleet-mcp"><img src="https://allmcps.com/api/badge/clawmanagerfleet-mcp?style=directory" alt="Clawmanagerfleet MCP on AllMCPs" /></a>