feat(mcp): MCP parity with web/Telegram agent — search + execute meta-tools (v0.3.0)

[simaonogueira101]

Summary

Brings the stdio MCP server to feature parity with the noticed web/Telegram agent by exposing the full 50-capability registry through two meta-tools instead of two hand-written ones.

• src/mcp-server.ts — replace search_network + get_connection_path with search + execute meta-tools. The LLM calls search to discover capabilities (network search, missions, PRM, memory, workspace, cron, …) and execute by name with the matching args.
• src/api-client.ts — add capabilitySearch / capabilityExecute methods that POST to noticed-agent's new /api/agent/capabilities/{search,execute} endpoints. The existing search / path / hydrate methods stay (used by the noticed search / noticed path CLI commands).
• Tests reworked: SearchArgsSchema + ExecuteArgsSchema (10 cases) + 3 api-client capability-method cases. 32 total.
• package.json + server.json bumped 0.2.0 → 0.3.0.
• README: new tools section + upgrade note from 0.2.x.

Depends on noticed.so serving POST /api/agent/capabilities/* — that landed in noticedso/noticed PR #104, deployed to production.

What clients see now

Before (0.2.x):

tools/list → [search_network, get_connection_path]

After (0.3.0):

tools/list → [search, execute]

search returns the full chat-safe registry (~50 capabilities) with JSON schemas. execute dispatches a named capability with args. Server-side denylist filters 9 chat-only capabilities (message, send_referral_invite, lookup_group_member, process_linkedin_zip, start_account_link, send_linkedin_export_instructions, cursor_cloud_agent_launch|status|followup).

Breaking changes

Clients that called search_network / get_connection_path directly will get an "Unknown tool" error after upgrading. The same operations are available via execute { capability: "search_network", args: { query: "…" } } and execute { capability: "get_connection_path", args: { query: "…" } }. MCP-aware LLMs (Claude, Cursor, ChatGPT MCP) discover the new shape via search automatically.

Test plan

• npm run lint — clean
• npm run check-types — clean
• npm test — 32/32 pass
• npm run build — clean
• Manual smoke against mcp.noticed.so — verified tools/list returns search+execute, search surfaces 50 capabilities, execute on list_missions returns real data
• Merge → push v0.3.0 tag → release workflow publishes @noticed/cli@0.3.0 to npm with provenance

Release flow

The release.yml workflow publishes to npm on v* tag push. After merge, please run:

git checkout main && git pull
git tag v0.3.0 && git push origin v0.3.0

The workflow handles lint / types / test / build / npm publish --provenance --access public.

🤖 Generated with Claude Code