OnlyWorlds

它能帮你做什么

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

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

安装

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

你需要

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

你用的是哪个应用？

claude mcp add --transport http onlyworlds https://www.onlyworlds.com/mcp --header 'API-Key: your-value' --header 'API-Pin: your-value'

{
  "mcpServers": {
    "onlyworlds": {
      "url": "https://www.onlyworlds.com/mcp",
      "headers": {
        "API-Key": "your-value",
        "API-Pin": "your-value"
      }
    }
  }
}

{
  "servers": {
    "onlyworlds": {
      "type": "http",
      "url": "https://www.onlyworlds.com/mcp",
      "headers": {
        "API-Key": "your-value",
        "API-Pin": "your-value"
      }
    }
  }
}

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

需要你填写的值

• API-Key 机密 HTTP header
  A world's API key: an ow_w_ write key, an ow_r_ read key, an agent seat's key, or a legacy 10-digit key. The schema tools need no key.
• API-Pin 机密 HTTP header
  The PIN, needed for writes: your account PIN, or an agent seat's ow_s_ secret. Reads with an ow_w_ or ow_r_ key need no PIN.

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

它能做什么

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

• list_element_types

  List all 22 OnlyWorlds element types with a one-line shape summary of each. Every world is built from these types; each element has a stable UUID `id`, a `name`, and a `type`. Use `get_element_schema(type)` for a type's full field list. Unauthenticated — schema is public referenc

• get_element_schema

  Return the field structure of one OnlyWorlds element `type` (a slug from `list_element_types`, e.g. "character"). The result groups the type's writable fields by kind so a caller knows how to read and write them: `text` (strings), `integer`, `single_link` (one UUID), `multi_link`

• search_schema

  Search every element type's fields for `query` (case-insensitive substring), across all 22 types. Useful for "which types have a `location` field?" or finding where a concept lives in the schema. Returns a mapping of type slug -> the matching field names in that type (types with

• list_worlds

  The worlds you can read here. With an API-Key: the key's one world. Signed in through a hosted client (a bearer), where this server offers one: every world your account owns or is a member of, as your account's world list shows them; pass one's `id` (or its `slug`) as `world` to

• list_elements

  List elements of one `type` in the world named by your API-Key header, newest-created first. `type` is a slug from `list_element_types` (e.g. "character"). Optional `name_contains` filters by case-insensitive name substring; `supertype` is trimmed and matched without regard to ca

• get_element

  Fetch one element by `type` and `id` (a UUID) from the world named by your API-Key header. `type` is a slug from `list_element_types`. Returns the full v2 wire shape (the same body as `GET /api/v2/{type}/{id}`): `type`, `id`, `name`, scalar fields, link fields as UUID arrays, and

• search_elements

  Search the world named by your API-Key header for elements whose name or text fields (description and each type's prose fields, such as a Character's background) hold every word of `query` as a whole word, ignoring case: "ore" does not find "more", and "copper mine" needs both wo

• get_changes

  Return the delta feed for the world named by your API-Key header: every element created/updated (`op: "upsert"`, full body) or deleted (`op: "delete"`) since `since_cursor`, in apply order, in pages of `limit` (default 25, max 1000). Entries carry FULL element bodies — a default

• get_draught

  What one Character knows, in one read: the draught. `id` is the Character's UUID; `policy` is one JSON object, every key optional: `components` (a list, or a comma string, of self, role, work, style, events, knowledge, names, sheet, recent, messages, room, proposed, roster; defau

• list_files

  List the files attached to one element (`type` and `id`, a UUID) in the world named by your API-Key header: PDFs, text files and world bundles kept on onlyworlds.com beside the element, never inside it. Returns `{data: [{id, name, kind, size, label, added_by, added_at}, ...]}`, n

• read_file

  Read one file attached to an element, by its id (from `list_files`). A text file (txt, md, json, csv, yaml, toml) answers its words, at most 64 KB per call (`truncated: true` past that), in `text`, which always begins with one line saying who added it and when, and that a file is

• create_element

  Create one new element of `type` in the world named by your API-Key header. `type` is a slug from `list_element_types` (e.g. "character"). `element` is the field payload: `name` plus any scalar, link, or extension fields for that type (call `get_element_schema(type)` for the fiel

• update_element

  Update an existing element by `type` and `id`, changing ONLY the fields you pass — omitted fields are preserved. This is a server-side read-merge: the current element is loaded and only the keys in `fields` are applied, so it is safe against the raw-HTTP-PATCH hazard where sendin

• edit_links

  Add and/or remove links on ONE multi-link `field` of an element, leaving the rest of that field's array untouched. Use this for additive/subtractive link edits (unlike `update_element`, which REPLACES a link array). `type` is a slug from `list_element_types`; `id` is the element'

• bulk_apply

  Create and/or update many elements across any of the 22 types in one call. Each entry in `items` is `{"type": , "element": }` with the same payload shape `create_element` takes: an `element` with an `id` UPDATES that id (creating it if absent), an `element` without an `id` CREATE

• get_image_upload_ticket

  Get a ticket to upload ONE image into this world, for an element's `image_url` (Keel #59). The image never passes through this tool: you send its bytes yourself, straight to the image host, with the ticket. Steps: 1. Call this tool. You get `ticket`, `upload_url`, `max_bytes` and

基础检查i

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

• ! 注意

  作者与仓库一致

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

• … 尚未检查

  仍在维护

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

• … 尚未检查

  有许可证

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

• ✓ 通过

  端点有响应

  在 114 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

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

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

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

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

替代选择

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

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

作者的 README

仓库中没有找到 README