原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

Less Annoying CRM (remote, OAuth)

✓ northkeellabs.com

作者:northkeellabs版本 0.1.0i★ 0i在云端运行代码仓库 ↗
注册名称com.northkeellabs/lacrm-mcp-remote

安装方法

能做什么

Unofficial remote MCP server for Less Annoying CRM: OAuth 2.1, read-only grants, 10 tools.

作者提供的原文

  • 连接方式 在云端运行
  • 账号或密钥 连接时登录该服务(OAuth)
  • 分类 营销与社交媒体

可搭配使用

教 AI 做这类工作的 Skill,可与本项一起使用

scroll-world

A skill that turn any brand into a scrollable 3D world landing page

作者:oso95★ 11,0791 个 skill

Skill · 操作手册

social-auto-upload

自动化上传视频到社交媒体:抖音、小红书、视频号、tiktok、youtube、bilibili

作者:dreammis★ 16,718 (整个仓库)4 个 skill

Skill · 操作手册

native-subtitle-quote-image

保留视频内嵌字幕,精确取帧并生成 3:4 社交长图的 Agent Skill

作者:chengyi-ai★ 2,8931 个 skill

Skill · 操作手册

为什么排在这里

此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列

1. 在 Claude 连接器目录中否
2. 团队实测过否
3. 适合泰国用户否
4. 不计星标的使用量20/100热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0
5. 登记日期2026-11-10

用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。

质量: 基础检查通过 4/4 项(仅展示,不用于排序)

安装

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

用一句话让 AI 帮你安装

请帮我安装 Less Annoying CRM (remote, OAuth)。按照 https://mcp.popnx.com/i/northkeellabs-lacrm-mcp-remote.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 4/4 项检查 · 你的提问会经过开发者的服务器(lacrm-mcp.northkeellabs.com) · ✓ 命令已检查 2026年11月20日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称Less Annoying CRM (remote, OAuth)
    Remote MCP server URL · 地址https://lacrm-mcp.northkeellabs.com/mcp

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsLess Annoying CRM (remote, OAuth)

  4. 试一试

    用 Less Annoying CRM (remote, OAuth) 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Less Annoying CRM (remote, OAuth),或回答中出现 Less Annoying CRM (remote, OAuth) 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称Less Annoying CRM (remote, OAuth)
    Connection · 地址https://lacrm-mcp.northkeellabs.com/mcp
  3. 在聊天中选择 Less Annoying CRM (remote, OAuth)

    开启新聊天,输入前先从插件列表中选择 Less Annoying CRM (remote, OAuth)

  4. 试一试

    用 Less Annoying CRM (remote, OAuth) 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 Less Annoying CRM (remote, OAuth),或回答中出现 Less Annoying CRM (remote, OAuth) 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user lacrm-remote https://lacrm-mcp.northkeellabs.com/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 Less Annoying CRM (remote, OAuth) 在列表中并显示已连接

  4. 试一试

    用 Less Annoying CRM (remote, OAuth) 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Less Annoying CRM (remote, OAuth),或回答中出现 Less Annoying CRM (remote, OAuth) 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Less Annoying CRM (remote, OAuth) 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Less Annoying CRM (remote, OAuth),或回答中出现 Less Annoying CRM (remote, OAuth) 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Less Annoying CRM (remote, OAuth) 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Less Annoying CRM (remote, OAuth),或回答中出现 Less Annoying CRM (remote, OAuth) 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://lacrm-mcp.northkeellabs.com/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Less Annoying CRM (remote, OAuth) 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user lacrm-remote https://lacrm-mcp.northkeellabs.com/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "lacrm-remote": {
      "url": "https://lacrm-mcp.northkeellabs.com/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "lacrm-remote": {
      "type": "http",
      "url": "https://lacrm-mcp.northkeellabs.com/mcp"
    }
  }
}

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

一览

每周下载量i
不在 npm/PyPI 上
已验证域名
✓ northkeellabs.com
连接方式
在云端运行
传输方式
streamable-http
最新版本i
0.1.0
发布到注册中心i
2026年11月10日
代码最后更新i
2026年11月12日
最近检查
2026年11月16日
作者
northkeellabs
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

服务器要求先登录,才会列出它的工具。

