Mitii

MCPAI代理

提供方 Mitii-dev

AI代理 未标注 API Key 社区 / 第三方 ClaudeCursorVS CodeCline

Your workspace-driven AI assistant for complex development. Mitti combines hybrid SQLite memory with seamless Model Context Protocol (MCP) tool integration to read files, write code, and run commands, all while keeping your data 100% self-hosted and protecting your token budget.

一句话选型结论

按资料字段整理

Mitii 属于AI代理类 MCP 服务器,传输方式未标注,API Key,可直接接入 Claude、Cursor、VS Code 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式未标注 鉴权API Key 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

ai ai agent vscode vscode extension qwen ollama local first

支持客户端

适用场景

aiai agentvscode

安装与配置

未标注 API Key
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Mitii当前 未标注 未标注 未标注 无 未标注
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Mitii-dev上游标注的维护方 Mitii-dev
分类AI代理本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · node本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

10.8 KB
来自项目仓库与上游目录的原文,未做删改

Mitii AI Agent

Mitii.dev_" width="220" />

A local-first AI coding agent for VS Code with repository-aware context, controlled execution, and flexible model providers.

AI coding agent · VS Code · local-first · MCP · Ollama · TypeScript

Mitii understands a repository before it changes it. It combines local indexing, Ask/Plan/Agent workflows, optional FIM autocomplete, approval-aware tools, checkpoints, memory, and session logs in one VS Code experience. Use a local OpenAI-compatible model for privacy, or any OpenAI-compatible cloud endpoint when more capability is required.

What Mitii provides

  • Repository-aware context - SQLite FTS5, symbols, vectors, repo maps, diagnostics, Git state, and explicitly attached files.
  • Clear operating modes - Ask for read-only analysis, Plan complex work, Agent applies changes, and Review inspects working-tree diffs with structured findings.
  • Structured code review - Deterministic file selection, path rules, line-anchored findings (emit_review_finding), durable ReviewRecord under .mitii/review/, SARIF export, and CI PR comment posting.
  • Evidence-assisted planning - Plan mode can follow in-scope preflight diagnostics, discover first when evidence is thin, draft from the ask for scoped feature work, or ask clarifying questions when the request is too unclear.
  • Controlled execution - configurable approvals, dangerous-command blocking, workspace trust checks, and pre-write checkpoints.
  • FIM autocomplete - optional VS Code inline suggestions from a generic OpenAI-compatible prompt + suffix endpoint.
  • Model flexibility - echo (local stub), native Anthropic (Claude) and Gemini adapters, plus OpenAI-compatible endpoints (Ollama, LM Studio, OpenRouter, OpenAI, Azure OpenAI, DeepSeek, and any /v1 API).
  • Extensible workflows - built-in tools, MCP servers (VS Code), project rules, and reusable skills.
  • Web retrieval - optional multi-provider web_search (SearXNG / Brave / Tavily via @mitii/search-kit) and content-aware fetch_url (Stack Overflow answers, GitHub issues, Wikipedia, arXiv, HTML readability).
  • Local evidence - session logs and a basic audit-pack export from the VS Code host (settings redacted). Org SSO/RBAC, SIEM webhooks, and managed enterprise policy packs are not implemented yet.

How it works```mermaid

flowchart LR
User[Developer] --> UI[VS Code webview]
UI --> Controller[Runtime controller]
Controller --> Context[Hybrid context engine]
Context --> Index[(SQLite FTS5 + symbols)]
Context --> Vectors[(LanceDB or SQLite vectors)]
Controller --> Pipeline[Classify -> route -> depth -> skills]
Pipeline --> Loop[Ask / Plan / Agent loop]
Loop --> Policy[Tool policy + approvals]
Policy --> Tools[Files, shell, Git, MCP]
Loop --> State[(Plans, memory, logs, checkpoints)]
Loop --> Provider[Local or cloud model]


The extension and CLI talk to the agent through `@mitii/sdk` -> `@mitii/v8`. Hosts inject ports from `@mitii/host` (including `@mitii/search-kit` for web retrieval). See packages/v8/ARCHITECTURE.md and packages/search-kit/ARCHITECTURE.md.

## Quick start

### Requirements

- VS Code 1.124 or newer
- Node.js 20 or newer
- pnpm 10.13 or newer for source development

### Install from source```bash
git clone https://github.com/Mitii-dev/Mitii.git
cd Mitii
pnpm run setup

