Ecosystem & Integrations

Omegon works with the tools you already have. MCP servers, IDE rule files, API keys, and project conventions from other AI coding tools carry over with minimal setup.

Bring Your Tools

MCP Servers

If you use MCP (Model Context Protocol) servers with Claude Code, Cursor, or any other tool, they work in Omegon. Create .omegon/mcp.toml in your project:

# Local process (npx, uvx, etc.)
[servers.filesystem]
command = "npx"
args = ["-y", "@modelcontextprotocol/server-filesystem", "/home"]

# Docker/OCI container
[servers.postgres]
image = "ghcr.io/mcp/server-postgres:latest"
env = { DATABASE_URL = "{DATABASE_URL}" }

# Remote HTTP endpoint
[servers.my-api]
url = "https://api.example.com/mcp"
timeout_secs = 45

MCP tools, resources, and prompts are auto-discovered at session start. The agent can use them like any built-in tool.

Coming from Claude Code? Run omegon migrate claude-code to import your MCP server configs automatically.

OpenAPI Specs

If an internal or third-party REST API already publishes an OpenAPI spec, Omegon can compile it into project tools without a custom extension. Add .omegon/openapi.toml:

[linear]
spec = "api/linear.openapi.yaml"
auth = "bearer"
secret = "LINEAR_API_KEY"
read_only = true

Specs may be local JSON/YAML files or http(s) URLs. Credentials are read from environment variables, and read_only = true limits the generated tools to GET operations. See OpenAPI Tools.

IDE Rules & Project Instructions

Omegon reads project instructions from multiple formats. If you already have rules for another tool, they'll work:

Or import everything at once: omegon migrate auto

API Keys & Credentials

Omegon connects to 14 inference providers. If you already have API keys for any of them, set the environment variable or use /login:

Already using Claude Code or Codex CLI? omegon migrate auto picks up your existing credentials — no re-login needed.

Extend Omegon

Skills (instruction sets)

Skills are markdown instruction files that load automatically when the agent detects a matching task. 10 skills ship built-in (git, rust, python, security, OCI, etc.). To add your own:

1. Create a SKILL.md file with domain-specific instructions
2. Place it in .omegon/skills/your-skill/SKILL.md
3. The agent loads it when it detects relevant work

Plugins (packaged capabilities)

Plugins bundle personas, skills, tones, and tools into installable packages. Install from any git URL:

/plugin install https://github.com/user/my-omegon-plugin

A plugin is a git repo with a plugin.toml manifest. It can include:

• Personas — system prompts with persistent memory that grows across sessions
• Skills — domain-specific instruction sets
• Tones — communication style overlays
• Tools — script-backed or HTTP tools the agent can call

Extensions (process-isolated binaries)

For heavier integrations, extensions run as separate processes with crash isolation. Build one in 60 seconds:

omegon extension init my-extension
cd my-extension
cargo build --release
omegon extension install .

Extensions communicate via JSON-RPC over stdin/stdout. They can provide tools, widgets, resources, and more. See Extensions for details.

Popular MCP Servers

These community MCP servers work out of the box with Omegon. Add them to .omegon/mcp.toml:

Full list: github.com/modelcontextprotocol/servers

Compatibility at a Glance