Kagi Rs

kdcokenny2stars

Rust SDK and MCP server for Kagi search and summarization in apps and AI agents.

1# Kagi Rs

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: MIT
Last checked: 2026-10-28

Stars: 2
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Kagi Rs?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Kagi Rs need an API key?

No required environment variable is listed on this record.

What transport does Kagi Rs use?

Kagi Rs runs locally over stdio.

When was Kagi Rs last checked?

Last checked 2026-10-28. Rust SDK and MCP server for Kagi search and summarization in apps and AI agents.

From the publisher

Documentation

kagi-rs

Rust-native workspace for building Kagi integrations with a typed SDK and an MCP server for agents.

Workspace status

Path	Package	Status	Purpose
`sdk/`	`kagi-sdk`	✅ Available	Rust SDK with explicit official-api and session-web surfaces
`mcp/`	`kagi-mcp`	✅ Available	MCP server (v1: stdio-only, tools-only) built on `kagi-sdk`
`cli/`	(planned)	⏳ Planned	Reserved path for a future end-user CLI crate
`docs/`	n/a	✅ Available	Reference and maintainer/operator documentation

Quickstart (canonical)

Run the MCP server locally from source:

KAGI_API_KEY=... cargo run -p kagi-mcp

This starts a stdio MCP server you can register in Claude Code, Codex, or OpenCode.

Choose your path

Building Rust apps/services: start in sdk/README.md
Connecting agent hosts to Kagi: start in mcp/README.md
CLI roadmap/status: see cli/README.md
Docs index (user + reference + maintainer): see docs/README.md

Two surfaces, one SDK

kagi-sdk keeps Kagi's protocol surfaces explicit:

Surface	Auth	Route families	Response shape
Official API	`Authorization: Bot <token>`	`/api/v0/`, `/api/v1/` (in-scope subset)	JSON envelopes
Session web	`Cookie: kagi_session=<token>`	`/html/search`, `/mother/summary_labs`	HTML / JSON / framed stream

Authoritative endpoint/auth/version coverage: docs/endpoint-auth-version-matrix.md.

Docs map

Need	Go to
Workspace onboarding	`README.md`
SDK usage and API surfaces	`sdk/README.md`
MCP host setup and agent usage	`mcp/README.md`
CLI planned status	`cli/README.md`
Endpoint/auth/version source of truth	`docs/endpoint-auth-version-matrix.md`
Release + workflow policy (maintainer)	`docs/releasing.md`

Development commands

Run from repository root:

cargo fmt --all
cargo clippy --workspace --all-targets --all-features -- -D warnings
cargo test --workspace

Contributor and maintainer docs

Contributor onboarding remains in package READMEs; maintainer/operator policy lives in docs/releasing.md.

Kagi Rs

kdcokenny2stars

Rust SDK and MCP server for Kagi search and summarization in apps and AI agents.

Install Run on PlugMCP

GitHub Website

Run on PlugMCP

1# Kagi Rs

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: MIT
Last checked: 2026-10-28

Stars: 2
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Kagi Rs?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Kagi Rs need an API key?

No required environment variable is listed on this record.

What transport does Kagi Rs use?

Kagi Rs runs locally over stdio.

When was Kagi Rs last checked?

Last checked 2026-10-28. Rust SDK and MCP server for Kagi search and summarization in apps and AI agents.

From the publisher

Documentation

kagi-rs

Rust-native workspace for building Kagi integrations with a typed SDK and an MCP server for agents.

Workspace status

Path	Package	Status	Purpose
`sdk/`	`kagi-sdk`	✅ Available	Rust SDK with explicit official-api and session-web surfaces
`mcp/`	`kagi-mcp`	✅ Available	MCP server (v1: stdio-only, tools-only) built on `kagi-sdk`
`cli/`	(planned)	⏳ Planned	Reserved path for a future end-user CLI crate
`docs/`	n/a	✅ Available	Reference and maintainer/operator documentation

Quickstart (canonical)

Run the MCP server locally from source:

KAGI_API_KEY=... cargo run -p kagi-mcp

This starts a stdio MCP server you can register in Claude Code, Codex, or OpenCode.

Choose your path

Building Rust apps/services: start in sdk/README.md
Connecting agent hosts to Kagi: start in mcp/README.md
CLI roadmap/status: see cli/README.md
Docs index (user + reference + maintainer): see docs/README.md

Two surfaces, one SDK

kagi-sdk keeps Kagi's protocol surfaces explicit:

Surface	Auth	Route families	Response shape
Official API	`Authorization: Bot <token>`	`/api/v0/`, `/api/v1/` (in-scope subset)	JSON envelopes
Session web	`Cookie: kagi_session=<token>`	`/html/search`, `/mother/summary_labs`	HTML / JSON / framed stream

Authoritative endpoint/auth/version coverage: docs/endpoint-auth-version-matrix.md.

Docs map

Need	Go to
Workspace onboarding	`README.md`
SDK usage and API surfaces	`sdk/README.md`
MCP host setup and agent usage	`mcp/README.md`
CLI planned status	`cli/README.md`
Endpoint/auth/version source of truth	`docs/endpoint-auth-version-matrix.md`
Release + workflow policy (maintainer)	`docs/releasing.md`

Development commands

Run from repository root:

cargo fmt --all
cargo clippy --workspace --all-targets --all-features -- -D warnings
cargo test --workspace

Contributor and maintainer docs

Contributor onboarding remains in package READMEs; maintainer/operator policy lives in docs/releasing.md.