MCP(모델 Context Protocol)의 제어반 런타임. Gateway, vault, 정책 엔진 및 AI 에이전트 및 다운스트림 MCP 서버 간의 모든 도구 통화에 대한 감사 트레일.

생산에 MCP를 실행해야 하는 핵심 인프라 구성 요소 지원: 게이트웨이 라우팅, 런타임 감독, 정책 시행, 자격 관리, 감사 로깅.

** 키 보증:**

• ** 치과 결함.** 비밀은 나머지 (PBKDF2 + AES-GCM)에서 암호화되며 실행 시간에 서버 측을 주입합니다. 클라이언트는 원료를 결코 볼 수 없습니다.
• ** 정책 엔진. ** RBAC/ABAC per-user, per-tool 기능 필터링. High-risk 가동을 위한 선택적인 인간에서 반복 승인.
• 오디오 트레일. 모든 도구 호출은 콜러 정체성, 정책 결정, 그리고 outcome으로 로그인됩니다. 비밀은 로그에 포함되지 않습니다.
• 관리 실행시간. Lifecycle 통제 및 자동화된 회복을 가진 Downstream MCP 서버 감독.
• Protocol 호환성. Standard MCP 업스트림, 그리고 공유 게이트웨이의 다운스트림 호환성은 Peta Core가 현재 지원되는 것입니다.

Peta Core

A control-plane runtime for MCP (Model Context Protocol). Gateway, vault, policy engine, and audit trail for every tool call between AI agents and downstream MCP servers.

Supports the core infrastructure components required to run MCP in production: gateway routing, runtime supervision, policy enforcement, credential management, and audit logging.

Key guarantees:

• Credential vault. Secrets stay encrypted at rest (PBKDF2 + AES-GCM) and are injected server-side at execution time. Clients never see raw credentials.
• Policy engine. RBAC/ABAC with per-user, per-tool capability filtering. Optional human-in-the-loop approval for high-risk operations.
• Audit trail. Every tool call is logged with caller identity, policy decision, and outcome. Secrets are never included in logs.
• Managed runtime. Supervises downstream MCP servers with lifecycle controls and automated recovery.
• Protocol compatibility. Standard MCP upstream, plus downstream compatibility for the shared gateway flows that Peta Core currently supports. Standard server-initiated reverse requests (sampling, roots, elicitation) are intentionally not exposed in the current shared runtime.
• Self-hosted. On-premises deployment model. No hosted SaaS dependency.

Quick Start | Website | Documentation

---

Architecture

Peta Core sits between MCP clients (Claude, ChatGPT, Cursor, n8n, or any MCP-compatible client) and downstream MCP servers. From the client’s perspective, it connects to a single MCP server. Behind that endpoint, Peta Core routes to multiple downstream servers using standard MCP for the shared forward-request flows it supports.

Peta Core is one component of the Peta MCP stack:

• Peta Core (this repository) — MCP gateway, credential vault, policy engine, and audit runtime.
• Peta Console — Admin UI for users, servers, policies, approvals, and audit logs.
• Peta Desk — Desktop client for approval workflows and per-user server configuration.

This repository contains only Peta Core. See docs.peta.io for the full stack.

---

Features

MCP Gateway

• Transparent MCP proxying. Acts as an MCP server upstream and an MCP client downstream. Routes tool calls via namespaced identifiers (serverId::toolName).
• MCP 2025-11-25 support. Modern clients can use stateless server/discover, POST-only Streamable HTTP, subscriptions/listen, and OAuth resource metadata behind an opt-in rollout flag while legacy sessionful clients remain supported.