Orin MCP

Use Orin's four model chains from Claude, Cursor, VS Code, and other MCP clients through hosted Streamable HTTP or local stdio.

Install

Mint a scoped token in Orin Chat → Account → MCP tokens, then install from GitHub:

npx -y github:januththedev/orin-mcp
ORIN_MCP_TOKEN=… orin-mcp

The package runs prepare/prepack, so dist/cli.js is built before execution. The npm dry-run package test verifies that the binary is included.

Hosted endpoint:

https://mcp.orinai.org/api/mcp
Authorization: Bearer <scoped-token>

Related MCP server: WarungCyber MCP Server

Tools and scopes

• orin_chat, orin_generate — chat:generate

• orin_list_models and orin://models — models:read

• orin_usage and orin://usage — usage:read

Core enforces the same scopes on its direct /api/mcp endpoint. A token cannot bypass MCP scope checks by calling Orin Core directly.

Presets

• orin-cheap

• orin-balanced

• orin-thinking

• orin-coding

MCP requests are bounded to 100 messages, 12,000 characters per message, and 64 KiB aggregate request size.

Configuration

Diagnostics always use stderr so stdio stdout remains valid JSON-RPC.

Development

npm ci
npm run platform:build
npm run typecheck
npm test
npm run test:package

Tests are hermetic and use only local fakes. No live Orin, model, or external network call is made.

Security

• Tokens and provider secrets are never logged.

• Core verifies revocation and exact token type/scopes.

• HTTP accepts only a bounded bearer token shape.

• Provider API URLs are fixed to the trusted Orin Core origin.

• Local stdio logs cannot corrupt the MCP protocol stream.

• Unknown tool input is rejected before backend access.

License

MIT