Logito
Log in Install CLI

Reference

MCP Server

Logito exposes a local MCP server that lets AI agents call runtime intelligence tools directly. The server bridges your CLI profile to both the hosted API and local CLI analysis.

Registers as logito_local. Communicates over stdio. Works with Claude Code, Codex, and any MCP-compatible client.

Install 
brew install logito
logito login
logito codex install

Architecture

How the bridge works

The MCP bridge is a single Python script that sits between your AI agent and Logito. It implements MCP protocol version 2024-11-05 over stdio and proxies tool calls to the Logito API. It also runs local analysis directly via the CLI when the hosted API has no data for a requested scope.

1

Agent sends a tool call

Claude Code, Codex, or another MCP client sends a JSON-RPC request over stdio.

2

Bridge authenticates

The bridge reads your CLI profile at ~/.logito/config.json, derives an agent-scoped token, and refreshes it automatically when it expires.

3

Request is routed

Remote tools are proxied to the Logito API at /v1/agent/tools/call. Local tools like API contract drift run directly via the CLI binary.

4

Results are merged

When both remote and local data are available, the bridge merges them into a single response. When remote data is empty, it can synthesize a local-only result.

Setup

Prerequisites

1. Install the CLI

brew tap progadigital/tap
brew install logito

2. Log in

logito login

Creates a profile at ~/.logito/config.json. The MCP bridge reads this profile for authentication.

3. Install the MCP plugin

logito codex install

Writes the plugin bundle to ~/plugins/logito and registers it in the local marketplace.

4. Verify

# Send an initialize message to the bridge
cd ~/plugins/logito
printf 'Content-Length: 75\r\n\r\n{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"capabilities":{}}}'  | python3 ./scripts/logito_mcp_bridge.py

You should see a response with logito_local and protocol version 2024-11-05.

Tools

What the server exposes

Tools are fetched dynamically from the Logito API plus one local-only tool backed by the CLI.

Local tool

logito.get_api_contract_drift

Runs logito drift --format json against a stored local OpenAPI baseline. No API dependency. Works offline.

Remote tools

  • logito.get_action_bundle
  • logito.get_remediation_cluster
  • logito.get_findings_evidence
  • logito.explain_issue
  • All other tools registered at /v1/agent/tools

Resources

  • logito://auth — Auth status and profile readiness
  • logito://context — Active org, workspace, API URL
  • logito://tools — Full tool catalog

Smart fallback

When the API has no sessions or signals for the requested scope, the bridge synthesizes results from local CLI analysis instead of returning an error. This means agents get useful drift data even before the first cloud-connected run.

Authentication

How auth works

The bridge derives an agent-scoped access token from your CLI login. It refreshes this token automatically on expiry, and recreates it when the active org or workspace changes. On 401 or auth-related 403 responses, it retries once with a fresh token.

For advanced setups, override auth with environment variables:

Overrides 
LOGITO_CONFIG_PATH=~/.logito/custom.json
LOGITO_API_BASE_URL=https://api.example.com
LOGITO_AGENT_ACCESS_TOKEN=your-token
LOGITO_ACTIVE_ORG=org-id
LOGITO_ACTIVE_WORKSPACE=ws-id
LOGITO_BIN=/usr/local/bin/logito

Testing

Verify the bridge is working

Quick smoke test

cd plugins/logito
python3 scripts/test_mcp.py

Sends initialize, tools/list, and resources/read to the bridge and prints formatted responses.

Make target

make smoke-logito-agent-mcp \
  TOOL_NAME=logito.get_latest_run

Tests agent login plus bridge connectivity against the API.

Full integration

make smoke-logito-self-improve-docker

Creates temp configs, signs in, starts capture, drives traffic, and verifies the bridge end-to-end on the local Docker stack.

Pre-release gate

make smoke-logito-pre-release-gate

Full integration gate for maintainers before a release.

Comparison

Local bridge vs hosted MCP

logito_local (this bridge)

  • Stdio transport
  • Auth via CLI profile
  • Local drift analysis available
  • Best for: local development, Codex, Claude Code

Hosted /mcp endpoint

  • HTTP transport with OAuth
  • No local CLI dependency
  • No local drift or filesystem access
  • Best for: third-party remote MCP clients

Team Setup

Distribution for teams

1

Commit the plugin

Keep the plugins/logito/ directory and marketplace manifest checked into the repo.

2

Each engineer runs login once

logito login
3

Enable in agent

Codex and Claude Code discover the plugin from the repo marketplace automatically.

Install

Connect your agent to runtime intelligence.

Install CLI Claude Code Integration