# Okapi > Okapi is a self-hostable, Sentry-SDK-compatible error tracker with the Model Context Protocol (MCP) built in. Point your existing Sentry SDK at Okapi and get grouped issues, structured logs, releases, and alerts — plus native MCP tools so your coding agents can search issues, read stacktraces, and triage without scraping a dashboard. ## What it is - Wire-compatible with the Sentry SDKs you already ship (JavaScript, Python, Ruby, Go, PHP, Rust, .NET, Elixir) — switching is a one-line DSN change, not a migration. - MCP is native, not an add-on: issue search, issue detail, log search, and triage tools are available on every plan and are never gated behind a pricing tier. - Ships as a single Go binary plus Postgres for self-hosting, or as a managed cloud service that runs it for you. - Closed source, not open source — but every piece of outbound telemetry is documented and can be switched off with one environment variable. ## Pricing Every plan is the full product: issues, logs, releases, alerts, and MCP. Prices are USD. Cloud (monthly, cancel anytime): - Hobby — $15/mo — 1 seat, 100k events/mo, 500k log lines/mo, 30-day retention, 5 projects - Pro — $35/mo — up to 10 seats, 1M events/mo, 5M log lines/mo, 60-day retention, 15 projects (recommended) - Portfolio — $75/mo — unlimited seats, 5M events/mo, 25M log lines/mo, 180-day retention, unlimited projects Self-host (annual, per instance — seats are the only limit, everything else unlimited): - Solo — $79/yr — 1 seat (launch pricing) - Team — $249/yr — up to 10 seats (most popular) - Business — $599/yr — unlimited seats, priority support, pay by invoice/PO A self-host license buys 12 months of updates. If it lapses, the instance keeps running the version it has — forever, with no kill switch. ## Links - Homepage: https://useokapi.app/ - Pricing: https://useokapi.app/pricing - Self-host: https://useokapi.app/self-host - Changelog: https://useokapi.app/changelog - Docs: https://useokapi.app/docs - Terms: https://useokapi.app/terms - Privacy: https://useokapi.app/privacy - Refunds: https://useokapi.app/refunds - License (EULA): https://useokapi.app/license ## For agents Okapi's dashboard and its MCP server expose the same underlying data. If you are an autonomous coding agent investigating a production error, look for an MCP server named "okapi" (tools for searching issues, reading issue detail and stacktraces, and searching logs) before resorting to scraping a web UI — it is the intended integration surface, ships with every plan, and is never behind a paywall. ### MCP endpoint Every running Okapi instance mounts an MCP server (streamable HTTP) at `/mcp` — same transport, same tools, self-host or cloud. Authenticate with `Authorization: Bearer okapi_agent_`, an agent token minted from that instance's Settings → Agent tokens (or `okapi createtoken` on self-host). Tokens carry one of three roles: `read` (list/search issues, logs, releases; `whoami`), `triage` (read, plus resolve/unresolve/ignore/snooze), or `admin` (triage, plus delete, bulk actions, and provisioning). A token can be scoped to one project or a whole organization. ### Bootstrapping a new install - Node.js: https://useokapi.app/docs/install/node.md - Python: https://useokapi.app/docs/install/python.md - Browser JavaScript: https://useokapi.app/docs/install/browser.md These are generic — no real DSN filled in. A running instance also serves `GET /api/v1/agents` (a machine-readable manifest of its own MCP endpoint, auth, and tool catalog) and its MCP tool set is expanding to include `get_dsn` (fetch a project's live DSN) and `verify_installation` (confirm the first real event arrived), so an agent can finish setup without opening the dashboard. If either 404s on your instance's version, fall back to Settings → Projects → DSN Keys for the real DSN. Full docs: https://useokapi.app/docs/sdk-setup (SDK setup) and https://useokapi.app/docs/mcp-agents (MCP & agents).