MCP.so
Sign In

Kora

@Idkasam

About Kora

kora - MCP server for Kora — give Claude governed spending with zero code

Basic information

Category

Other

License

Apache-2.0

Runtime

python

Transports

stdio

Publisher

Idkasam

Submitted by

Idkasam

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "kora": {
      "command": "kora-mcp",
      "env": {
        "KORA_API_URL": "https://api.koraprotocol.com",
        "KORA_AGENT_SECRET": "kora_agent_sk_...",
        "KORA_MANDATE": "mandate_...",
        "KORA_ADMIN_KEY": "kora_admin_sk_..."
      }
    }
  }
}

Tools

5

Authorize a spend — returns APPROVED + seal or DENIED + hint

Check daily/monthly remaining, velocity, time windows

List recent authorizations

Server health and version

Full audit trail for a mandate

Overview

What is Kora?

Kora is a cryptographically secure Go/No-Go layer for autonomous software, implemented as a Model Context Protocol (MCP) server. It enables LLMs (Claude, GPT-4, Cursor) to request explicit permission before initiating financial actions, providing budget-checked, Ed25519-signed spending with no SDK integration needed.

How to use Kora?

Install kora-mcp-server via pip, then add Kora as an MCP server in your client configuration (e.g., Claude Desktop) by setting environment variables KORA_AGENT_SECRET, KORA_MANDATE_ID, and KORA_BASE_URL. Restart the client; your AI agent can then call tools like kora_spend to authorize spending.

Key features of Kora

  • Budget-checked, Ed25519-signed spending for AI agents
  • Zero-code integration – no SDK needed
  • Deterministic 14-step approval pipeline (no ML)
  • Cryptographically sealed decisions with actionable hints
  • Five available tools: spend, budget check, activity, health, audit

Use cases of Kora

  • An AI agent requesting permission to spend $50 on AWS infrastructure
  • Checking daily/monthly remaining budget and velocity before a transaction
  • Auditing recent authorizations and full mandate history
  • Health-checking the Kora server from an MCP client

FAQ from Kora

What makes Kora different from other authorization systems?

Kora uses a deterministic, no-ML pipeline to approve or deny spending requests, providing a cryptographically sealed Go/No-Go decision. Every decision is signed with Ed25519.

What are the runtime dependencies for Kora?

Python is required to run the MCP server via kora-mcp-server, and an MCP client (e.g., Claude Desktop) is needed to invoke the tools. The server communicates with a remote Kora server specified by KORA_BASE_URL.

Where does authorization data live?

Authorization decisions and budgets are managed on the Kora server instance you point to via KORA_BASE_URL. The MCP server only relays signed requests and responses.

What types of actions can Kora authorize?

Kora is designed for financial actions like spending money. The available tools focus on spending, budget checks, and audit trails.

How does authentication work?

Authentication is handled via an Ed25519 signing key (KORA_AGENT_SECRET) and a mandate identifier (KORA_MANDATE_ID) provided as environment variables. No additional transport layer security is documented beyond this key-based signing.

Comments

More Other MCP servers