Loocor's recent timeline updates
Loocor's repos on GitHub
Swift · 668 watchers
codmate
CodMate is a macOS SwiftUI app for managing CLI AI sessions: browse, search, organize, resume, and review work produced by Codex, Claude Code, and Gemini CLI. It focuses on speed, a compact three-column UI, and “ship it” workflows like Project Review (Git Changes) and one-click Resume/New.
TypeScript · 39 watchers
db2llm
DB2LLM is a minimal prototype that combines SQLite database metadata with RESTful APIs and large language models (LLMs). It allows users to interact with databases using natural language, without writing SQL queries or understanding database structures
Rust · 34 watchers
mcpmate
MCPMate is a progressive MCP management center for organizing servers, clients, profiles, capabilities, and runtime visibility in one local workspace.
JavaScript · 3 watchers
codex-helper
Codex Helper is a lightweight local enhancement launcher for Codex desktop.
3 watchers
MitmRust
High-performance MITM proxy built in Rust. 10x faster than mitmproxy with async runtime and zero-copy design.
TypeScript · 1 watchers
Aether
Aether 是一个基于 VSCode 插件生态打造的 AI 代理(Agent)调度与运行平台,旨在通过模块化的架构与工具集成,实现类似现实世界团队协作的仿生智能体组织。它通过明确的角色分工和自动化的任务执行,使 AI 能够高效处理复杂任务
JavaScript · 1 watchers
fmsapi
Node wrapper for FileMaker Data API.
TypeScript · 1 watchers
opencode
The open source coding agent.
JavaScript · 1 watchers
scrollinput
A simple number input demo which based on smooth-scrollbar and jQuery.
0 watchers
A2UI
Python · 0 watchers
ai-marketing-codex
AI Marketing Suite for Claude Code. 15 marketing skills with parallel subagents — audit any website, generate copy, email sequences, ad campaigns, content calendars, competitive intelligence, and client-ready PDF reports.
Rust · 0 watchers
ai-toolbox
Personal AI Toolbox
0 watchers
api2mcp
0 watchers
cc-switch
A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Gemini CLI & Hermes Agent. Only official website: ccswitch.io
Rust · 0 watchers
cherry-db-bridge
A Rust library for managing Cherry Studio LevelDB configurations, specifically designed for handling MCP (Model Context Protocol) server configurations.
Swift · 0 watchers
CliMate
TypeScript · 0 watchers
codex-plugins
Unified Codex plugin marketplace for Loocor plugins
Swift · 0 watchers
deeplinker
0 watchers
delivery
Um aplicativo de delivery feito em flutter com GetX, GraphQL, GetStorage, Dio etc. Utilizando Strapi como Backend
0 watchers
fileMakerAC
A template for FileMaker Account & Access Config management
0 watchers
FluidVoice
Voice-to-text macOS App - Fully local
Dart · 0 watchers
flutter_cool_alert
A flutter package to display animated dialods
HTML · 0 watchers
fm-dash-gen
FileMaker Documentation Generator to HTML/Dash
Shell · 0 watchers
go-zero-doc
the source of gitbook
TypeScript · 0 watchers
gstack
Use Garry Tan's exact Claude Code setup: 15 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA
TypeScript · 0 watchers
homebrew-tap
0 watchers
iGuard
iGuard 是一个全国学生视力筛查管理系统,专注于儿童近视防控。支持数据采集、AI 分析和安全管理,促进学校、家长与机构协作。通过多端访问,实现从筛查到干预的全流程,提升眼健康水平
0 watchers
loocor
loocor's GitHub profile
TypeScript · 0 watchers
mcp-umate-ai
0 watchers
MoePeek
A lightweight macOS selection translator built with pure Swift 6, featuring on-device Apple Translate for privacy, only 5MB install size and stable ~50MB memory usage. 一款轻量级 macOS 划词翻译工具,纯 Swift 6 开发,设备端 Apple 翻译保护隐私,安装体积仅 5MB,后台运行内存稳定约 50MB
0 watchers
openclaw
Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞
Rust · 0 watchers
redber
TypeScript · 0 watchers
rules-editor
Open-source Rules Engine editor with Simulator
Go · 0 watchers
rules-sample
Rust · 0 watchers
rust-sdk
The official Rust SDK for the Model Context Protocol
0 watchers
service-manager-rs
Provides adapters to communicate with various operating system service managers like launchd and systemd
0 watchers
swift-bridge
swift-bridge facilitates Rust and Swift interop.
Swift · 0 watchers
SwiftTerm
Xterm/VT100 Terminal emulator in Swift
0 watchers
taro-ui
一款基于 Taro 框架开发的多端 UI 组件库
0 watchers
tiberius
TDS 7.2+ (Microsoft SQL Server) driver for Rust
Dockerfile · 0 watchers
zero-env
“抄袭” gonivinck 的本地 golang 开发环境配置
Loocor

