Mcp

Score agent manifests, generate CI workflows, and pull Clarx scan findings into your IDE.

Clarx MCP is an npm package published by ai.clarx that exposes Clarx cloud capabilities to AI agents over a stdio transport. The server is configured with two environment variables: an Anthropic API key and a Clarx MCP token, which together authenticate the agent against the Clarx platform.

The server covers three documented functions. First, it scores agent manifests — an agent can submit a manifest and receive a structured quality or compliance score from the Clarx analysis engine. Second, it generates CI workflow files, allowing an agent to produce ready-to-use continuous integration configurations based on the project context. Third, it pulls Clarx scan findings directly into the developer’s IDE, surfacing security or quality issues that Clarx has detected without requiring a manual context switch to a separate dashboard.

Because the transport is stdio, the server runs as a local child process and communicates through standard input and output. This means it integrates with any MCP-compatible host that supports stdio, such as a locally running IDE extension or agent harness, but it is not suitable for remote or networked deployments without a wrapper.

The package is at version 0.2.0 on the npm registry under the identifier @clarxai/mcp. There is no bundled license declaration in the registry record. Developers who need Clarx scan data, manifest validation, or CI scaffolding surfaced inside an agentic workflow are the target audience.

Use cases

  • Score an agent manifest against Clarx criteria to identify quality or compliance issues before deployment
  • Generate CI workflow files automatically as part of an agentic build pipeline
  • Pull Clarx scan findings into an IDE session without leaving the editor
  • Automate manifest review steps in a continuous integration process
  • Integrate Clarx cloud analysis results into an AI agent's decision loop

When to use it

  • When an agent needs to evaluate or validate agent manifests using Clarx scoring
  • When CI workflow generation should be automated within an agentic workflow
  • When Clarx scan findings need to appear inline in an IDE via an MCP-compatible host
  • When the host environment supports stdio transport for MCP servers

When not to use it

  • When no Clarx account or CLARX_MCP_TOKEN is available — the server requires both credentials
  • When a remote or HTTP-based MCP transport is needed instead of stdio
  • When the goal is general-purpose Postgres or database access — this server has no database tools
  • When a license-reviewed dependency is required — no license is declared in the registry record