MEOK.AI
Sign inStart Free
Features
Pricing
Blog
About
🚀 Activate your agent

Free forever · No credit card

Open Source

Built in the open.
Governed by covenant.

MEOK's core tools are open-source. Not because we have to be — because sovereignty requires transparency.

CSOAI Robot Mascot — Corporate Sovereign Open AI

What licence does MEOK use?

MEOK core components are released under the Functional Source License 1.1 (FSL 1.1). You can read, audit, fork, and contribute from day one. FSL 1.1 prohibits competing commercial products from using the same functionality for two years — after which all code automatically converts to Apache 2.0. Client libraries and plugin SDKs are released under the fully permissive MIT licence.

This is the same model used by Sentry, HashiCorp, and Elastic. Open enough to build on. Fair enough to sustain.

FSL 1.1 Components

  • Character SDK
  • MCP Server Toolkit
  • SOV3 Byzantine Council
  • MCP Mesh Network

Open to read, audit, fork, and contribute. Converts to Apache 2.0 after 2 years.

MIT Components

  • 255 MCP servers
  • Client libraries
  • Plugin scaffolding

Fully permissive. Use in any project, commercial or personal, without restriction.

255

GitHub Repos

39K+

Lines of MCP Code

100%

Open Source

MIT

Licensed

Which MEOK components are open source?

The infrastructure of sovereign AI — readable, forkable, improvable by anyone.

Character SDK

FSL 1.1

Build your own companions. Define personality, voice, care style, and domain. Submit to the marketplace for a 70/30 revenue split — you keep 70%.

MCP Server Toolkit

FSL 1.1

255 production-ready MCP servers. From AI safety to business automation — every server is MIT licensed, security audited, and ready for Claude, Cursor, and any MCP client.

Byzantine Council

FSL 1.1

The 33-agent fault-tolerant consensus system at the heart of SOV3. Open for academic use, research, and peer review.

How does the MEOK plugin marketplace work?

Community-built companions and integrations run inside fully isolated WASM modules via Extism. Sandboxed at the runtime level — no malware possible. Unlike VS Code extensions, a rogue plugin cannot read your filesystem, phone home, or touch another plugin's memory.

70%

Creator revenue share

WASM

Sandboxed runtime — zero malware surface

GitHub

Submit via PR — reviewed within 72h

Submit your plugin via a GitHub pull request to the meok-ai organisation. Once merged, your companion or integration is live in the marketplace and earning revenue share on every subscription that uses it.

🔌

MCP Marketplace

Explore 255 production-ready MCP servers. AI safety, business automation, healthcare, robotics, and more. Every server is MIT licensed, security audited, and ready for Claude, Cursor, and any MCP-compatible client.

Browse 255 MCP Servers →View on GitHub

How do I contribute to MEOK?

Four steps from lurker to contributor with skin in the game.

Step 01

Join the Discord

Introduce yourself, pick a working group — character builders, protocol engineers, or research.

Join Discord →

Step 02

Pick a bounty

Browse GitHub Issues labelled bounty. From docs fixes to new MCP connectors — every level welcome.

View GitHub Issues →

Step 03

Fork → PR → review

Standard GitHub flow. Our maintainers review within 72 hours. All contributors are credited in the changelog.

Step 04

Earn rev-share

Merged plugin contributions earn ongoing marketplace rev-share. Open-source work that pays.

Star us on GitHub

Every star funds open-source sovereign AI. The more visible we are, the more contributors we attract, the faster the ecosystem grows.

View meok-ai on GitHubDesktop OS →

The meok-ai GitHub organisation may not be publicly visible yet — we're staging the open-source release. Star this page and we'll notify you when repos go live.