基础检查i

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

  • ✓ 通过

    作者与仓库一致

    注册名称已通过域名 northkeellabs.com 验证(注册中心会核实域名所有权)

  • ✓ 通过

    仍在维护

    代码最后更新于8天前

  • – 不适用

    有许可证

    不适用:由 northkeellabs.com 的所有者自己运行的云端服务器,你不会运行仓库里的代码

  • ✓ 通过

    端点有响应

    在 179 毫秒内响应(HTTP 401)

  • ✓ 通过

    使用 OAuth 登录

    声明支持 OAuth 登录,你的 AI 应用可以带你去登录

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/northkeellabs-lacrm-mcp-remote.svg)](https://mcp.popnx.com/en/servers/northkeellabs-lacrm-mcp-remote)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“营销与社交媒体”中的其他服务器比较i

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

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

常见问题

Less Annoying CRM (remote, OAuth) 安全吗?

它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于8天前,最新版本(0.1.0)于10天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:Relaticle, ChatbotX, X (Twitter) MCP Server by Xquik, Betterlytics, BibiGPT YouTube Video Summarizer

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

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

Relaticle

Open-source CRM your AI agents can write to: companies, people, opportunities, tasks and notes.

作者:relaticle正在增长★ 1890今天更新

在云端运行✓ 服务方 · relaticle.com

ChatbotX

Omnichannel customer messaging, CRM contacts, flows, sequences, broadcasts, and AI automation.

作者:ChatbotXIO正在增长★ 1134 整个仓库的星标14天前更新

在云端运行✓ 服务方 · chatbotx.io

Betterlytics

Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.

作者:betterlytics正在增长★ 1964个月前更新

在云端运行✓ 服务方 · betterlytics.io
与相似项目对比
本项
Less Annoying CRM (remote, OAuth)
RelaticleChatbotXX (Twitter) MCP Server by XquikBetterlyticsBibiGPT YouTube Video Summarizer
运行位置在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否是否
可在 Claude 中按 + 添加否否否否否否
基础检查4/44/44/44/44/44/4
许可证MITAGPL-3.0NOASSERTIONMITAGPL-3.0MIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

lacrm-mcp-remote

A remote MCP server for Less Annoying CRM (LACRM), hosted on Cloudflare Workers, with OAuth 2.1 sign-in. It exposes the same 10 tools as the local lacrm-mcp server (stdio, Python, also by Northkeel Labs), but over Streamable HTTP, so it works as a claude.ai custom connector and in any MCP client that supports remote servers with OAuth.

Independent and unofficial. Not affiliated with, endorsed by or supported by Less Annoying CRM.

Video walkthrough (62 s, voice + captions): Claude using this hosted server as a claude.ai connector on a live account with demo data, the read-only mode, OAuth 2.1 sign-in and the test results. GitHub starts videos muted: click the speaker icon in the player to hear the voiceover.

https://github.com/user-attachments/assets/99e98a72-4f8e-41c6-b0c6-46789ef81c4c

Hosted endpoint

https://lacrm-mcp.northkeellabs.com/mcp

Northkeel Labs runs this code at that URL. Paste it into any MCP client that supports remote servers with OAuth (see Connect a client), sign in, and paste your LACRM API key on the consent page. The Worker stores only the encrypted OAuth grant; it keeps no other copy of your key or CRM data. Free, best effort, no SLA, 60 tool calls per minute per connection. To run it on your own Cloudflare account instead, see Deploy your own.

Why remote + OAuth

A local stdio server needs every user to install Python, store an API key in a config file and keep the process running on their machine. A remote server is one URL. The user pastes it into claude.ai, Claude Desktop or Cursor, signs in once in the browser, and the client gets a short-lived, revocable token. The API key stays out of the client, out of config files and out of the model's context.

LACRM itself has no OAuth, only API keys. This server bridges the two with a "bring your key, get OAuth" pattern: the Worker is a standards-compliant OAuth 2.1 authorization server (discovery metadata, dynamic client registration, Client ID Metadata Documents, PKCE S256, refresh-token rotation), and its consent page is where the user pastes their LACRM key once. The key is checked with a single read-only LACRM call and then lives only inside the encrypted OAuth grant.

Architecture

flowchart LR

subgraph Client["MCP client (claude.ai, Claude Desktop, Cursor, Inspector)"] C[OAuth + Streamable HTTP] end subgraph Worker["Cloudflare Worker: lacrm-mcp-remote"] OP["OAuthProvider discovery, register, token"] AU["Consent page at authorize key + access level"] MCP["MCP endpoint rate limit, scope gate, 10 tools"] RL[("RateLimiter SQLite Durable Object one per grant")] end KV[("KV: OAUTH_KV clients, grants, token hashes props encrypted")] LACRM["LACRM API v2 api.lessannoyingcrm.com"] C -- discovery, DCR/CIMD, token --> OP C -- browser sign-in --> AU C -- Bearer token --> MCP OP <--> KV AU -- GetUser (validate key) --> LACRM AU -- completeAuthorization --> OP MCP --> RL MCP -- key from decrypted grant --> LACRM

Code map: src/index.ts (OAuthProvider wiring), src/authorize.ts (consent page), src/mcp.ts (protected endpoint), src/tools.ts (the 10 tools), src/lacrm.ts (API client, retries, error mapping), src/security.ts (truncation, untrusted-data wrapper, redaction), src/ratelimit.ts (Durable Object).

Built on @cloudflare/workers-oauth-provider 1.2.4, agents 0.33.0 (createMcpHandler) and the MCP TypeScript SDK v2 (@modelcontextprotocol/server 2.4.0). The handler is stateless: every request gets a fresh MCP server built for that grant. It serves both 2025-era Streamable HTTP clients and the stateless 2026 protocol from the same /mcp endpoint. There is no /sse endpoint. McpAgent is deprecated as of agents 0.33.0, so this uses createMcpHandler instead; the only Durable Object is the per-grant rate limiter.

The auth flow, step by step

  1. The client calls POST /mcp without a token and gets 401 with WWW-Authenticate: Bearer resource_metadata=".../.well-known/oauth-protected-resource/mcp", scope="lacrm.read".
  2. It reads the protected resource metadata (RFC 9728), then the authorization server metadata at /.well-known/oauth-authorization-server (RFC 8414).
  3. It identifies itself, either with a Client ID Metadata Document URL or by registering at /oauth/register (RFC 7591 dynamic client registration).
  4. It opens /authorize in the browser with PKCE (S256 only), state and resource. The server rejects unknown clients and any redirect URI that was not registered, and renders those errors locally instead of redirecting.
  5. The consent page shows which client is asking (name, verified domain for CIMD clients, redirect host, a warning for local apps), asks for the LACRM API key and an access level: read-only (lacrm.read) or read and write (lacrm.read lacrm.write).
  6. On submit (POST only, CSRF handle bound to a __Host- cookie, single use, 10 minutes), the server calls LACRM GetUser with the key. A rejected key shows an error and nothing is stored.
  7. The server completes the authorization. The key, LACRM user id, granted scopes and a grant id are stored as grant props, encrypted with key material wrapped by the token. The browser is redirected to the client with a code.
  8. The client exchanges the code plus PKCE verifier at /oauth/token for an access token (1 hour) and a rotating refresh token.
  9. Every /mcp call is rate limited per grant (60 per minute by default) and scope-checked: a read-only grant sees 6 tools in tools/list and any call to a write tool is refused, whether or not it was listed.

Tools

ToolAccessLACRM functionWhat it does
search_contactsreadGetContactsSearch contacts and companies by text; summary per record, paged
get_contactreadGetContactFull record for one contact or company
list_contact_notesreadGetNotesAttachedToContactNotes on a contact, paged
list_tasksreadGetTasksTasks in a date range (max 366 days), optional contact filter
list_pipelinesreadGetPipelinesPipelines and their status ids
list_pipeline_itemsreadGetPipelineItemsItems in one pipeline, optional status filter
create_contactwriteCreateContactNew contact or company; owner defaults to the key's user
add_notewriteCreateNotePlain-text note on a contact
create_taskwriteCreateTaskNew task, optionally on a contact
update_pipeline_item_statuswriteEditPipelineItemMove an item to another status; automations are not run

There are no delete tools. Limits match the Python version: at most 50 results per page with has_more_results, text fields truncated at 2,000 characters, lists capped at 50 items, and every response that contains CRM records carries a data_notice marking the content as untrusted data, not instructions. Inputs are validated with zod (ids are digit strings, enums, ISO dates, email format, length limits) before any request reaches LACRM.

Deploy your own

You need a Cloudflare account (the free plan is enough: one Worker, one KV namespace, SQLite-backed Durable Objects) and Node 22+.

git clone <this repo> lacrm-mcp-remote && cd lacrm-mcp-remote

npm install npx wrangler login npx wrangler kv namespace create OAUTH_KV

Paste the printed namespace id into kv_namespaces[0].id in wrangler.jsonc (the id in the repo belongs to the hosted instance and will not work on your account). The repo config serves the Worker on our custom domain, so change the address too:

  • Your own domain (the zone must be on the same Cloudflare account): set routes[0].pattern to your hostname, for example mcp.example.com, and vars.MCP_RESOURCE to https://mcp.example.com/mcp.
  • Or workers.dev: delete the routes entry, set "workers_dev": true, and set vars.MCP_RESOURCE to https://lacrm-mcp-remote. .workers.dev/mcp (your subdomain is shown in the Cloudflare dashboard under Workers and Pages).

Tokens are bound to this exact URL. Then:

npm test                 # unit and integration tests in the Workers runtime

npx wrangler deploy

No server-side secret is needed: each user's LACRM key arrives through the consent page and is stored only in their encrypted grant. Optional settings are plain vars in wrangler.jsonc (RATE_LIMIT_PER_MINUTE, default 60). If you later add a secret of your own, use npx wrangler secret put NAME in production and .dev.vars locally (see .dev.vars.example; .dev.vars is gitignored).

Local development: copy .dev.vars.example to .dev.vars (it sets MCP_RESOURCE to http://localhost:8787/mcp, overriding the production value), then npx wrangler dev serves everything at http://localhost:8787.

Connect a client

Use the hosted endpoint https://lacrm-mcp.northkeellabs.com/mcp or your own deployment's URL.

  • claude.ai: Settings > Connectors > Add custom connector. Paste the URL, then Connect. A browser tab opens the consent page; paste your LACRM key (LACRM: Settings > Programmer API) and choose the access level.
  • Claude Desktop: Settings > Connectors > Add custom connector, same URL and flow as claude.ai.
  • Cursor: add to ~/.cursor/mcp.json and enable the server; Cursor opens the browser for sign-in.
  { "mcpServers": { "lacrm": { "url": "https://lacrm-mcp.northkeellabs.com/mcp" } } }
  • MCP Inspector: npx @modelcontextprotocol/inspector, choose transport "Streamable HTTP", enter the URL, and complete its OAuth sign-in flow. Against local dev use http://localhost:8787/mcp.

To revoke access, delete or rotate the API key in LACRM. Every grant made with that key then stops working, whatever client holds the token.

Security

Summary (details and threat model in SECURITY.md):

  • The LACRM key is never accepted as a tool argument, never returned to the client, never logged. Error text from LACRM is redacted before it reaches a tool result.
  • Grant props (which hold the key) are encrypted by the OAuth provider; access tokens, refresh tokens and codes are stored only as hashes.
  • Consent page: POST only, single-use CSRF handle bound to the browser, all client-supplied text HTML-escaped, Content-Security-Policy: default-src 'none'; script-src 'none'; frame-ancestors 'none' with one nonce'd inline style, no JavaScript and no third-party resources, X-Frame-Options: DENY, no-store.
  • Exact redirect URI matching; unknown clients and unregistered redirect URIs are rendered as local errors, never redirected.
  • Scope enforcement on every call; per-grant rate limit; writes are never auto-retried on 5xx or timeouts.
  • CRM content is bounded and labelled as untrusted to reduce prompt-injection risk. It cannot be made harmless; keep a human in the loop for writes and prefer read-only grants for summarising.

Tests

Test results, 2026-11-10: npm test 50 tests passing (Workers runtime via @cloudflare/vitest-plugin, LACRM mocked at fetch); tsc --noEmit clean; wrangler deploy --dry-run succeeds; live end-to-end (scripts/e2e-live.mjs against wrangler dev and a real LACRM account holding demo data) 20/20 steps passing, and the same 20/20 against the production deployment at https://lacrm-mcp.northkeellabs.com. Redacted output: local, production. Also tested 2026-11-10 as a claude.ai custom connector (read-only grant).

The tests cover each tool's request mapping and output shape, truncation, pagination, the untrusted-data wrapper, error mapping and redaction, retry policy, scope gating (a read grant can neither see nor call write tools, including in a batch), the consent page (bad key, missing or forged CSRF t

只显示了开头部分;其余内容请在仓库中阅读