Can n8n use the CLEATUS MCP server instead of the REST API?

Yes. n8n's MCP Client Tool node (used inside AI Agent workflows) can point at the CLEATUS MCP endpoint and call the same 34 tools conversationally. Rule of thumb: deterministic scheduled flows are simplest over REST with an API key; agent-style n8n workflows that reason over tools use the MCP client.

How do I get a CLEATUS API key?

Sign in to CLEATUS, open Settings → Integrations → API Keys, and create one. The key is shown once and can be revoked anytime. API access is included on plans with Automations.

What are the rate limits?

Per-key rate limits (generous for automation workloads: 100 reads/min and 30 writes/min), shared with the MCP surface so one quota covers both. 429 responses include a Retry-After header.

Connect n8n 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=n8n (7-day free trial).
Setup: Mint an API key: In CLEATUS: Settings → Integrations → API Keys → Create. The plaintext shows once; store it as an n8n credential. Add an HTTP Request node: Point it at https://api.cleat.ai with the X-Api-Key header. The OpenAPI spec lists all 34 endpoints. Build the loop: Cron trigger → search or recommendations → filter → add to pipeline → notify Slack/Teams/CRM.

CLEATUS for n8n · automation platform

Connect n8n to Government Contracting

n8n workflows call the CLEATUS REST API directly. Mint a long-lived API key in CLEATUS, drop it in an HTTP Request node, and build flows that watch opportunities, sync your CRM, and post alerts to Slack or Teams.

The setup

1
Mint an API key
In CLEATUS: Settings → Integrations → API Keys → Create. The plaintext shows once; store it as an n8n credential.
2
Add an HTTP Request node
Point it at https://api.cleat.ai with the X-Api-Key header. The OpenAPI spec lists all 34 endpoints.
3
Build the loop
Cron trigger → search or recommendations → filter → add to pipeline → notify Slack/Teams/CRM.

Copy-paste config

n8n HTTP Request node

GET https://api.cleat.ai/v1/opportunities/search
Headers:
  X-Api-Key: ck_live_…   // Settings → Integrations → API Keys
Query:
  q=cybersecurity
  naics_codes=541512,541511
  states=VA,MD

// full surface: https://api.cleat.ai/api/openapi.json

What to ask once connected

Daily: fetch new recommendations, filter score > 70, post to #bd-pipeline in Slack.Ships as an installable skill: Morning BD Triage →

On new pursuit: create a row in the CRM and a kickoff task list in CLEATUS.Ships as an installable skill: Proposal Kickoff →

Weekly: pull pipeline by phase and email a status digest.Ships as an installable skill: Pipeline Hygiene →

All agent platforms

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

Agents hub →Developers →

n8n + CLEATUS FAQ

Frequently Asked Questions

You do not need one: the REST API works from n8n's standard HTTP Request node with a single X-Api-Key header. Every CLEATUS capability (opportunity search, recommendations, pipeline, pursuits, tasks, workflows, market intelligence) is a plain HTTPS endpoint documented in the OpenAPI spec.