SignalBase - Registration and MCP setup guide for AI assistants
Revision: 2026-10-23. Current copy: https://signalbase.fans/downloads/signalbase-setup.txt

Supported clients: Codex, Claude Code, and WorkBuddy.
Platforms: Windows and macOS. No Python installation or local proxy is required.
SignalBase uses browser sign-in and OAuth. An invitation code is not an API key.

What this connection is
SignalBase provides authorized reports, company meetings, research articles and news. Official endpoints: signalbase.fans and auth.signalbase.fans. Configure only this product.

Installation flow and completion
The user's request to configure this connection authorizes its ordinary setup steps, subject to the client's actual permissions and security prompts. Ask only for information or user actions that are genuinely missing. Work through configuration, trust/loading, browser authorization and one tool-call verification in that order. Saving JSON is only configuration readiness; an authorization-success page is only authorization evidence. Report completion only after this client exposes this server's research tool and the metadata-only call below succeeds. If a user click is pending, state the exact pending stage and the control you actually observed.

If SignalBase is not visible after setup
If the new SignalBase connection is missing from the client's connector/MCP list after configuration or an initial trust approval, refresh that list. If it still does not appear, save your work, fully quit and reopen WorkBuddy, Codex, or Claude Code, then check the list again. Select SignalBase and complete any trust, enable, or authorization prompt the client displays. An earlier trust approval may not complete every loading/authorization step. Have the user restart the client when ready; do not force-close it. Recheck loading afterward using the verification steps below; restarting alone does not prove setup is complete.
如果配置完成或首次点击信任后，仍未在连接器／MCP 列表中看到 SignalBase，请先刷新列表；仍未出现时，保存当前工作，完全退出并重新打开 WorkBuddy、Codex 或 Claude Code，再查看列表，选择 SignalBase 并按客户端提示完成信任、启用或授权。重启后仍需按下文确认连接已加载。

Existing connections and upgrades
Keep the existing account, OAuth credentials, server URL, and unrelated settings. Refresh or reload only the SignalBase connection to discover its current tool schema. Do not repeat registration, redeem another invitation code, or sign in again unless the client reports that authorization is required. The public interface consists of exactly one tool named research.

Switching clients
An explicit request to install or reconnect SignalBase authorizes browser OAuth in the selected client. Complete normal OAuth approval in the selected client, even when the browser already has a website login. SignalBase Gold permits two active connections across clients or computers. An explicit third authorization replaces only the oldest authorization. Other ordinary plans permit one active connection; administrator exemptions remain server-controlled. Membership eligibility is checked on first use each Beijing day and cached, with exact expiry, revocation and membership changes still enforced. Saved current credentials survive app restarts and temporary network faults; these do not require a fresh browser login. Tool discovery, ordinary requests, app restarts and token refresh never activate another connection. A replaced client must stop and await a new user request; do not automatically run login/reconnect, reuse an old authorization URL or try to reclaim access. SignalBase research with reconnect=true only reports the current connection; it does not activate a new OAuth grant.
SignalBase Gold 可同时保留两个客户端／电脑连接；明确授权第三个连接时，仅替换最早授权的连接。其他普通套餐保留一个连接，管理员豁免由服务端决定。旧客户端的后台刷新和普通查询不会抢回连接；收到失效提示后，应等待用户再次明确要求重连。

Determine the user's registration state before making changes:
- Not registered: use the invitation recipient's email and the invitation code voluntarily supplied by the user. If the attachment names a registration email, use it rather than asking again.
- Registration submitted / activation email received: the invitation code has already been redeemed. Do not register again or ask for the code. The user must verify their email and set a password themselves.
- Existing active account: proceed to client setup and browser authorization. Do not request an invitation code.

Instructions for the configuration assistant

1. Configure only the client selected by the user. Locate its actual active configuration, back it up, and preserve other MCP servers, settings, projects, and credentials. Do not display existing credentials or ask for passwords in chat.
2. For a new registration, open https://signalbase.fans/register/ and enter the invitation recipient's email and the user-supplied invitation code. Email invitations are restricted to the original recipient. Never put the code in a URL, MCP configuration, or logs.
3. After submission, the service sends an activation email with this TXT attachment. Have the user open the email's secure link themselves, verify their email, and set a password. Do not request or handle their password or activation link. Activation is incomplete until both steps are done. For a missing email, check spam and follow the page's retry guidance instead of repeatedly submitting registration.
4. Configure a remote HTTP MCP using the instructions for the selected client below.

MCP server: https://signalbase.fans/mcp
Identity service: https://auth.signalbase.fans/auth/realms/research
Do not configure a static Bearer token, API key, or Client Secret.

Codex
- Locate the Codex CLI bundled with the installed application and its active config.toml. Back up the file and merge only these tables; do not create duplicate entries:

  [mcp_servers.signalbase]
  url = "https://signalbase.fans/mcp"
  startup_timeout_sec = 30
  tool_timeout_sec = 180
  [mcp_servers.signalbase.oauth]
  client_id = "research-codex"
  callback_url = "http://127.0.0.1:8767/callback"
  callback_port = 8767

- Verify with: codex mcp get signalbase
- Start authorization with: codex mcp login signalbase
- Let the user sign in and approve access in the browser. Do not construct, share, or log callback URLs containing authorization codes.

Claude Code
- First inspect: claude mcp get signalbase
- If there is no matching connection, add it with:
  claude mcp add --scope user --transport http --client-id research-claude-code --callback-port 8768 signalbase https://signalbase.fans/mcp
