Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LINUXDO_COOKIENo方式一:手工指定 cookie,形如 `_t=xxx`(裸 token 也可)。用于独立 token 登录,功能最全。
LINUXDO_BROWSERNo浏览器类型:`chrome`(默认)/`chromium`/`brave`/`slack`/`firefox`。仅方式二使用。chrome
LINUXDO_CACHE_DIRNo缓存目录,默认 `~/.cache/linuxdo-mcp`。~/.cache/linuxdo-mcp
LINUXDO_COOKIE_TTLNo缓存有效期秒数,默认 `2592000`(30 天,配合自续期)。2592000
LINUXDO_IMPERSONATENoTLS 指纹,默认 `chrome`。chrome
LINUXDO_READ_BROWSERNo方式二:置 `1` 才允许读浏览器(默认 `0`,防止与主浏览器互顶)。0
LINUXDO_CHROME_PROFILENo方式二:Chrome 系 profile 的显示名或目录名(如 `linuxdo` / `Profile 1`)。填错会列出所有可用 profile 供对照。

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
whoamiA

查看当前 cookie 对应的 linux.do 登录用户与信任等级。

searchA

全量搜索 linux.do。query 支持 Discourse 高级语法(order:latest、#分类、@用户、 tags:标签、after:2025-01-01、in:title 等)。pages 为连续抓取的页数(每页约 50 条)。 展示约定:Markdown 表格或列表,标题完整勿截断,纯文字勿用 emoji(易乱码)。

get_topicB

读取指定话题的详情与楼层正文。topic_id 可传数字 id,也可直接传 linux.do 话题 URL(如 https://linux.do/t/xxx/2885565/1,会自动取出 id)。posts=返回楼层数, start=起始楼层(1-based,用于翻页,如 start=21 取第 21 楼起)。返回含 total_posts(总楼数)。

format_searchA

同 search,但直接返回拼好的 Markdown(标题+URL+摘要列表),客户端可原样展示。

format_topicA

同 get_topic,但直接返回拼好的 Markdown(出处头 + 逐楼表格),客户端可原样展示。 topic_id 可传数字 id 或 linux.do 话题 URL(自动解析)。posts=楼层数, start=起始楼层(1-based,翻页用,如 start=21)。

list_categoriesA

列出所有板块/类别,含每个类别的话题数(topic_count)与帖子数(post_count)。

category_topicsA

列出指定类别下的话题(每页约 30 条)。返回含该类别总话题数 topic_count、 本页话题列表与是否有下一页。category_id 用 list_categories 查询。每条话题已含 category、min_trust_level。展示约定同 latest_topics(Markdown 表格、完整标题、 纯文字表头禁用 emoji)。

list_tagsA

列出所有标签及各自的话题数(count)。

tag_topicsA

列出指定标签下的话题(每页约 30 条)。tag 用标签名(如「人工智能」)。每条话题 已含 category、min_trust_level。展示约定同 latest_topics(Markdown 表格、完整 标题、纯文字表头禁用 emoji)。

user_infoB

查询用户资料:信任等级、注册/最后在线时间、发帖数、获赞数等。

latest_topicsA

获取首页「最新」话题列表(每页约 30 条)。每条已含 category(分类名)、 min_trust_level(最低等级要求,null=无限制),无需再逐条 get_topic 查分类。

展示约定:用 Markdown 表格,列依次为 标题(完整勿截断) | 分类 | 等级 | 回复 | 点赞 | 链接;表头与单元格一律纯文字,禁用 emoji(多字节 emoji 在生成时可能 碎成「����」乱码)。等级按 min_trust_level 显示「Lv0/1/2/3」,null 显示「—」。

top_topicsA

获取「热门」话题列表。period 取 daily/weekly/monthly/quarterly/yearly/all。 每条已含 category、min_trust_level。展示约定同 latest_topics(Markdown 表格、 完整标题、纯文字表头禁用 emoji)。

user_actionsC

获取某用户的发帖/回复活动(含摘要与跳转链接)。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 13 tools

Disambiguation3/5

Most tools map to distinct resources or filters, but search/format_search and get_topic/format_topic are essentially the same operations differing only in output formatting. The descriptions make the distinction explicit, so confusion is possible but not severe.

Naming Consistency3/5

Names mix bare verbs (search), verb_noun patterns (get_topic, list_categories), noun_topics forms (category_topics, latest_topics), and standalone words (whoami). All names are lowercase snake_case and readable, but they do not follow a single predictable convention.

Tool Count4/5

At 13 tools the count is within a reasonable range for a forum reader, but format_search and format_topic are redundant with search and get_topic, slightly padding the surface. The remaining tools each contribute meaningfully to searching and browsing the forum.

Completeness4/5

For a read-oriented forum browsing/searching server, the coverage is solid: search, topic detail, categories, tags, users, and topic feeds are all present. Obvious gaps like posting or replying would matter only if write access was expected, which is not suggested by the tool set.

Maintenance

ActivityMaintained
ResponsivenessNo issues