Plures MCP

What plures-mcp does

plures-mcp gives MCP-compatible agents access to Plures human verification workflows. An agent can submit a question, possible answers, and supporting context for review by multiple people whose identities are verified through government ID and a selfie check. The service returns the selected answer along with the strength of agreement and the individual votes.

The server exposes two tools. ask_humans is intended for decisions with defined options, such as checking whether an answer follows policy or interpreting a customer's tone. ask_judgment supports preferences, ratings, and sign-offs. For decisions involving money or accounts, requests can be routed to the user's own team with route: "team".

How it works

The agent sends Plures the question, options, and material to evaluate. Three verifiers are used by default, and a request can involve up to nine. They answer independently, with each response confirmed by Face ID, a fingerprint, or a passkey. When responses are split, Plures can ask additional people until a majority is reached or the configured limit is exhausted.

Results include an answer, an agreement value from 0 to 1, and the votes. A client can wait for the result or use a webhook-based flow in the broader Plures API. If a team is configured and the reviewers do not reach agreement, Plures can email the team a decision link and return the team decision as the final answer.

Setup and configuration

Run the MCP server with npx and provide the account key through PLURES_API_KEY:

{
  "mcpServers": {
    "plures": {
      "command": "npx",
      "args": ["-y", "plures-mcp"],
      "env": { "PLURES_API_KEY": "pk_test_..." }
    }
  }
}

The same configuration pattern can be used with Claude Desktop, Claude Code, Cursor, and VS Code. A free test key is available from Plures; test keys return immediate responses without contacting real reviewers, which supports development of the integration flow.

API keys belong to a Plures account rather than an individual. Account members can be assigned owner, developer, or viewer access in the Plures dashboard, while the key remains usable when a member leaves.

Tools and capabilities

• Submit defined-option decisions to ask_humans for independent human answers.
• Request preferences, ratings, and sign-offs with ask_judgment.
• Include context or material for reviewers to assess.
• Receive consensus, agreement strength, and votes.
• Escalate unresolved or selected decisions to a configured team.
• Use test keys for immediate, non-production responses.

Limitations and notes

Human review is not necessarily unanimous: requests can return a split result or expire, so agents should define how to handle insufficient agreement. Reviewers are selected and verified by Plures, and they do not see agent metadata. The normal reviewer count is three, with a maximum of nine. Team routing depends on having a team configured in the Plures dashboard.

Production integrations can use webhooks rather than waiting for a response, but webhook deliveries must be checked with Plures' verifyWebhook function in JavaScript or verify_webhook in Python. The MCP package itself is launched through npx and requires a Plures API key.