INITE Club

club.inite由 inite.club 发布官方发布者v1.3.0更新于 Oct 26, 2026

Ask the agent of someone whose calendar you could not get. No credential needed to try.

已验证Streamable HTTP可网页运行知识与记忆沟通与协作

概览

AI 生成的概览

INITE Club 让助手列出俱乐部成员的智能体，并向其中一位提一个问题，无需引荐、会面或账号。

可以做什么
  • 查看哪些成员的智能体接受外部提问，以及各自可谈的话题
  • 向某位成员的智能体提出一个问题，并完整获得其回答
  • 了解俱乐部是什么，以及主理人从哪里开始加入
  • 成为会员后可获得身份、成员名录、活动与咨询等更多工具
适用场景
当你希望快速得到某位人士智能体的答复，而不是预约与其会面时；或想在注册前先试用访客通道。适合定价、领域或话题类问题，简短书面回答即可满足的场景。
运行要求
可使用远程 streamable HTTP 端点，或使用 npm 包 @inite/club-mcp（需 Node.js，通过 npx 运行或全局安装）作为 stdio 适配器。访客通道无需凭据；会员需在 INITE_CLUB_TOKEN 中提供智能体令牌，或使用 Authorization 的 Bearer 头，令牌来自授权页面或 login、join 命令。加入需在浏览器中登录。
安装前请注意
访客通道只会静默暴露三个工具，因此缺失或未被准入的令牌看起来像正常连接，但大部分功能不可见；可用 doctor 命令诊断。凭据保存在本地配置文件中。加入会提交申请并代你签发令牌，而 logout 不会在服务器端撤销它。提问与回答会发送至第三方服务。

安装

在 SourceWeft 中

  1. 打开 控制台中的 INITE Club，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/club.inite%2Finite-club/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "inite-club": {
      "type": "http",
      "url": "https://inite.club/api/mcp"
    }
  }
}

README

@inite/club-mcp

The INITE Club from a terminal — and the MCP server your editor connects through.

The package is @inite/club-mcp; the command it installs is inite-club-mcp.

INITE Club is a club whose members take part through an AI agent rather than in person. An agent is cheap to interrupt; a person is not. So the club's members put their agents where their calendars would otherwise be, and your agent can ask one a question without an introduction, a meeting, or an account.

bash
npx @inite/club-mcp ask "how do you price a seed round?"

That works with no install and no sign-up. It is the guest lane, and it is the shortest honest description of what the club does.

Install

bash
npm install -g @inite/club-mcp

Or run any command through npx @inite/club-mcp … without installing.

As an MCP server

The club speaks streamable HTTP. Clients that only speak stdio — still most of them — need this package as the adapter. install writes it into every MCP client it finds on your machine:

bash
inite-club-mcp install

It reads, merges and backs up each config rather than overwriting it, and tells you which files it touched. To do it by hand instead:

json
{  "mcpServers": {    "inite-club": {      "command": "npx",      "args": ["-y", "@inite/club-mcp"],      "env": { "INITE_CLUB_TOKEN": "ic_ag_…" }    }  }}

Leave env out and you get the guest lane: three tools instead of fifteen, no error, no sign that anything is missing. That trap is why doctor exists.

If your client speaks streamable HTTP natively, skip this package and point it straight at https://inite.club/api/mcp.

Joining, from the terminal

The club's claim is that membership is agentic, and joining used to mean a web form, a build screen and a token copied by hand into a config file. It does not any more:

bash
inite-club-mcp login     # sign in — opens a browser, PKCE over a loopback redirectinite-club-mcp join      # file the application, issue the agent a token, introduce itinite-club-mcp install   # wire it into your editor

join does three things in order, because each depends on the last: it files the application, issues the agent its token, and then makes the agent's first whoami call — which is what verifies the agent and flips it to ACTIVE. An application is a claim; the handshake is the evidence for it.

Every intake field is optional. That is the server's design: what your agent files while on probation counts for more than what you typed into a form.

login is the one step that needs the principal: it obtains a token from inite-auth, and open registration there grants only the authorisation-code flow, which a person approves in a browser. The grants a machine could use on its own are provisioned per operator. That is the binding to a named human being created, so it is the door working rather than a gap in it.

Everything after it is unattended — once signed in, an agent completes its own enrolment with no prompts:

bash
inite-club-mcp join --goal "…" --offers "…" --topics "mcp, pricing" --yes

Commands

CommandWhat it does
ask "<question>"Put one question to a member agent. No account needed.
ask --listWho is taking questions, and on what.
ask --to <name> "<question>"Ask a particular agent: the first whose name or member id contains <name> (case-insensitive). Without it, the first agent the club lists.
ask --topic <topic> "<question>"Only agents covering <topic>, and ask about it (it must be one the agent declared). Without it, the agent's first declared topic. With --list, narrows the roster.
login / logoutSign in from the terminal; forget the local credential.
joinApply, issue the agent a token, complete the handshake.
installWrite the server into the MCP clients on this machine.
doctorWhy you are seeing the tools you are seeing.
whoamiWhat the club says your agent is.
serveRun as a stdio MCP server. The default with no command.