Loocor

V2EX member #16476, joined on 2012-02-08 10:59:02 +08:00
23 S 1 B
CodMate & MCPMate 作者,AI 粉,野生编程爱好者
当 MCP Server 变了,用户原来的设置还算数吗?
程序员  •  Loocor  •  3 days ago  •  Lastly replied by Loocor
1
CodMate:给 Codex 重度用户的免费工具
分享发现  •  Loocor  •  Dec 30, 2025  •  Lastly replied by Loocor
10
今天退订了 cc 的镜像服务,感觉挺不好意思
Claude  •  Loocor  •  Jul 18, 2025  •  Lastly replied by Loocor
3
自己的第一个开源项目 db2llm
程序员  •  Loocor  •  Mar 11, 2025  •  Lastly replied by Loocor
15
taro 好像烂尾了
程序员  •  Loocor  •  Mar 15, 2025  •  Lastly replied by tinyhill
21
中年如何提升体能啊
健康  •  Loocor  •  Dec 16, 2024  •  Lastly replied by Loocor
144
Loocor's recent replies
以下内容只是正文事实与筛查结论的证据索引。状态敏感的来源需要在实际发布日期再次核验。

- **Claude Code:**[权限配置]( https://code.claude.com/docs/en/permissions)
- **Claude Code:**[通过 MCP 连接工具]( https://code.claude.com/docs/en/mcp)
- **Exa MCP Server:**[窗口起点代码提交]( https://github.com/exa-labs/exa-mcp-server/commit/0d24063b065878797114ac81d9541c7dcad98d4d)
- **Exa MCP Server:**[起点的 10 个 Tool 注册项]( https://github.com/exa-labs/exa-mcp-server/blob/0d24063b065878797114ac81d9541c7dcad98d4d/src/index.ts#L26-L36)
- **Exa MCP Server:**[PR #225:弃用冗余 Tool]( https://github.com/exa-labs/exa-mcp-server/pull/225)
- **Exa MCP Server:**[PR #225 合并提交]( https://github.com/exa-labs/exa-mcp-server/commit/092d96750ac4dca856fbb36af05c2c9beaf60760)
- **Exa MCP Server:**[PR #273:将 crawling 改名为 web_fetch 并保持向后兼容]( https://github.com/exa-labs/exa-mcp-server/pull/273)
- **Exa MCP Server:**[改名前的代码版本]( https://github.com/exa-labs/exa-mcp-server/commit/4c93ef879d16d2fba7908ab3e82041092697b5a7)
- **Exa MCP Server:**[最初的改名提交]( https://github.com/exa-labs/exa-mcp-server/commit/77049677f3c663a60fced708147e6f67530295cd)
- **Exa MCP Server:**[增加弃用别名的提交]( https://github.com/exa-labs/exa-mcp-server/commit/18830c1c0a7560963b2af34dc98079a38f473b59)
- **Exa MCP Server:**[改名后的合并版本]( https://github.com/exa-labs/exa-mcp-server/commit/8df65b05f133299fb0342e22e3f013aea85bf01e)
- **Exa MCP Server:**[PR #280:移除 `code_search_help` Prompt]( https://github.com/exa-labs/exa-mcp-server/pull/280)
- **Exa MCP Server:**[移除 Prompt 的代码提交]( https://github.com/exa-labs/exa-mcp-server/commit/bdd0e16fdebda7848165c86b622682cd35d6ab3a)
- **Exa MCP Server:**[PR #383:合并 Agent Tool]( https://github.com/exa-labs/exa-mcp-server/pull/383)
- **Exa MCP Server:**[合并 Agent Tool 的代码提交]( https://github.com/exa-labs/exa-mcp-server/commit/b4436d9487e2d0461dfde705b2c1884db1907fb9)
- **Exa MCP Server:**[窗口终点代码提交]( https://github.com/exa-labs/exa-mcp-server/commit/0de23f94b7e8539192bdc2008c16592156ada870)
- **Exa MCP Server:**[Issue #275:托管默认能力面与文档不一致]( https://github.com/exa-labs/exa-mcp-server/issues/275)
- **Exa MCP Server:**[Issue #275:维护者说明]( https://github.com/exa-labs/exa-mcp-server/issues/275#issuecomment-4210439834)
- **Exa MCP Server:**其他用户报告 [Issue #48]( https://github.com/exa-labs/exa-mcp-server/issues/48)
- **Exa MCP Server:**其他用户报告 [Issue #66]( https://github.com/exa-labs/exa-mcp-server/issues/66)
- **Exa MCP Server:**其他用户报告 [Issue #77]( https://github.com/exa-labs/exa-mcp-server/issues/77)
- **Exa MCP Server:**其他用户报告 [Issue #84]( https://github.com/exa-labs/exa-mcp-server/issues/84)
- **GitHub MCP Server:**[PR #1563:支持安全改名]( https://github.com/github/github-mcp-server/pull/1563)
- **GitHub MCP Server:**[安全改名的合并提交]( https://github.com/github/github-mcp-server/commit/94ee0745ca46be7e45a4d1a856ec3183cca67aee)
- **GitHub MCP Server:**[关于别名生命周期的审查意见]( https://github.com/github/github-mcp-server/pull/1563#issuecomment-3642737423)
- **GitHub MCP Server:**[PR #1652:GitHub Actions Tool 别名]( https://github.com/github/github-mcp-server/pull/1652)
- **GitHub MCP Server:**[GitHub Actions 别名的合并提交]( https://github.com/github/github-mcp-server/commit/63c7db030a081b0ff1a4de7ab10f237da4fac491)
- **GitHub MCP Server:**[将合并后的工具集设为默认值]( https://github.com/github/github-mcp-server/commit/0a62aabc94dd5c84dd076fcdde9601e637088b61)
- **GitHub MCP Server:**[移除旧的独立实现]( https://github.com/github/github-mcp-server/commit/3c53687eb35a5fe880df9f2efbf11abe9a99388c)
- **GitHub MCP Server:**[固定版本的 Tool 改名指南]( https://github.com/github/github-mcp-server/blob/eb088dfe9d854dab6453a8d4ae5871a5ced20974/docs/tool-renaming.md)
- **GitHub MCP Server:**[固定版本的弃用别名映射]( https://github.com/github/github-mcp-server/blob/eb088dfe9d854dab6453a8d4ae5871a5ced20974/pkg/github/deprecated_tool_aliases.go)
- **Context7:**[PR #2524:从 `query-docs` 移除 `researchMode`]( https://github.com/upstash/context7/pull/2524)
- **Context7:**[移除 `researchMode` 的代码提交]( https://github.com/upstash/context7/commit/ff6c1bef4b8491b8ded7920a8c63e1e1d9a374a3)
- **Context7:**[Issue #2527:可选列表处理器兼容问题]( https://github.com/upstash/context7/issues/2527)
- **Context7:**[维护者的复现请求]( https://github.com/upstash/context7/issues/2527#issuecomment-4516905204)
- **Context7:**[修复确认]( https://github.com/upstash/context7/issues/2527#issuecomment-4648908444)
- **Context7:**[PR #2534:增加空的 Prompts/Resources 处理器]( https://github.com/upstash/context7/pull/2534)
- **Context7:**[空处理器的合并提交]( https://github.com/upstash/context7/commit/fcdc36e2459ab0e4512f3dd108a2bbb0b5165720)
- **MCP 官方讨论与规范:**[PR #701:Tool 名称冲突指引]( https://github.com/modelcontextprotocol/modelcontextprotocol/pull/701)
- **MCP 官方讨论与规范:**[SEP-986:Tool 名称格式]( https://github.com/modelcontextprotocol/modelcontextprotocol/issues/986)
- **MCP 官方讨论与规范:**[PR #1603:Tool 名称格式]( https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1603)
- **MCP 官方讨论与规范:**[SEP #1292:使用 URI 作为命名空间]( https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1292)
- **MCP 官方讨论与规范:**[SEP #1413:限定名称连接符]( https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1413)
- **MCP 官方讨论与规范:**[SEP-1575:Tool 语义版本]( https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1575)
- **MCP 官方讨论与规范:**[PR #1602:Tool 语义版本草案]( https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1602)
- **MCP 官方讨论与规范:**[Issue #1915:Tool 版本与命名模式]( https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1915)
- **MCP 官方讨论与规范:**[SEP-1766:由摘要固定的 Tool 版本]( https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1766)
- **MCP 官方讨论与规范:**[SEP-1766:范围收窄说明]( https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1766#issuecomment-4211174323)
- **MCP 官方讨论与规范:**[SEP-1766:版本、摘要与策略的边界]( https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1766#issuecomment-4211316602)
- **MCP 官方讨论与规范:**[PR #2636:渐进式 Tool 披露]( https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2636)
- **MCP 官方讨论与规范:**[PR #2912:安全兴趣小组章程]( https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2912)
- **MCP 官方讨论与规范:**[Issue #2580:Server 显示名称]( https://github.com/modelcontextprotocol/modelcontextprotocol/issues/2580)
- **MCP 官方讨论与规范:**[Issue #2842:Server 身份回归问题]( https://github.com/modelcontextprotocol/modelcontextprotocol/issues/2842)
- **MCP 官方讨论与规范:**[MCP 2026-07-28 候选发布版]( https://blog.modelcontextprotocol.io/posts/2026-07-28-release-candidate/)
- **MCP 官方讨论与规范:**[冻结的官方代码仓库快照]( https://github.com/modelcontextprotocol/modelcontextprotocol/commit/7634684382c3d14cf7e9f14073fe40a2d8ace3fa)
- **MCP 官方讨论与规范:**[MCP 规范草案]( https://modelcontextprotocol.io/specification/draft)
- **MCP 官方讨论与规范:**[当前正式规范入口]( https://modelcontextprotocol.io/specification)
- **Firecrawl:**[Issue #113]( https://github.com/firecrawl/firecrawl-mcp-server/issues/113)
- **Firecrawl:**[Issue #130]( https://github.com/firecrawl/firecrawl-mcp-server/issues/130)
- **Firecrawl:**[PR #294]( https://github.com/firecrawl/firecrawl-mcp-server/pull/294)
- **Cloudflare:**[Radar 弃用 PR #375]( https://github.com/cloudflare/mcp-server-cloudflare/pull/375)
- **Cloudflare:**[增加 Browser Rendering Tool 的 PR #407]( https://github.com/cloudflare/mcp-server-cloudflare/pull/407)
- **Notion:**[Markdown Tool PR #320]( https://github.com/makenotion/notion-mcp-server/pull/320)
- **Notion:**[托管服务契约用户报告 #216]( https://github.com/makenotion/notion-mcp-server/issues/216)
- **XcodeBuildMCP:**[启动参数契约变化 PR #403]( https://github.com/getsentry/XcodeBuildMCP/pull/403)
- **Playwright MCP:**[Verification Tools 文档 PR #957]( https://github.com/microsoft/playwright-mcp/pull/957)
@germain 😂 那到底是爽到了没有
@iintothewind 我们整体观点是一致的,尽管这些能力方式各有所长,但最终还是 Agent 的设计起了决定性作用。

有两个细节表述上的差异,可以再对齐一下理解:

一是 cli 结构化输出能力应该是具备的,mcporter 是个典型的应用体现,它的 changelog 里好像有专门提及这个增强,避免了你说的需要 Agent 自己去解析字符串的问题,还是比较可靠;
二是 mcp 全量进入 context window 以及单个 tool 需求但装个全家桶这两个问题现在基本都有解决方案了,只是可能还不够普及,即前面回复提到的 smart tools selection 或叫做 meta tools 提供近似的延迟加载,以及 ClaudeCode 等也具备 allow 或 disallow 这类黑白名单控制指定的 tools 是否加载。我在自己的 mcpmate 里使用了 profile 的概念,也是细化到具体能力清单这个层级进行启停管控的,所以“要一个但装全部”的问题都可以解决,说到底还是是 mcp server 和 mcp host app 具体实现的问题;
@mmdsun 对,现在这种 smart tools selection 的模式几乎已经成为共识了,但在去年整半年都是被拉踩的短处。我们在 mcpmate 里也用了类似的实现,catalog 、details 、call 三个 meta 工具配合,访问后端所有的能力,包括但不限于 tools 、prompts 、resources 。其中就用到了你说的那种前缀,不过我们把这个环节做的更严格一些,作为 namespace 贯穿整个过程。
@cybort 嗯,我感觉用户端特别是个人用户其实现在都不怎么待见 mcp 的
@germain 不是 Claude ,workbuddy 里 DeepSeek 和 glm 写的,都发了才发现还有些细节问题。没关系,表达个意思,中心思想和观点是我的就行 😄
跟 cc-switch 是不是一类,这类太卷了怎么敢做的,而且似乎也很难变现啊
漂亮!
raycast 一直都是 web 套壳...
aHR0cHM6Ly9jb2RleHpoLmNvbS8/cmVmPUY1QjZENA== 这里也还行,目前我在用。注意这个有我的邀请码,不喜欢的话自己清除了再访问
About   ·   Help   ·   Advertise   ·   Blog   ·   API   ·   FAQ   ·   Solana   ·   1403 Online   Highest 6679   ·     Select Language
创意工作者们的社区
World is powered by solitude
VERSION: 3.9.8.5 · 22ms · UTC 17:04 · PVG 01:04 · LAX 10:04 · JFK 13:04
♥ Do have faith in what you're doing.