Kosli MCP Server

The Kosli MCP Server is a Model Context Protocol server that exposes the Kosli API to LLM clients. Once installed, you can ask Claude things like “which artifacts are running in prod-aws and which are non-compliant?” and it will call the relevant Kosli endpoints for you. It is published from kosli-dev/mcp-server and distributed as both an npm package (@kosli/mcp-server) and a .mcpb desktop bundle.

How it works

Rather than ship a tool per Kosli endpoint, the server generates a catalog from Kosli’s OpenAPI spec and exposes three generic tools:

Tool	Purpose
`search_actions`	Fuzzy-search the catalog for relevant actions by natural-language query.
`execute_read_action`	Invoke any GET action by ID. Auto-allowed in MCP clients.
`execute_write_action`	Invoke any POST/PUT/PATCH/DELETE action by ID. Gated behind user approval.

The typical flow is: the LLM calls search_actions to discover the right action ID and its parameter schema, then calls execute_read_action or execute_write_action with the chosen ID. Both execute tools accept an optional fields array to request only specific top-level fields in the response, which keeps token usage down.

Prerequisites

Node.js v20 or higher
A Kosli API token
An MCP-capable client (Claude Code, Claude Desktop, or any other)

Install

Claude Code
Claude Desktop (.mcpb)
Claude Desktop (manual)
Other MCP clients

Run from your project directory, or add --scope user to install globally:

claude mcp add kosli \
  -e KOSLI_API_TOKEN=your-token \
  -e KOSLI_ORG=your-org \
  -- npx -y @kosli/mcp-server

Download the latest .mcpb file from the releases page and drag it into Claude Desktop (or double-click to install). Claude Desktop will prompt for your API token and organization, and store secrets in the OS keychain.

Sideloaded extensions show an “unverified by Anthropic” warning and do not auto-update. These limitations will go away once the extension is listed in Anthropic’s Connectors Directory.

Edit claude_desktop_config.json via Settings → Developer → Edit Config:

{
  "mcpServers": {
    "kosli": {
      "command": "npx",
      "args": ["-y", "@kosli/mcp-server"],
      "env": {
        "KOSLI_API_TOKEN": "your-token",
        "KOSLI_ORG": "your-org"
      }
    }
  }
}

This method auto-updates via npx on each restart, but stores secrets in plain text.

The server communicates over stdio. Point any MCP-compatible client at the package via npx -y @kosli/mcp-server and set the required environment variables.

Configuration

The server reads configuration from environment variables.

Variable	Required	Default	Notes
`KOSLI_API_TOKEN`	yes	-	Preferred. `KOSLI_API_KEY` is accepted as a fallback.
`KOSLI_ORG`	yes	-	Default org used when a path parameter `org` is not supplied.
`KOSLI_BASE_URL`	no	`https://app.kosli.com`	Use `https://app.us.kosli.com` for US, or your single-tenant endpoint.

Example prompts

Once connected, try prompts like:

“List the environments in my org and tell me which are compliant.”
“Show me the last 5 deployments to prod-aws.”
“What attestations are on trail release-456 in flow my-release?”
“Create a new flow called payments-api.”

Read prompts run without confirmation. Write prompts (create, update, delete) require an approval step in the MCP client.

Limitations

The catalog is generated from a snapshot of the OpenAPI spec. New endpoints land when the catalog is regenerated and a new package is published.
LLM clients may need several search_actions calls before settling on the right action ID for ambiguous queries.
Response shapes are whatever the Kosli API returns. Use the fields parameter on execute calls to trim large responses.

Feedback

Tell us what you think - email support@kosli.com or open an issue at kosli-dev/mcp-server.

Kosli Next

Concepts

Preview

How it works

Prerequisites

Install

Configuration

Example prompts

Limitations

Feedback

​How it works

​Prerequisites

​Install

​Configuration

​Example prompts

​Limitations

​Feedback

How it works

Prerequisites

Install

Configuration

Example prompts

Limitations

Feedback