OpenSEO
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Private memory, documents, voice and a local LLM for your agents, served by a Mac app on-device.
选择你使用的 AI 应用,然后复制设置。
通过 2/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
ChatGPT 暂时无法连接 M1K3
开发者尚未在 MCP 注册表中填写安装方式
Claude Code 暂时无法连接 M1K3
开发者尚未在 MCP 注册表中填写安装方式
Cursor 暂时无法连接 M1K3
开发者尚未在 MCP 注册表中填写安装方式
VS Code 暂时无法连接 M1K3
开发者尚未在 MCP 注册表中填写安装方式
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月15日
注册名称已通过域名 m1k3.app 验证(注册中心会核实域名所有权)
代码最后更新于昨天
GitHub 无法识别许可证类型;请打开文件自行查看
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于昨天,最新版本(1.0.0)于43天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。
同一分类中有:OpenSEO, Exa, Mockserver, Microsoft Learn MCP, Docs
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Mock, record/replay, verify and chaos-test any HTTP, REST, gRPC or LLM dependency over MCP.
Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The flagship surface: a Mac-native SwiftUI app — on-device MLX inference, live voice (Kokoro TTS + WhisperKit STT), a personal knowledge graph with RAG, an embedded agent, a 3D companion, and a local MCP server other agents can call.
Private by design. M1K3 runs on your Mac. Models download once from Hugging Face; after that the only network use is web search, which is on by default so answers can be current, with one switch in Settings to turn it off. (An opt-in Apple Private Cloud Compute rung arrives in a later release; the 1.0 build has no cloud path.)
brew install xcodegen xcbeautifygit clone https://github.com/Round-Tower/M1K3.git
cd m1k3/macos
xcodegen generate
open M1K3.xcodeproj # then ⌘R (set your own dev team for local signing)
Or from the command line:
xcodebuild -scheme M1K3 -destination 'platform=macOS' build | xcbeautify
xcodebuild -scheme M1K3iOS -destination 'generic/platform=iOS Simulator' build | xcbeautify xcodebuild -scheme M1K3visionOS -destination 'generic/platform=visionOS Simulator' build | xcbeautify
First launch is one screen: say hello (a name is optional) and you're talking — M1K3 starts on Mini, Apple's built-in on-device model, so there's nothing to download. Sharper local brains (Lil / Big) are one click away in Settings, or via the in-chat offer after your first answer; weights download only when you ask.
Signing note: run with your personal development team. Building with
CODE_SIGNING_ALLOWED=NOcompiles fine (CI does it) but the app then runs
without its sandbox container and will read/write the wrong data locations.
The business logic lives in SwiftPM packages and tests without Xcode:
swift test --parallel --disable-xctest # the full fast suite (CI runs it without the flag)
tools/dev/tdd.sh M1K3KnowledgeTests # one test target, rebuilt and run alone
Tests use swift-testing (import Testing, @Test), not XCTest.
Heavy MLX/Metal integration tests are env-gated off by default — M1K3_MLX_INTEGRATION=1 swift test opts in (downloads a real model and generates; Apple Silicon only).
M1K3App/ | macOS app shell: SwiftUI views, AppEnvironment, settings |
M1K3iOSApp/ | iOS + visionOS SwiftUI shell (M1K3iOS/M1K3visionOS schemes) on the shared Sources/ graph |
Sources/ | SwiftPM modules: agent, inference, knowledge/RAG, voice, MCP |
Tests/ | swift-testing suites per module |
project.yml | XcodeGen spec (the .xcodeproj is a build artifact) |
ROADMAP.md | What's next — kept current |
PLAN.md | Historical build log / decision record (append-only, signed) |
docs/ | ADRs, model choices, MCP setup, release pipeline |
The running app serves MCP over HTTP at http://127.0.0.1:4242/mcp — knowledge search, documents, voice, and ask_m1k3 (ask the resident AI). See docs/MCP_SETUP.md to wire it into Claude Code or any MCP client.
See CONTRIBUTING.md at the repo root. Found a bug? In the app: Settings → Report an issue… generates a redacted diagnostic you can attach to a GitHub issue.