The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Cli listing page.
CLI, MCP server, and Claude Code plugin for noticed — search your developer network, trace connections, and find the shortest path to anyone through GitHub and LinkedIn collaboration graphs.
The MCP server exposes two meta-tools — search and execute — backed by ~50 noticed capabilities: developer-network search and connection paths, mission and goal tracking, a PRM (people-relationship-management) board, a virtual filesystem for agent workspace files, persistent memory, web search, scheduled crons, and more. Same surface the noticed web and Telegram agents use. Chat-only capabilities (in-chat messaging, referral invites, the Cursor Cloud bridge) are filtered server-side.
Upgrading from 0.2.x? The tool surface changed: clients that called
search_network/get_connection_pathdirectly should now callsearch(to discover the capability) followed byexecute { capability: "search_network", args: { query: "…" } }. MCP-aware LLMs handle this discovery automatically.
You have two ways to connect: hosted (no install, Streamable HTTP) or stdio (this package via npx). The hosted server runs your queries against noticed.so so anyone with a noticed account can use it. The stdio server is useful when your MCP client can't speak HTTP, or when you're running a self-hosted noticed instance.
https://mcp.noticed.so/api/mcp is a hosted Streamable HTTP endpoint. Two authentication paths are supported; pick whichever your client prefers.
The hosted server is a spec-compliant OAuth 2.1 authorization server with Dynamic Client Registration. Clients that follow the MCP authorization profile — including claude.ai's custom connectors and ChatGPT's MCP integration — discover the server, register themselves, and walk the user through a consent screen automatically. No API key needed in the client config.
claude.ai custom connector: open Settings → Connectors → Add custom connector, paste https://mcp.noticed.so/api/mcp as the URL. claude.ai handles the rest. Connected applications are visible (and revocable) at noticed.so/dashboard/oauth-grants.
For clients that can set an Authorization: Bearer … header, mint a key at noticed.so/dashboard/api-keys and use it directly — no OAuth flow needed.
Claude Code (one command):
Cursor, Claude Desktop, Zed, VS Code Copilot, Windsurf, Cline — all support URL + header config. Drop the command/args/env block from any of the stdio snippets below and replace with:
Pick your client below for the stdio install.
--scope project writes to .mcp.json at your repo root so the server is shared with everyone on the team. Drop the flag for a personal-scope install.
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):
Edit .vscode/mcp.json for workspace, or run MCP: Open User Configuration for global:
Note VS Code uses servers (not mcpServers) and requires type.
Edit ~/.codeium/windsurf/mcp_config.json:
Edit ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json:
MCP works in agent mode only. Add .continue/mcpServers/noticed.yaml:
Edit ~/.config/zed/settings.json (note: key is context_servers, not mcpServers):
The portable noticed Agent Skill works in Codex, Claude Code, Cursor, and other clients supported by the open skills ecosystem:
The repository is also an Agent Plugins 1.0 package. It carries a portable
plugin.json, skills/, and mcp.json, plus a Claude Code compatibility
manifest under .claude-plugin/. The MCP definition starts the version-pinned
stdio server; configure NOTICED_API_KEY in the client environment or run
noticed config --set-key … before querying production data.
To install the Claude Code compatibility plugin directly from source:
The CLI authenticates with a Bearer API key. Mint one at /dashboard/api-keys — the secret is shown once at create time, so copy it immediately. Tokens look like nk_live_…, are rate-limited to 60 requests per minute per key, and can be revoked from the same page.
noticed search <query>Search your developer network for people, companies, skills, or topics.
| Flag | Description | Default |
|---|---|---|
-l, --limit <n> | Maximum results | 25 |
-o, --offset <n> | Pagination offset | 0 |
-s, --source <src> | Filter: github or linkedin | all |
--sort <col:dir> | Sort: name:asc, company:desc | none |
-p, --paths | Fetch shortest paths to the top 5 hits | off |
-j, --json | Output raw JSON | off |
--csv | Output as CSV | off |
--no-color | Disable colors | auto |
noticed path [target]Find the shortest connection path between you and a person.
Logins are resolved via search before the path lookup. Pass --li to skip the search step and look up by LinkedIn username directly.
noticed configConfig is stored at ~/.config/noticed/config.json (XDG-compliant).
noticed mcpnoticed completion <shell>| Variable | Description | Required |
|---|---|---|
NOTICED_API_KEY | API key minted at https://www.noticed.so/dashboard/api-keys | yes |
NOTICED_API_URL | Override the noticed instance URL. Defaults to https://www.noticed.so — only set this if you self-host | no |
NOTICED_BASE_URL | Alias for NOTICED_API_URL | no |
Precedence: CLI flags > environment variables > config file.
The MCP server exposes exactly two tools — both meta-tools that bridge to the noticed agent's capability registry. The client's LLM uses search to discover capabilities at runtime, then calls execute by name.
| Tool | Description |
|---|---|
search | Discover noticed capabilities by keyword and optional category. Returns names, descriptions, categories, and JSON parameter schemas. Call with no arguments to list everything. |
execute | Run a capability by exact name. Pass capability arguments in the args object. |
Example client-side flow:
The ~50 chat-safe capabilities cover developer-network search (search_network, get_connection_path, my_profile, my_network, my_activity, …), missions/goals/milestones, PRM (people / interactions / stages), virtual filesystem and persona files, persistent memory, web search and fetch, and cron scheduling. Nine chat-only capabilities (in-chat messaging, referral invites, Cursor Cloud agents) are filtered server-side.
Test with the MCP Inspector:
Or by hand against the stdio server:
The CLI defaults to the hosted noticed instance at https://www.noticed.so. Self-hosting noticed itself is possible but operationally heavy — the value depends on a pre-ingested GitHub + LinkedIn collaboration graph (hundreds of GiB of ClickHouse data, daily GHArchive ingestion, paid LinkedIn API access, OpenAI + Anthropic keys, NextAuth OAuth apps). Most users want the hosted service.
If you do run your own instance, set NOTICED_API_URL to its URL — everything else works the same:
The source for the hosted service lives at https://github.com/noticedso/noticed.
MIT © noticed