Benchmark

Connect Benchmark

Connect your AI client and verify your workspace.

Paste this prompt into your AI client to start. Setup verification is free. Research can spend credits.

For persistent use, install the skill with the optional command below.

npx skills add https://benchmark.social --skill benchmark-setup

Connect Benchmark

Connect the current client to https://api.benchmark.app/mcp with OAuth. Complete free setup verification before research.

Reuse the current connection

Determine whether Benchmark tools are already available in this client. If available, call whoami and list_operations. Verify the workspace identity and available operations. If both calls succeed for the intended workspace, reuse this connection. Do not add another connection or change another client.

If the workspace is wrong, ask which workspace the user intends to use. If the client is unknown, ask which client the user uses. Use that client’s supported setup method. Do not install another client, overwrite configuration, or purchase a subscription.

Add a missing connection

For a CLI, read its installed help before a configuration change. Add only the Benchmark server entry. Preserve other server entries and settings. For a browser client, guide the user through its connection settings. The user completes OAuth sign-in and chooses the intended Benchmark workspace. Do not request passwords, API secrets, or copied OAuth tokens.

Claude Code

Run this command in the intended environment:

claude mcp add --transport http benchmark https://api.benchmark.app/mcp

Use /mcp in Claude Code to authenticate. See Claude Code MCP documentation if the installed command differs.

Codex

Use the MCP controls in the current Codex client, or its supported CLI commands:

codex mcp add benchmark --url https://api.benchmark.app/mcp
codex mcp login benchmark

Run these commands in the environment that supplies this client’s MCP connections. A CLI configuration does not necessarily configure a separate web client.

Cursor

Open Cursor’s MCP settings and add an HTTP server with this entry:

{"mcpServers":{"benchmark":{"url":"https://api.benchmark.app/mcp"}}}

Merge the entry with existing configuration. Use Cursor’s Connect or sign-in control to complete OAuth. See Cursor MCP documentation for current settings.

Claude, ChatGPT, or another web client

Use the current client’s custom connector or MCP app settings. Set the server URL to https://api.benchmark.app/mcp. Select OAuth when the client requests an authentication method. Complete Benchmark sign-in, enable the connection, and return to this conversation. If an administrator must enable custom connectors, explain that requirement and stop until access exists. If custom MCP is unavailable, explain the limitation without changing clients automatically. Manual client guidance is at benchmark.social/mcp#connect.

Verify and stop

Call whoami and list_operations through this client’s connection. Report the workspace identity and whether mutations are available. A read-only connection can still complete setup verification. Do not treat missing mutation access as permission to change scopes or billing. If tools remain unavailable, report the failed step and a specific next action. Do not claim success from configuration text alone.

Stop after these free verification calls. Ask for the intended task, bounded scope, and credit budget before paid research. For a supplied post or business content strategy, offer content-research. Do not call query or mutate merely to test the connection.