meticulous

MCP开发工具

提供方 Meticulous · 包名 skills

开发工具 stdio · 本地进程 OAuth 授权 社区 / 第三方 ClaudeCursorVS CodeCodex
查看接入方式

由 Meticulous 提供的 MCP 服务器,stdio · 本地进程。

一句话选型结论

按资料字段整理

meticulous 属于开发工具类 MCP 服务器,stdio · 本地进程,OAuth 授权,可直接接入 Claude、Cursor、VS Code 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

testing frontend

支持客户端

适用场景

testingfrontend

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
npx skills add alwaysmeticulous/skills --skill "*" --agent claude-code --agent codex --agent cursor -y

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

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

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
meticulous当前 未标注 stdio · 本地进程 本地部署 有 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Meticulous上游标注的维护方 Meticulous
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时skills · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

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

Meticulous Agent Skills

A collection of agent skills for Meticulous — the automated visual regression testing platform for web frontends.

These skills enable AI coding assistants (Cursor, Claude Code, etc.) to use Meticulous: review test runs, investigate replays, debug diffs, etc.

Setup

Full setup instructions live in the Meticulous docs: app.meticulous.ai/docs/agents/setup. They cover installing the CLI, authenticating, and installing these skills.

The short version:```bash

1. Install/update the Meticulous CLI

npm install --global @alwaysmeticulous/cli@latest

2. Authenticate (opens a browser to sign in and pick a default project)

meticulous auth login

3. Install these skills into your project

npx skills add alwaysmeticulous/skills --skill "*" --agent claude-code --agent codex --agent cursor -y


### Claude Code plugin

This repository is also packaged as a Claude Code plugin, which installs all the skills below (namespaced as `/meticulous:`) and automatically connects the hosted Meticulous MCP server. To install, run in Claude Code:```shell
/plugin marketplace add alwaysmeticulous/skills
/plugin install meticulous@meticulous

Then type /mcp and choose Authenticate for the Meticulous MCP server (login happens in your browser; not needed if you already authenticate via meticulous auth login for the CLI).

Codex plugin

