Skip to content
Quevell
RU
Menu

MCP

Connecting ChatGPT, Codex and Claude to Quevell: rights, action approval, history, revocation and files.

Updated 19 Oct 2026

Connection address

MCP lets an AI application perform ordinary work in Quevell within a person's or service account's rights. Administration, billing and granting rights are unavailable through MCP. Your company owns the connection address:

https://<key>.quevell.com/api/mcp

Replace <key> with your company key. Use HTTPS. Client and plan capabilities are checked separately: a successful read does not prove writing or file transfer.

Whose authority the application uses

  • Personal connection. Sign in to Quevell normally, complete the second factor when required, review company, application, return address and requested actions, then approve access. The application acts as you with your current rights. Reading needs mcp.read, writing also needs mcp.write; offline_access permits token refresh while the original session and connection remain valid. A personal OAuth token works only at MCP and does not open other REST methods.
  • Service account. It has its own project rights and revocable credentials from Service accounts. Its token does not become a person's personal login. Server support for client_credentials does not imply support in every cloud application. Do not put secrets in a prompt or report.

Connecting clients

Client verification status. ChatGPT passed live connection, read, write, revocation and reconnection checks in a test company. Production connection is also confirmed. On 19 October 2026, the owner confirmed production connection, reading and writing through Claude, followed by revocation in the Quevell profile and successful reconnection. Claude file transfer and dangerous-action approval have not yet been checked. Desktop and Code have not been accepted separately. File transfer in ChatGPT has not yet been checked.

ChatGPT: Quevell MCP Plugin

  1. In ChatGPT Plugins, add a custom MCP server. Name the connection Quevell MCP Plugin.
  2. Enter your company MCP URL from the example above and choose OAuth. OAuth addresses and client settings are discovered automatically; no service account or service secret is required.
  3. Sign in to your account on the Quevell page, check the company and requested actions, then approve access.
  4. In a new chat, select Quevell MCP Plugin using @. Ask: "Call list_projects with offset 0, limit 10. Change nothing." You can then read your own issue with get_issue.

Availability depends on your plan and workspace policies. Check menu names against the official ChatGPT instructions. Quevell may show the verified application as ChatGPT: that is the OAuth client name; Quevell MCP Plugin is the plugin name.

If ChatGPT says authorization is invalid or expired, start a new connection from ChatGPT and use a fresh consent page. If it fails again, give support the attempt time, error text and correlationId when available. Do not forward OAuth URLs with parameters, codes or tokens. The message alone does not establish the cause.

Codex CLI

Add an HTTP server and request the scopes:

codex mcp add quevell --url https://<key>.quevell.com/api/mcp
codex mcp login quevell --scopes mcp.read,mcp.write,offline_access

Reading alone needs mcp.read; refreshing access needs offline_access. If your version requires a predefined public client ID, add --oauth-client-id quevell-codex when adding the server. That login carries the public-client assurance label. For a separate service integration use --bearer-token-env-var QUEVELL_MCP_TOKEN: supply the value through a protected environment; configuration stores the variable name, not the token. Commands were checked against CLI 0.160.0.

Claude in the browser or Desktop

Add a remote connector with the company URL and complete Quevell OAuth. Check each client you use; support in one does not prove support in another. See the official Claude instructions.

Claude Code

For HTTP you can explicitly configure requested scopes:

claude mcp add-json quevell '{"type":"http","url":"https://<key>.quevell.com/api/mcp","oauth":{"scopes":"mcp.read mcp.write offline_access"}}'
claude mcp login quevell

In the interactive client, login is also available through /mcp. If a predefined public client ID is required, use quevell-claude-code without a secret. Check your version against the official Claude Code instructions.

Writes and retries

A write carries a UUID requestId: a network retry reuses that UUID and identical arguments. A new intention uses a new UUID. Changes use the version actually read; a conflict does not silently substitute a newer version.

Dangerous-action approval

Some actions require a separate human decision. Open the returned Quevell link and review the exact operation. Opening, reloading and approval alone execute nothing: the application then retries the original MCP call with current rights and version checked again.

Action history

History distinguishes the person or service account, MCP channel and application. The "public OAuth client (no application signature)" label describes the application. The user completes normal sign-in and grants access. "Verified application" indicates a checked client signature. Records without assurance information show "application identity not verified". Verified service-integration credentials do not identify an AI model. Work and history remain limited by ordinary Quevell rights.

Revoking access

In Profile → Connected applications, choose Revoke for the connection. Its old token stops working; a new connection needs new consent. Ending the original session also ends delegation. For service mode revoke the service account's OAuth client or token. Removing configuration from the AI client alone does not revoke server authority.

Files

MCP file tools follow the same authorized operations. The server upload limit is 10 MB; a client may have a lower limit or no suitable file-transfer mechanism. One successful small request does not prove its file-picker support.