Loutre

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 其他
• 你需要填写：Authorization

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

claude mcp add --transport http loutre https://api.loutre.app/mcp --header 'Authorization: your-value'

{
  "mcpServers": {
    "loutre": {
      "url": "https://api.loutre.app/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "servers": {
    "loutre": {
      "type": "http",
      "url": "https://api.loutre.app/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

• Authorization 机密 HTTP header
  Optional. Bearer la_… (Loutre API token) to list and manage your account's mocks; without it, mocks are created anonymously.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• create_mock

  Create a hosted mock from an OpenAPI 3.0/3.1 or Swagger 2.0 document (YAML or JSON), from TypeScript types (interfaces, types, enums: CRUD routes derived, or a route map type keyed like "GET /users") or from a Postman v2 collection, an Insomnia export (v4 JSON or v5 YAML), a Brun

• list_mocks

  List the connected account's mocks (API token required), with their URL, routes and expiry.

• get_mock

  Details of a mock: routes with identifiers, behaviour, lock, sample generated bodies per route.

• call_mock

  Call a route of the mock like an HTTP client would and return the status, the x-loutre-* headers and the body. The headers x-loutre-status, x-loutre-delay, x-loutre-count, x-loutre-message and x-loutre-seed are honoured; latency is not awaited, it is reported in delayMs. Writes (

• set_behavior

  Change a mock's behaviour: default status, latency, jitter, error rate, persistent writes, and per route status, latency, hand-written bodies, rules. Merge semantics: missing keys are kept, null clears.

• set_response

  Set the JSON body a route returns for a given status (hand-written response); a null body restores the generated response.

• add_rule

  Add a conditional response to a route: when the request matches the conditions (query, header, path param, body field), the mock answers with this status, body and latency. Rules are evaluated in order, the first match wins; x-loutre-* headers keep priority.

• clear_rules

  Remove every conditional rule of a route.

• regenerate_mock

  Generate a new data set (new seed), for the whole mock or for one route and the routes sharing its collection. A full new set forgets persisted writes.

• get_requests

  The latest requests received by the mock, most recent first: method, path, query, status, headers and body as received (body cut at 8 KB), where the answer came from, latency. Each entry has an id for replay_request.

• replay_request

  Replay a request from the log exactly as it was received (same method, path, headers and body) against the mock as it is now, and return the answer. Useful after changing a rule, a body or a scenario.

• clear_requests

  Empty the mock's request log.

• sync_mock

  Re-read the schema at the mock's source URL now and update the mock if it changed (routes, fields; settings kept, persisted writes forgotten). force regenerates even when the document is unchanged.

• set_domain

  Serve the mock under the account's own hostname (Pro): declares it at Cloudflare and returns the CNAME to create (hostname → target) plus the current status; call again without hostname to re-check, or with hostname null to remove it.

• reset_state

  Forget persisted writes (POST, PUT, PATCH, DELETE): the generated collections come back as they were.

• set_access

  Lock a mock with a token (private) and/or restrict the allowed browser origins. Pro plan.

• delete_mock

  Permanently delete a mock and its kept schema.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

• ! 注意

  作者与仓库一致

  注册中心没有列出源代码仓库，因此无法将发布者（loutre.app）与代码对应起来

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 321 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 17 个工具描述，未发现针对 AI 的隐藏指令

与“其他”中的其他服务器比较i

• 星标数多于此分类中其他 32505 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 32505 个服务器的 89% 更新
• 基础检查结果等于或优于此分类中其他 32505 个服务器的 37%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

仓库中没有找到 README