What can the agent actually do once connected?

Everything the CLEATUS REST API exposes: search 1M+ federal and SLED opportunities, pull AI-ranked recommendations, read full opportunity details, manage the pipeline and pursuits, create and update tasks, search market intelligence (agencies, contractors, contracting officers), run workflows, and search the Document Hub. Write actions are guarded with confirm-before-change and every call lands in the audit log.

Do I need a CLEATUS account first?

Yes. Account creation and the OAuth approval are the two steps that deliberately stay human; your agent can do everything else. No account yet? Ask your agent to set CLEATUS up: it hands you the signup link (7-day free trial), waits while you create the account, then verifies the connection itself. The same login works in the your OpenClaw agent connection flow.

Connect OpenClaw to CLEATUS: MCP endpoint https://www.cleat.ai/api/mcp/mcp (OAuth 2.1 + PKCE, dynamic client registration). REST alternative with X-Api-Key, OpenAPI spec at https://api.cleat.ai/api/openapi.json, interactive docs at https://api.cleat.ai/api/docs. Plain-text platform guide: https://www.cleat.ai/llms-full.txt. Signup for a new account: https://www.cleat.ai/authentication/signup?utm_source=agents&utm_medium=openclaw (7-day free trial).
Setup: Add the MCP server: Add https://www.cleat.ai/api/mcp/mcp to your agent's MCP server list. Authenticate once: The first tool call triggers OAuth 2.1 + PKCE. A human signs in and scopes the token to one CLEATUS entity. Give it a loop: Schedule the agent to pull new recommendations daily, triage against your capabilities, and add qualified matches to the pipeline with notes.

CLEATUS for OpenClaw · autonomous agent

Connect OpenClaw to Government Contracting

OpenClaw agents connect to CLEATUS over MCP. Add the server URL to your agent config, complete OAuth once, and the agent can watch for fitting opportunities, triage them, and maintain your pipeline autonomously.

The setup

1
Add the MCP server
Add https://www.cleat.ai/api/mcp/mcp to your agent's MCP server list.
2
Authenticate once
The first tool call triggers OAuth 2.1 + PKCE. A human signs in and scopes the token to one CLEATUS entity.
3
Give it a loop
Schedule the agent to pull new recommendations daily, triage against your capabilities, and add qualified matches to the pipeline with notes.

Copy-paste config

openclaw config

{
  "mcpServers": {
    "cleatus": {
      "url": "https://www.cleat.ai/api/mcp/mcp"
    }
  }
}
// first call opens OAuth sign-in; token is entity-scoped
// no account yet? https://www.cleat.ai/authentication/signup?utm_source=agents&utm_medium=openclaw

What to ask once connected

Every morning: pull new CLEATUS recommendations, keep anything scoring above 70, add to pipeline with a one-line rationale.Ships as an installable skill: Morning BD Triage →

Watch for sources-sought notices in our NAICS codes and draft a capability-statement response outline.Ships as an installable skill: Sources Sought Responder →

When a pursuit moves to proposal stage, create the compliance-matrix task list.Ships as an installable skill: Proposal Kickoff →

All agent platforms

Setup guides for 8 platforms, plus the REST API in the developer hub.

Agents hub →Developers →

OpenClaw + CLEATUS FAQ

Frequently Asked Questions

Over OAuth 2.1 with PKCE. The first time your OpenClaw agent calls the CLEATUS MCP server it opens a browser window: sign in (or create an account), pick the CLEATUS entity to scope the connection to, and approve. your OpenClaw agent receives an entity-scoped token; no API key is pasted anywhere, and you can revoke the connection from CLEATUS at any time.