- Preserve other connections. Have the user open /mcp, select signalbase, and choose Authenticate to complete browser authorization.

WorkBuddy
- First identify the installed version and inspect its actual MCP management screen. On the observed Windows WorkBuddy 5.7.6 the entry is "MCP 服务管理" -> "添加 MCP" (MCP service management -> Add MCP). Use this supported interface for a new connection; reuse/edit an existing signalbase connection rather than creating a duplicate. Choose remote HTTP with URL https://signalbase.fans/mcp and name signalbase. Leave static Headers, API key and Client Secret empty; use browser OAuth.
- Menu labels and form fields may differ in other versions. If you cannot operate the screen, give the user the fields above and the minimum required click. Do not invent a "自定义连接器" entry, a trust button or automatic browser launch that you have not observed. If the actual form lacks HTTP/OAuth support, report that version limitation rather than changing transport or adding a local proxy.
- File-based setup is a fallback only after verifying the active config path for this installation. Windows commonly uses ~/.workbuddy/mcp.json; that path alone does not prove it is loaded. Back up and merge only mcpServers.signalbase: {"type":"http","url":"https://signalbase.fans/mcp","disabled":false}. Preserve other entries. Unparseable or ambiguous config requires diagnosis before writing.
- WorkBuddy also maintains a loaded MCP registry and trust approvals. A directly written file may need an explicit supported refresh/import and user trust approval. Use its MCP management screen to inspect signalbase, enable/approve it when actually requested by the app, then connect/authorize it. Do not edit approval records or credentials yourself, and do not claim that the desktop never reads mcp.json.
- After configuration, have the user complete browser login and consent on auth.signalbase.fans and allow the return to WorkBuddy when prompted. Use the client connection state and tool discovery to check loading. Refresh/reconnect only signalbase if needed. If it remains absent from the connector/MCP list, follow the restart guidance above, then complete any displayed trust or authorization prompt. Do not invoke CodeBuddy CLI commands or create project .mcp.json as a substitute for this desktop interface.

5. Verify that the authorization page is on auth.signalbase.fans. After the user signs in and grants access, refresh the client's MCP tool list and confirm the connection status.
6. Confirm that this server's tools/list contains exactly one tool named research; tools belonging to other MCP servers do not count. If a previous tool list remains visible, refresh or reload this connection and verify again. Do not call retired tool names or add a fallback connection. Follow the newly discovered input schema and supply fields directly, without a request wrapper. Verify one metadata-only call to research with {"limit":1,"user_request":null,"resolved_request":"Verify this user-requested SignalBase installation with one authorized catalog item."}; do not add a question, read article text, bulk-search, or download reports. This verifies tool execution without consuming a full-article read. If discovery or execution fails, report the actual failure rather than claiming installation succeeded.
7. Report configuration, authorization, and successful tool execution separately. Saving a configuration or seeing an authorization-success message does not prove a tool call succeeded. Clearly state any remaining user clicks or system permission prompts. Do not bypass security warnings or terminate unrelated work.

If a step fails
- No entry/tool appears: check the active config, MCP management entry, trust/enabled state and this connection's loading first. If the connection is still missing after refreshing, follow the restart guidance above. Do not repeatedly register, rewrite the same file, restart the app in a loop or scan unrelated directories.
- First authorization is pending: continue this connection's browser OAuth flow; do not treat the normal unauthenticated 401 discovery response as proof that the account is invalid. A website login alone does not authorize WorkBuddy.
- Connection replaced / session_revoked: stop. Explain that a newer authorization replaced this connection. Only if the user requests reconnection, start a fresh browser OAuth from this client; no extra takeover confirmation is needed.
- Browser callback reports 127.0.0.1 connection refused: the local client callback listener may no longer be running. This does not prove an account or membership failure. Return to the client, start a fresh authorization (Codex: codex mcp login signalbase), keep that process running and complete its newly opened browser flow. Do not reuse an old localhost URL, change cloud membership or claim the server has verified the local listener.
- Temporary authentication verification failure (HTTP 503): preserve credentials and retry only when the explicit response marks retryable=true, reauthentication_required=false and query_executed=false. Do not treat network trouble as lost membership, run login or reinstall.
- Tool execution fails: report the stage and credential-free error; preserve the existing connection and account while diagnosing. Do not reset passwords, revoke sessions or change product membership as an installation workaround.
- Once the metadata-only call passes, installation is complete. Further research, author lookups and article reads are separate user requests, not additional installation tests. Keep the final setup report brief and never repeat invitation codes or credentials.

Useful links
Registration: https://signalbase.fans/register/
Account: https://signalbase.fans/account/
Download this TXT and get help: https://signalbase.fans/guide/

Privacy
AI 客户端生成的最终回答不会自动回传给 SignalBase。我们仅接收本次检索所需的请求，不读取你的完整聊天历史。
The AI client’s final answer is not automatically sent back to SignalBase. We receive only the requests needed for the current retrieval and do not read your complete chat history.
Retrieval requests may include your question and are recorded as described at https://signalbase.fans/privacy/.

Remove configuration or revoke access
Removing this client’s MCP entry stops using that configuration; it does not revoke server authorization or delete request records. To disconnect this device, use the client’s supported sign-out/disconnect controls (Codex: codex mcp logout signalbase). For server-side authorization/session revocation contact the administrator who supplied your invitation. Already-issued access tokens may remain valid until expiry. Account closure and record deletion are separate requests. Do not describe configuration removal as revocation.