Quetext MCP Connector

Use Quetext plagiarism and AI detection inside MCP-compatible tools and apps.

The Quetext MCP connector gives Model Context Protocol tools and apps a secure way to create originality reports, check AI-generated text, retrieve completed results, and review account quota without leaving the writing or research workflow.

Remote MCP endpoint https://app.quetext.com/mcp Transport: Streamable HTTP Authorization: OAuth 2.1 Protocol version: 2025-06-18

Built for originality workflows in AI assistants

Quetext MCP makes originality review available where writing and research work is already happening. Users can ask a compatible assistant, tool, or app to submit text to Quetext, monitor report status, and return structured results from their own authorized Quetext account.

Plagiarism checker

Create plagiarism reports from assistant conversations and retrieve scores, matches, and source details when processing is complete.

AI Detection

Analyze text for AI-generated writing signals using Quetext AI detection through the same authorized account connection.

Secure account access

OAuth 2.1 authorization keeps access scoped to the user account, with tool permissions limited to the Quetext actions approved during the connection flow.

MCP connection details

The connector is hosted by Quetext. Users do not need to run a local server. Add the remote MCP URL in a compatible tool or app, authorize Quetext, and grant the requested tool permissions.

  1. Open your MCP-compatible tool or app. In an MCP-compatible tool or app, choose the option to add a remote MCP connector.
  2. Enter the Quetext MCP URL. Use https://app.quetext.com/mcp as the connector endpoint.
  3. Authorize your Quetext account. Complete the OAuth consent flow and grant the requested report and account scopes.
  4. Start checking content. Ask your MCP tool or app to create a plagiarism checker report, run AI detection, fetch report progress, or retrieve completed results.

Directory submission summary

Name
Quetext
Connector URL
https://app.quetext.com/mcp
Category
Writing, Education, Research, Productivity
Authentication
OAuth 2.1
Primary capabilities
Plagiarism checker, AI detection, report retrieval, quota lookup

Available MCP tools

The connector exposes a focused set of Quetext actions. Tool access is controlled by OAuth scopes and by the user's Quetext plan and quota.

ToolScopeWhat it does
create_plagiarism_reportplagiarism:writeSubmits text for plagiarism analysis and returns a report ID for progress polling.
create_ai_detection_reportai:writeSubmits text for AI detection and returns a report ID for retrieving the result.
get_report_progressreports:readChecks whether a report is still processing or ready to fetch.
get_plagiarism_reportreports:readFetches a completed plagiarism report with score, matches, and source details.
get_ai_detection_reportai:readFetches a completed AI detection report in a display-ready format.
list_reportsreports:readLists reports created through Quetext API and MCP workflows for the account.
delete_reportreports:deletePermanently deletes an API-created report by ID.
get_account_planaccount:readReturns the account plan and remaining plagiarism checker and AI detection quota.

Designed for user trust and assistant directories

Quetext MCP uses a hosted remote endpoint, OAuth authorization, scoped tool permissions, and account-level quota enforcement. Compatible tools and apps receive a clear, limited interface for originality checks without direct access to the broader Quetext application.

Frequently asked questions

Do users need to install anything locally?

No. Quetext MCP is a hosted remote connector. Users add the remote endpoint in a compatible MCP tool or app and authorize access through Quetext.

Does MCP use my Quetext account quota?

Yes. Report creation is tied to the authorized Quetext account and follows the plan, quota, and feature availability for that account.

Which tools or apps can use this connector?

The connector is built for tools and apps that support remote MCP over Streamable HTTP with OAuth authorization.