Research · setup

Plug Claude
into the desk.

Skills are plain markdown, MCP tools are role-gated, the bearer token lives only in your Claude config. Three steps from cold to first call.

01

Install the skills

Drops six markdown files into ~/.claude/skills/. They tell Claude what tools to use for which questions.

install · ~/.claude/skills
$ curl -fsSL https://inite.fund/install.sh | sh

Pass --target=project to install into the current repo's .claude/skills/ instead.

02

Generate an API key

Bearer tokens for the MCP server. Hashed at rest; the plaintext shows once at creation. One key per Claude client.

  1. Open Settings → API tokens.
  2. Click Generate, name it (e.g. laptop).
  3. Copy the plaintext — it's shown once.
  4. If you lose it, revoke and generate a new one.
03

Add the MCP server

Pick the runtime where you use Claude. Replace YOUR_API_KEY with a token from your Account page.

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows). Restart Claude Desktop.

{ "mcpServers": { "strateg": { "transport": { "type": "http-sse", "url": "https://inite.fund/mcp" }, "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }
04

Try it

In any Claude chat:

show me current state of the balanced strategy

Claude detects the strateg-overview skill, calls get_state via MCP, and surfaces equity, drawdown, regime, and any pending approvals.

MCP setup details
Per-client config →

Desktop, CLI, SDK.
Tools reference
All MCP tools →

What they do, role required.