v0.5.6Apache 2.023+ export targets

Every Agent
Needs a Contract

MCP connects tools. A2A connects agents. Neither defines the contract.

The M×N Problem

Every framework defines agents differently. LangChain has one format. CrewAI has another. Kubernetes needs its own manifests. GitLab has its own agent config. If you support M agent types across N platforms, you're maintaining M×N configurations. That's fragmentation.

This costs real engineering time: rewriting manifests for every new platform, vendor lock-in when you want to switch, compliance gaps when governance metadata lives in different places, and wasted effort keeping everything in sync.

Before OpenAPI, every API had a different description format. The same thing is happening with agents right now.

LangChain

CrewAI

K8s

Claude

Support Bot

.yml

Code Review

.yml

Data Pipeline

.yml

3 agents × 4 platforms = 12 configs to maintain

The fix

Where OSSA Sits

One contract layer above the protocols. Define once, export everywhere.

Your ApplicationAgent Logic & Business Rules

OSSA Contract Layer

Identity·Capabilities·Compliance·Lifecycle·Security·Trust

MCPTools & Context

A2AAgent Comms

ANP / ACPNetwork Layer

Deployment Platforms

LangChain·CrewAI·Kubernetes·Docker·GitLab Duo·Claude Code·Cursor·Drupal·MCP·A2A·npm·+ more

3 agents × 1 manifest each → export to any platform

The Missing Layer

The Contract Layer That Bridges
Protocols to Platforms

MCP connects tools. A2A connects agents. OSSA is the contract that says how to deploy, govern, and move agents between platforms — without rewriting anything.

MCP

Tool and context protocol. Connects LLMs to external data and capabilities.

What the agent can use

OSSA

The agent contract. Deploy, govern, and migrate agents across any platform.

The portable definition

A2A

Inter-agent communication. How agents talk to each other.

How agents communicate

	MCP	OSSA	A2A
Purpose	Connects agents to tools	Defines the agent contract	Connects agents to agents
Answers	“How does it access tools?”	“What IS this agent?”	“How do agents talk?”
Artifact	Server definition	Portable YAML manifest	Agent Card (per-endpoint)
Security	None native	Compliance + trust metadata	Endpoint-level auth
Portability	Server-specific	Framework & platform agnostic	Protocol-specific

OSSA doesn't replace MCP or A2A — it's the portable manifest that references both.
Define once in YAML. Export to any platform.

Interactive playground is not bundled in this static export build.

What's in the Spec

OSSA covers the full lifecycle of production agent systems. Every feature has an honest maturity label.

Agent Identity & Capabilities

MCP Tool Integration

production

Define MCP server connections, operations, and capabilities directly in your manifest. Works with the official MCP PHP SDK, Symfony MCP Bundle, and all major implementations.

A2A Protocols

production

Agent-to-agent communication patterns, message schemas, and coordination contracts. Complements Google A2A protocol.

Skills Pipeline

new

Research, generate, and export agent skills. New in v0.4.

Governance & Safety

Compliance Modeling

production

SOC2, HIPAA, GDPR, and FedRAMP requirements expressed as structured metadata in the manifest.

Human-in-the-Loop

production

Approval workflows, intervention points, and escalation policies defined at the spec level.

Cost Controls

production

Token budgets, daily spend limits, and cost tracking configuration per agent.

Runtime & Infrastructure

State Management

production

Persistent state, checkpointing, and recovery contracts for long-running agent workflows.

Mesh Networking

beta

Service discovery and inter-agent routing for distributed agent systems.

AG2 Extensions

beta

AutoGen v2 integration for multi-agent conversation patterns.

The Trust Problem Nobody's Solving

Agents trust tool descriptions at face value. There's no verification, no signing, no supply-chain integrity.

The Current State

A recent security analysis identified 16 distinct threat scenarios in MCP alone — including naming attacks, tool poisoning, and description manipulation. Agents have no identity verification. There's no trust chain between agent publisher and consumer.

Source: Hou et al., “MCP: Landscape, Security Threats, and Future Research Directions” (2503.23278)

What OSSA Does About It

Security posture metadata — compliance declarations and access tiers in the manifest
Version-pinned capabilities — agents declare exactly what they require and are authorized to access
Governance as first-class metadata — SOC2, HIPAA, GDPR, and FedRAMP requirements expressed at the spec level, not bolted on after (your auditor still signs off)

Get Started

Install, create, export. Under 5 minutes.

terminal