Press F5 in VS Code to open an Extension Development Host. Open a project, select the Mitii icon, wait for indexing to complete, and choose a provider in Settings.

For Cursor development on macOS:```bash
pnpm run setup:cursor


### Connect a local model

Run an OpenAI-compatible endpoint such as Ollama, then configure:```json
{
  "mitii.provider.type": "openai-compatible",
  "mitii.provider.baseUrl": "http://localhost:11434/v1",
  "mitii.provider.model": "qwen3-coder:30b",
  "mitii.safety.autonomyPreset": "guided",
  "mitii.safety.approvalMode": "review_all"
}

API keys for hosted providers are stored in VS Code SecretStorage rather than workspace settings.

Enable FIM autocomplete

Autocomplete is disabled by default and separate from the Ask/Plan/Agent model path. Leave baseUrl and model empty to inherit the provider settings, or point them at a faster FIM-specific endpoint.```json
{
"mitii.autocomplete.enabled": true,
"mitii.autocomplete.baseUrl": "http://localhost:11434/v1",
"mitii.autocomplete.model": "your-fim-model",
"mitii.autocomplete.endpointPath": "completions"
}


## Example workflow

Ask Mitii:```text
Plan a safe migration of the user cache to Redis. Identify affected files,
tests, rollback steps, and configuration changes. Do not edit files yet.

Review the generated plan, switch to Agent mode, and send:```text
Implement the approved plan and run the relevant tests.


Mitii retrieves relevant context, selects the required capabilities, requests approval for protected actions, checkpoints affected files, applies scoped edits, and runs configured or discovered verification commands.

For repair requests with matching preflight diagnostics, Mitii can skip redundant discovery and start from concrete Change steps tied to the failing files. Optional lightweight model enrichment can improve plan wording, but deterministic policy still owns gates, approvals, grants, and verification requirements.

## Evidence-led execution

Agent runs now carry a structured evidence artifact in addition to plan and task state. The goal is to make every major action accountable without making the live task list the source of truth.

- **Discovery report** records the target, files/searches/commands inspected, bounded discovery capacity, and why discovery stopped.
- **Issue inventory** tracks findings from diagnostics/build/verification as issues rather than just counting files.
- **Plan evidence** records how many plan steps are linked to concrete targets, reviewed context, or verification.
- **Execution ledger** records tool actions, edits, verification commands, and stop decisions with safe summaries and paths.
- **Verification delta** records before/after error counts, remaining issues, checks, and the stop reason when verification is available.

The plan remains the execution contract. Task lists are a derived progress view, useful for UI, but subordinate to plan evidence and verification. Once requested verification passes after edits, the agent should stop and summarize instead of continuing because the model produced transitional narration.

## CLI and SDK

### CLI```bash
pnpm run build:cli
node apps/cli/bin/mitii.js --help
node apps/cli/bin/mitii.js setup --provider ollama --yes
node apps/cli/bin/mitii.js session
node apps/cli/bin/mitii.js ask "Summarize the authentication flow" --echo
node apps/cli/bin/mitii.js index --cwd /path/to/project
node apps/cli/bin/mitii.js status --json

New users: mitii setup writes non-secret provider config, then set an API key in the environment and run mitii session (dotted MITII banner + REPL). See apps/cli/README.md for setup, ask, session, index, status, export-session, and automation commands such as schedule, events, and serve.

SDK

