Hosted test pending
Cursor
Add BoxFetch as a remote MCP server, start with no credential, and complete the OAuth flow opened by the client.
Connect
Choose your MCP client
Every supported client starts from the same protected BoxFetch endpoint. The client follows discovery, opens BoxFetch for human consent, and receives its OAuth tokens without asking the human to copy them.
Client paths
Client readiness and connection entry points
BoxFetch is not an official listed connector in any client below. Exact tested commands, UI labels, and screenshots will be published after each client completes a real hosted acceptance run.
Read setup guidance
Hosted test pending
Claude
Use a custom connector or remote MCP entry when your Claude plan and workspace provide that capability.
Hosted test pending
ChatGPT
Use an eligible workspace that exposes custom connector or remote MCP configuration. Availability varies by plan and rollout.
Hosted test pending
Codex
Add the remote MCP server using the syntax reported by your installed Codex client, then follow the browser consent flow.
Standards path
Other MCP clients
Use a client that supports remote Streamable HTTP MCP, OAuth discovery, dynamic client registration, and PKCE S256.
Canonical endpoint
Use the protected MCP server
Configure https://app.boxfetch.ai/api/mcp/standard. Do not configure the operator HTTP fallback as a normal hosted-client connection.
Human control
Approve the exact client and scopes
Review the unverified client identity, exact redirect, selected agent, and requested scopes before approval. Revoke the grant or agent whenever needed.
Read the human onboarding path