This repository is also packaged as a Codex plugin, which installs all the skills below and automatically connects the hosted Meticulous MCP server. To install, run:```bash
codex plugin marketplace add alwaysmeticulous/skills
codex plugin add meticulous@meticulous


Then run `codex mcp login meticulous` to authenticate the MCP server (login happens in your browser). To pick up later changes, run `codex plugin marketplace upgrade meticulous`.

### Cursor Marketplace

This repository is also packaged as a Cursor plugin. Once listed in the Cursor Marketplace, Cursor users can install Meticulous skills from **Customize → Plugins** (or search the marketplace) without using `npx skills`. The plugin also automatically connects the hosted Meticulous MCP server: authenticate it from Cursor's MCP settings (login happens in your browser). If you added the Meticulous MCP server to Cursor by hand before, remove that entry so its tools aren't listed twice. The `npx skills` flow above remains the recommended path when you need the same skills across multiple agents.

## Skills

Skills are Markdown files that provide AI coding assistants with domain-specific knowledge and step-by-step workflows. When an agent reads a skill, it gains targeted expertise for a specific task — without needing that context baked into every conversation.

Skills follow the `SKILL.md` format used by Cursor and Claude Code.

| Skill                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Review skills**                                                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| `meticulous-review`                       | Work through a Meticulous test run's results, reacting to their review state — review the unreviewed diffs against what the PR is meant to change and flag potential regressions; when you're working on the PR's code, hand what needs fixing to `meticulous-fix`. Use whenever a run's results matter: reviewing a pull/merge request, right after pushing a frontend change, when its Meticulous CI check is failing or pending, or when asked to look at Meticulous results.     |
| `meticulous-fix`                             | Fix the visual diffs that have been reviewed and rejected on a test run, following their review comments if given. Use when a user has reviewed the results of a test run and is handing off to an agent to implement the fixes, or when `meticulous-review` hands off what needs fixing.                                                                                                                                                                                            |
| `meticulous-test`                           | Run a Meticulous test run after implementing a frontend change, then hands off to the `meticulous-review` skill to classify each visual change as intended or unintended.                                                                                                                                                                                                                                                                                                            |
| `meticulous-zero-diff-task`       | Implement a task for which no visual diffs are expected end to end, using Meticulous as the loop you iterate against until the diff is clean, then open a PR. Use when the task's whole premise is "the UI shouldn't change" — a dependency/version upgrade, a code refactor, a migration, or similar.                                                                                                                                                                               |
| `meticulous-increase-coverage` | Increase coverage for a Meticulous project by tracing specific under-covered files back to a real UI action in the codebase, driving that action with a real recorded browser session, and validating the improvement with a clean coverage comparison. Also opens a PR proposing `.meticulousignore` entries for code that structurally never executes in-browser. Use when asked to "increase coverage", "find untested code", or "add `.meticulousignore` entries" for a project. |
| `meticulous-iterative-dev`         | Iterative frontend development loop using Meticulous for per-step visual validation. Use when implementing a multi-step frontend change and want to catch visual regressions and unintended side effects at each step, before the final cloud test run.                                                                                                                                                                                                                              |
| `meticulous-simulate-and-diff` | Run a Meticulous session simulation against a live URL and analyze the visual output — either by inspecting screenshots directly (quick-check mode) or by comparing pixel and HTML diffs against a base replay. Use when checking whether a code change has introduced visual regressions for a specific session.                                                                                                                                                                    |
| `meticulous-use-session-data`   | Download and use structured Meticulous session data (user flows + network mocks) for testing code changes locally. Use when you need to understand what user interactions and API calls a test covers, or when you want network mocks for writing tests.                                                                                                                                                                                                                             |
| `meticulous-improve-test-env`   | Work out what to change in a project's test environment so Agent swarm stops getting blocked when it tests against a live backend — seed better test data, widen the test user's permissions, enable feature flags, fix test login. Reads the setup blockers Agent swarm has recorded, inspects the codebase and test-environment configuration, and proposes concrete fixes.                                                                                                        |
| **Supporting skills**                                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| `meticulous-cli`                             | Overview of the Meticulous CLI tool and its global options. Use when asking about the meticulous CLI in general, available commands, or global flags that apply to all commands.                                                                                                                                                                                                                                                                                                     |
| `meticulous-cli-update`               | Check whether the Meticulous CLI (@alwaysmeticulous/cli) and skills are installed and up to date, and install/update them if not. Invoked at the start of every other Meticulous skill, since the CLI and skills are under active development with frequent changes and improvements.                                                                                                                                                                                                |

## Contributing

All Markdown, JSON and YAML in this repository is formatted with
oxfmt, and CI enforces it:```bash
pnpm install
pnpm format        # format in place
pnpm check-format  # what CI runs

This isn't only about house style. Skills from this repository get installed
into other repositories (via npx skills add), some of which run oxfmt over
their whole tree — including the installed skill files. If a skill isn't
already oxfmt-clean at the source, their formatter rewrites it on the way in,
the installed copy no longer matches the upstream hash recorded in
skills-lock.json, and every subsequent npx skills update there fights the
formatter. Keeping the source formatted the same way avoids that entirely, so
.oxfmtrc.json here mirrors the settings used in the repositories these skills
are consumed from (notably printWidth: 80).

License

ISC © Meticulous, Inc.

常见问题

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

在客户端按下面的安装命令接入:npx skills add alwaysmeticulous/skills --skill "*" --agent claude-code --agent codex --agent cursor -y。对应的包名是 skills。装完在客户端配置里引用同一个包或端点。

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

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

meticulous 收费吗?

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

meticulous 需要 API Key 吗?

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

meticulous 支持哪些客户端?

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

meticulous 能提供哪些能力?

资料显示能力标签包括 testing、frontend。具体工具清单以官方文档为准。

meticulous 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

meticulous 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

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

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