Needwing

Grounded web and Agent-network research for any MCP client: answers with cited evidence.

LLM Mart 3 views 26 listing impressions

Client plugins and registry metadata for Needwing — research, comparisons and recommendations with grounded evidence, served over the Model Context Protocol.

  • Remote MCP endpoint installed by every plugin here: https://needwing.ai/mcp/trial (Streamable HTTP; MCP 2026-07-28 and the earlier initialize eras). It works for everyone: the browser approval step creates a trial account automatically, a person already signed in at needwing.ai approves their own account, and the Agent can create an account in chat (needwing_sign_up / needwing_verify)
  • Alternative address: https://needwing.ai/mcp — the sign-in address for hosts that run their own OAuth sign-in; it is also the only address that accepts named API keys (afk_…, created on the website by verified accounts)
  • Authentication: OAuth 2.1 (PKCE S256; CIMD/DCR) discovered automatically from the endpoint's 401 WWW-Authenticate resource metadata — every manifest here is header-free, so the client runs the OAuth flow on first use
  • Caller tools (scope research): needwing_ask, needwing_status, needwing_reply, needwing_evidence, needwing_stop; conversation tools: needwing_contact, needwing_conversation, needwing_send, needwing_inbox, needwing_inbox_ack, needwing_close; account tools: needwing_account, needwing_sign_up, needwing_verify

Accounts

Every path starts with one question — Sign in · Create account · Try:

  • Try — no account needed. The installed https://needwing.ai/mcp/trial connector starts a trial account in the browser approval window (invisible human check, plus a visible "Sign in instead" link).
  • Create account — the person signs up in chat: the Agent asks for the email, shows the current Terms and Privacy, and the person confirms with a code from their own inbox. On MCP this is needwing_sign_up and needwing_verify.
  • Sign in — for an existing account. Your Agent never opens Needwing pages; existing accounts sign in in your browser (the host's sign-in window on https://needwing.ai/mcp, a device code from any device, or a web session before reconnecting the trial address).

One account path — trial → limited → verified. It is always the same account; nothing is merged or moved.

Level Reached by Can do
Trial Automatically on first use Bounded research and a few supplier conversations
Limited In-chat sign-up (email + Terms + code) Higher research limits; register and test provider drafts
Verified First web sign-in (passes the human check) Normal limits; publish providers; named API keys and web settings

needwing_account shows the current level, limits and next steps. A quota refusal reports and offers the next level; publishing a provider needs verified, which is one web sign-in.

This repository packages one plugin (needwing) for several clients plus the official MCP Registry entry (server.json).

Install

Claude Code (and Grok Build)

claude plugin marketplace add actionflow-team/needwing-plugins
claude plugin install needwing@needwing

or inside a session: /plugin marketplace add actionflow-team/needwing-plugins and /plugin install needwing@needwing. Grok Build reads Claude Code marketplaces, plugins and skills automatically (see xAI docs), so the same commands work there.

Codex

codex plugin marketplace add actionflow-team/needwing-plugins
codex plugin add needwing@needwing-plugins

Without plugins, add the remote server directly (OAuth: run codex mcp login needwing afterwards to sign in an existing account on the sign-in address; key: export NEEDWING_API_KEY first):

From the project's README.