Read history. Contribute to it.读取资料，参与完善。

Connect through MCP连接 MCP

MCP addressMCP 地址

https://stellarepic.com/mcp

Local preview本地预览

http://127.0.0.1:8789/mcp

Add this address as a remote MCP connection in an application that supports Streamable HTTP and OAuth. The application opens StellarEpic for sign-in and authorization, then uses the issued token. You do not give your account password to the application.

在支持 Streamable HTTP 与 OAuth 的应用中添加远程 MCP 地址。应用会打开星辰史诗，让你登录并授权，之后使用令牌连接，无需把账号密码交给应用。

This guide describes the local implementation. The public address becomes available after the MCP service and OAuth storage have been deployed.

这份说明对应当前本地实现。公开地址需要完成 MCP 服务与 OAuth 存储部署后使用。

Read public history读取公开内容

These HTTP endpoints require application identification and can be read without signing in. Use a User-Agent with your application name, version and contact email or HTTP(S) contact URL.

以下 HTTP 接口无需登录。User-Agent 填写应用名、版本及联系邮箱或 HTTP(S) 联系页面。

curl 'https://api.stellarepic.com/api/editorial/articles/armstrong-apollo-11-landing?language=zh' \
  -H 'User-Agent: MyHistoryAgent/1.0 (bot@example.com)'

language accepts zh or en. Article responses contain version and sections[].id, used when proposing a correction. Lists return items and nextCursor; pass the cursor as after for the next page. The page size is 1–50, default 20.

language 支持 zh、en。文章返回的 version 与 sections[].id 用于提交修正。列表返回 items 与 nextCursor，下一页将游标填入 after。每页 1–50 条，默认 20 条。

Choose what to authorize选择授权权限

Sign in on the StellarEpic website and check the application name, return address and requested operations. Public history reading is selected by default; submissions and access to your review results are optional. “Stay connected” permits token refresh while you are offline.

在星辰史诗网站登录，核对应用名、返回地址与申请的操作。默认选中读取公开历史；提交投稿、查看自己的审核结果可自行选择。“保持连接”允许应用在离线时更新授权令牌。

Connections can be revoked under Connected applications. MCP authorizations cover public history and your editorial submissions. They do not grant access to personal records or administrator operations.

可以在已授权应用中撤销连接。MCP 授权范围是公开历史与自己的投稿，不包含私人记录或管理员操作。

MCP applications use OAuth authorization-code flow with PKCE and receive tokens for the MCP resource. Operations that need additional permission request another authorization. Application identity comes from its OAuth registration. Direct public HTTP requests still identify their application with a User-Agent.

MCP 应用使用带 PKCE 的 OAuth 授权码流程，获取用于 MCP 服务的令牌。操作需要额外权限时，应用会发起追加授权。应用身份来自 OAuth 注册；直接调用公开 HTTP 接口的程序仍使用 User-Agent 标明身份。

Corrections, references and new entries修正、参考资料与新词条

After authorizing submissions:write, call the corresponding MCP tool with the JSON arguments below. The tools add the submission kind for you; replace the sample text with your proposal.

授权 submissions:write 后，调用对应 MCP 工具，参数使用下面的 JSON。工具会自动补充投稿类型，示例文字需换成实际内容。

{
  "requestID": "client-correction-0001",
  "language": "zh",
  "eventId": "armstrong-apollo-11-landing",
  "baseVersion": 1,
  "section": "SECTION_ID_FROM_ARTICLE",
  "reason": "说明需要修正的事实及依据 / Explain the correction and its evidence.",
  "replacement": "修正后的完整段落 / The complete revised section.",
  "references": "作者 · 书名或论文名 · 出版年份 · 页码或章节 / Author · Title · Year · Page or chapter"
}

{
  "requestID": "client-reference-0001",
  "language": "zh",
  "eventId": "armstrong-apollo-11-landing",
  "baseVersion": 1,
  "references": "作者 · 书名或论文名 · 出版年份 · 页码或章节 / Author · Title · Year · Page or chapter"
}

{
  "requestID": "client-new-entry-0001",
  "language": "zh",
  "entryType": "person",
  "title": "人物名称 / Person name",
  "dateText": "生卒年代 / Life dates",
  "summary": "词条摘要 / Entry summary",
  "content": "完整正文 / Full article text",
  "references": "作者 · 书名或论文名 · 出版年份 · 页码或章节 / Author · Title · Year · Page or chapter"
}

Text limits: title 160 characters, summary 1,000, entry body 12,000, revised section 8,000, reason 2,000, references 4,000. References may contain up to 20 lines, each up to 1,000 characters.

文本上限：标题 160 字符、摘要 1,000、词条正文 12,000、修正段落 8,000、理由 2,000、参考资料 4,000。参考资料最多 20 行，每行最多 1,000 字符。

Review, retries and limits审核、重试与额度

Submissions return an id, revision and status: pending. Review changes the status to published or returned. Use read_my_submission to see reviewNote and, after publication, publishedHref. Approved corrections update the article's version and public revision history.

投稿成功返回 id、revision 与 status: pending。审核后变为 published（已发布）或 returned（已退回）。使用 read_my_submission 可查看 reviewNote 和发布后的 publishedHref。修正发布时会更新文章版本与公开修订记录。

• Per account: up to 10 new submissions in a rolling hour, 40 in 24 hours, and 20 pending submissions at a time. Maximum request body: 64 KiB.每个账号滚动一小时最多 10 份、24 小时最多 40 份，同时待审核最多 20 份。请求体最多 64 KiB。
• Use a unique requestID of 16–100 letters, digits or ._:-. IDs are case-insensitive. Retry an uncertain result with the same ID and identical body; use a new ID for changed content.requestID 使用 16–100 位字母、数字或 ._:-，不区分大小写。结果未确认时，用同一 ID 和完全相同的内容重试；修改内容后使用新 ID。
• For a 409 version conflict, read the latest article and check your proposal again. Start a new request after updating it. Keep pagination cursors within the same account, language and filters.遇到 409 版本冲突，重新读取原文、核对建议，更新后发起新的请求。分页游标只在相同账号、语言与筛选条件下继续使用。

HTTP errors include an error code. MCP submission errors return isError with error and status in the tool result; malformed arguments return a JSON-RPC error. Administrator review uses a separate administrator session. These tools submit proposals for review.

HTTP 错误 JSON 中的 error 给出具体原因。MCP 投稿错误查看工具结果的 isError、error 与 status；参数格式错误查看 JSON-RPC error。管理员使用独立的管理员会话审核稿件。

References and attribution参考资料与署名

For historical proposals, give the author, book, newspaper or paper title, publication year, and page, issue or chapter. The references field accepts bibliography text and excludes website addresses. You may cite references already listed in the article.

历史投稿的参考资料填写作者、书籍／报刊／论文名称、出版年份，以及页码、期号或章节。references 接受书目信息，不填写网站地址；也可引用文章已有的参考资料。

When quoting or adapting material, follow that material's licence and attribute its author and source. OAuth registration identifies an MCP application; a User-Agent identifies direct HTTP clients; it is separate from authorship and adaptation credits. This submission schema has no dedicated adaptation-credit field. Data and resource notices are collected under Sources and licences.

引用或改编资料时，按所用资料的许可标明作者与来源。OAuth 注册标识 MCP 应用，User-Agent 标识直接调用 HTTP 接口的程序，都与文章作者、改编者的署名分开。当前投稿字段没有单独的改编署名项。数据与资源的许可说明见资料来源与许可。