Consensus MCP server for Claude, Codex and Cursor

What your AI apps can do with Consensus

• Search research papers
• Summarize scientific findings

Consensus MCP tools

1 tool, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Suggested access for each AI app

The documentation this list comes from doesn't mark Consensus's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Consensus connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

1. Connect once. Add Consensus to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
2. Choose access per app. Give Claude Code every Consensus tool, give Cursor only the read tools, or keep Consensus away from an app entirely.
3. Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
4. Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Consensus MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

claude mcp add --transport http toolstile 'https://mcp.toolstile.com/mcp'

Then connect Consensus in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Consensus endpoint to each app separately. In Claude Code:

claude mcp add --transport http consensus 'https://mcp.consensus.app/mcp'

In Cursor's mcp.json:

{
  "mcpServers": {
    "consensus": {
      "url": "https://mcp.consensus.app/mcp"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the Consensus MCP documentation for what your client needs.

Before you connect

A Consensus account. Sign-in uses your Consensus permissions.

Server details

Consensus MCP documentation