# 1. Install

npm install -g @bluefly/openstandardagents

# 2. Create & validate

ossa init my-agent --template full -y
ossa validate my-agent.ossa.yaml

# 3. Export to any platform

ossa export my-agent.ossa.yaml --to docker
ossa export my-agent.ossa.yaml --to claude-agent-sdk
ossa export my-agent.ossa.yaml --to langchain

Full Getting Started Guide

Built-in MCP Server

10 MCP Tools. Works in Every AI IDE.

OSSA ships a production MCP server that works in Claude Code, Cursor, Windsurf, and any MCP-compatible client. Validate, scaffold, convert, and publish agents without leaving your editor.

ossa_validate

Validate manifests against v0.4 schema

ossa_scaffold

Create new agent directory structure

ossa_convert

Export to 23+ platforms instantly

ossa_inspect

Deep analysis of capabilities and access tiers

ossa_generate

Generate agent-card.json for A2A discovery

ossa_publish

Publish to registries via HTTP or arctl

ossa_list

Discover all agents in workspace

ossa_workspace

Init, discover, and manage workspaces

ossa_diff

Compare manifests with breaking change detection

ossa_migrate

Migrate manifests to newer spec versions

.mcp.json

{
  "mcpServers": {
    "ossa": {
      "command": "npx",
      "args": ["-y", "@bluefly/openstandardagents", "serve", "--mcp"]
    }
  }
}

Add to your IDE's MCP config. Works in Claude Code, Cursor, Windsurf, and more.

CMS Integration

Drupal-Native Agent Import

OSSA manifests import directly into Drupal as config entities. Create agents with the CLI wizard, import into your CMS, and Drupal auto-discovers API tools.

Create

Use the interactive wizard to define your agent

ossa wizard

Export

Wizard outputs a portable OSSA YAML manifest

agent.ossa.yaml

Import

Import into Drupal via UI form or Drush

drush ossa:import manifest.yaml

What happens on import

✓Drupal creates a config entity from the OSSA manifest (PHP-native validation included)
✓API tools are auto-discovered from the manifest's tool definitions
✓Agent becomes available to Drupal AI modules (ai_agents, ai_agents_ossa, MCP Registry)
✓Works with the Drupal import form (paste YAML) or CLI: drush ossa:import manifest.yaml

Platform Status

Honest maturity labels. We ship what works and label what doesn't.

Production

LangChain (Python/TS)
MCP (Model Context Protocol)
npm (installable package)
Docker (compose + multi-stage)
Kubernetes (kagent CRDs)
GitLab Duo Agent
Agent Skills
A2A (agent-card.json)
Anthropic (Messages API)
OpenAI (Assistants/function_calling)

Beta

CrewAI (agent roles)
Claude Code (IDE)
Claude Agent SDK (TS/Py/Go/Rust)
Cursor (IDE rules)
Drupal (CMS import)
LangFlow (visual workflow)
Warp (terminal agents)
Mobile Agent (runtime)
AutoGen (ConversableAgent)
Semantic Kernel (plugin)

Key Numbers

npm versionv0.5.6
GitHub stars5
Weekly downloads42
Export targets23+
CLI commands65+
MCP tools10
Example manifests30+
Test suites121
LicenseApache 2.0

Metrics sourced from npm registry and GitHub API. Updated every 5 minutes.

Dogfooding OSSA — this site uses OSSA-defined agents

content-syncversion-updaterlink-validatordeploy-orchestrator

Try it now

Create your first OSSA agent in minutes with our interactive creator. No installation required — just click and build.

Quick Start Guide GitLab Repo Join Discord

How this site is built →

Every AgentNeeds a Contract

The M×N Problem

Where OSSA Sits

The Contract Layer That Bridges Protocols to Platforms

MCP

OSSA

A2A

What's in the Spec

Agent Identity & Capabilities

MCP Tool Integration

A2A Protocols

Skills Pipeline

Governance & Safety

Compliance Modeling

Human-in-the-Loop

Cost Controls

Runtime & Infrastructure

State Management

Mesh Networking

AG2 Extensions

The Trust Problem Nobody's Solving

The Current State

What OSSA Does About It

Get Started

10 MCP Tools. Works in Every AI IDE.

Drupal-Native Agent Import

Create

Export

Import

What happens on import

Platform Status

Production

Beta

Key Numbers

Try it now

Every Agent
Needs a Contract

The Contract Layer That Bridges
Protocols to Platforms