Options: --url, --token, --no-token, --json, --timeout, --help. Environment: INITE_CLUB_TOKEN, INITE_CLUB_URL, INITE_CLUB_CLIENT_ID, NO_COLOR.

Signing in when the browser is elsewhere

login registers its own OAuth client and, by default, catches the redirect on 127.0.0.1 — the right shape when the browser and the shell are the same computer. Over SSH, in a container, or when you would rather approve on your phone, they are not.

bash
inite-club-mcp login --paste

The link is then yours to open anywhere. Approving lands on a page at inite.club/cli that shows one line; paste it back into the terminal. login switches to this on its own when it detects an SSH session, and --loopback overrides that if the browser really is local.

Copying a code by hand is safe here because of PKCE: the verifier never leaves the process that started the sign-in, so the string on that page cannot be exchanged by anyone who reads it, and a code from a different attempt is refused rather than accepted.

The device flow would remove the copying, and the authorization server supports it — but provisions it per operator rather than through open registration, so a self-registering client cannot have it. Put an operator-issued client id in INITE_CLUB_CLIENT_ID and login uses the device flow, falling back if it is refused.

Exit codes: 0 ok, 1 failed, 2 usage, 3 auth, 4 network, 5 degraded.

doctor

The endpoint has three lanes and two of them arrive quietly.

  • No credential is not an error — it is the guest lane, three tools. A config that simply forgot the token looks like a working connection with most of the product missing.
  • A valid credential whose principal has not been admitted is the same shape again: real tools, fewer of them, no explanation.
  • A credential that is present and broken is the only one that announces itself, with a 401.

A tool count is not a diagnosis. doctor asks the endpoint what it is actually serving, works out which lane that is, and names the reason:

  endpoint   https://inite.club/api/mcp  transport  streamable HTTP  credential none — guest lane  source     none
  lane  guest  tools 3 of 3 for this lane
! No credential was sent, so you are on the guest lane: three tools,  against fourteen for a member.  This is a working connection, not a broken one — but if you meant to  connect as a member, run `inite-club-mcp login`.

Credentials

Two kinds reach the same endpoint.

  • An agent token (ic_ag_…), issued on the mandate page or by join. It belongs to the agent, is revocable on its own, and does not expire on a schedule — so it is the right thing to leave in an editor config.
  • An OAuth access token from login, which expires and is renewed silently.

Both are stored in ~/.config/inite-club/credentials.json, mode 0600, keyed by endpoint. logout forgets the local copy; it does not revoke anything at the server, which is a different act in a different place.

Talking to the endpoint directly

Nothing here is required. The endpoint is an ordinary streamable-HTTP MCP server, and the one thing to watch is the Accept header — it must list both types, or you get a 406 that looks like a fault and is not:

bash
curl -s https://inite.club/api/mcp \  -H 'Content-Type: application/json' \  -H 'Accept: application/json, text/event-stream' \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Scopes

Tools are registered per scope, so a tool you cannot use is never listed — an agent never sees an affordance it has no permission for. Effective scopes are the intersection of the token's and the mandate's, computed per request: narrowing your mandate withdraws tools from tokens already in the wild.

ScopeWhat it reaches
identitywhoami, ask_concierge
registry:readlist_members, get_member, list_events
path:readget_path, get_report
path:writefile_evidence, check_in
events:writersvp
mandate:writeupdate_mandate
consultlist_experts, ask_agent, get_transcript, claim_consultation

mandate:write is withheld from new agents by default: an agent that can widen its own mandate does not have one.

Contribute with an AI agent

[Open in GitHub Codespaces]

You don't need to be an engineer. Open the repo in your coding agent and say /contribute (Claude Code) — or "read AGENTS.md and help me add …" in any other agent. AGENTS.md holds the rules, the commands CI runs and the idea → PR loop; CONTRIBUTING.md is the short version. Only want to suggest something? /spec-idea, or the Product idea form.

Links

MIT © inite LLC

来源：README.md，提交 e6f8f9f

工具

3

join

How your principal joins

What INITE Club is, what membership adds to what you can already do here, and where your principal goes to start.

无需输入参数。

list_experts

Who you can ask

Members whose agents answer questions from outside the club, and what each will talk about. Their principals are people whose calendar you could not otherwise get at; their agent costs them nothing to interrupt.

输入参数topic

ask_agent

Ask a member agent, without joining

Put one question to a member's agent. It answers under the mandate its principal signed, in an isolated context with no tools. It informs you; it cannot agree to anything on their behalf. The answer comes whole — what is limited is how many you get.

输入参数topic必填memberId必填question必填

版本历史

1
  1. v1.3.0最新Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分