@mitii/v8, @mitii/sdk, @mitii/host, and @mitii/cli publish to npm on v* release tags (see docs/RELEASE.md). For local development, consume them from this monorepo workspace.```ts
import { createMitiiClient, EchoLlmPort } from '@mitii/sdk';

const client = createMitiiClient({
understandingLlm: / host LlmPort /,
runLlm: new EchoLlmPort(),
workspaceRoot: process.cwd(),
defaultMode: 'ask',
});

const run = client.start({
prompt: 'Summarize the authentication flow',
mode: 'ask',
});

for await (const event of run.events) {
if (event.type === 'model_delta' && event.preview) {
process.stdout.write(event.preview);
}
}

await run.result;


The live surface is `createMitiiClient` / `start` / `resume` - not a legacy `query()` helper or `DaemonClient`. More detail: packages/sdk/README.md.

## Local safety controls

Mitii keeps indexes, plans, memory, logs, and checkpoints local by default. Only context sent to the configured model provider crosses that provider boundary.

What exists today:

- approval presets and workspace trust enforcement
- SecretStorage for API keys (VS Code)
- session logs and a basic audit-pack export (redacted settings + run events)
- OpenAI-compatible local endpoints (Ollama / LM Studio) for privacy-sensitive work

Not yet product features: `mitii.enterprise.localProvidersOnly`, signed SIEM/webhook delivery, SSO/OIDC, RBAC, or a dedicated `docs/enterprise/` pack.

## Repository layout```text
mitii-ai-agent/
|-- packages/
|   |-- v8/                   # @mitii/v8 - host-neutral agent runtime
|   |-- sdk/                  # @mitii/sdk - public API + bundled skills/
|   |-- host/                 # @mitii/host - indexing, ports, writing recipes
|   |-- automation/           # @mitii/automation - schedules and claim runner
|   |-- mcp/                  # @mitii/mcp client + @mitii/mcp-web server
|   `-- search-kit/           # @mitii/search-kit - web search/fetch helpers
|-- apps/
|   |-- vscode/               # VS Code extension (F5 target)
|   |-- cli/                  # headless CLI (`mitii`)
|   |-- daemon/               # long-lived automation daemon (`mitii-daemon`)
|   `-- acp/                  # ACP-lite stdio bridge (`mitii-acp`)
|-- tests/                    # solid benchmark (+ package-local specs elsewhere)
|-- docs/                     # developer and release guides (+ automation/)
`-- scripts/                  # build, release, and audit automation

Development```bash

pnpm run build:all # build all packages + Electron SQLite for F5 / indexes
pnpm run build # packages only
pnpm run typecheck
pnpm test
pnpm run package # target-specific VSIX (apps/vscode)
pnpm run package:preflight # release checks, tests, and package


Native modules target different runtimes. `rebuild:native` stages the Electron
binding for F5 and restores the Node ABI in `node_modules`, so tests keep working:```bash
pnpm run rebuild:native     # Electron -> dist/native, then restore Node ABI
pnpm run rebuild:node       # Node-only (tests/CLI)

Vitest scripts auto-heal ABI mismatches via scripts/ensure-node-native.mjs.

See CONTRIBUTING.md for coding conventions and pull request guidance.

Documentation

  • Architecture
  • Repository layout
  • Initial launch / F5
  • Skills format
  • CLI (includes writing recipes)
  • VS Code extension
  • Release / publish units
  • Solid benchmark
  • Tests layout
  • MCP packages
  • Search kit
  • Website
  • Hosted documentation

Contributing and support

Contributions are welcome. Keep changes focused and run pnpm run typecheck and pnpm test before opening a pull request.

  • Issues: github.com/Mitii-dev/Mitii/issues
  • Author: @codewithshinde
  • Email: codewithshinde@gmail.com

License

Mitii AI Agent is licensed under AGPL-3.0-or-later. Contact the maintainer for commercial licensing outside the AGPL terms.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Mitii 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Mitii 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Mitii 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Mitii 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Mitii 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Cline、Gemini CLI、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Mitii 能提供哪些能力?

资料显示能力标签包括 ai、ai agent、vscode、vscode extension、qwen、ollama。具体工具清单以官方文档为准。

Mitii 需要什么运行环境?

运行时为 node。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。