Skip to main content
Scite MCP is a hosted Model Context Protocol server that lets AI tools search scientific literature and retrieve citation data in conversation. It powers Scite’s first-party ChatGPT plugin and Claude connector, and it works with any other MCP-compatible client. The plugin, connector, and MCP API are not separate data products. They are three ways to reach the same Scite tools.

Install Scite in ChatGPT or Claude

Scite plugin for ChatGPT

Open the Scite listing in ChatGPT, select Install plugin, and sign in with your Scite account. Use @Scite in a prompt to activate it.

Scite connector for Claude

Open the Scite listing in Claude’s Connectors Directory, select Connect, and sign in with your Scite account when prompted.
These first-party listings handle the MCP server configuration and use OAuth. You do not need to copy an MCP URL or create an API key. Availability may depend on your ChatGPT or Claude plan and workspace settings.

Choose your setup

See scite.ai/mcp for setup instructions for Claude Desktop, Claude Code, Gemini CLI, Copilot Studio, and other clients.

Authentication

First-party plugin and connector (OAuth)

Install Scite from the ChatGPT Plugin Directory or Claude Connectors Directory. The listing configures the connection; sign in with your Scite account when prompted. A Scite premium subscription is required.

Other MCP clients (OAuth)

Other interactive MCP clients use the standard OAuth 2.1 authorization-code flow with PKCE. Most discover Scite’s authorization and registration endpoints automatically after you provide https://api.scite.ai/mcp.
Every request to /mcp/oauth/authorize must include client_id, code_challenge, and code_challenge_method=S256. A client_id is obtained via Dynamic Client Registration (DCR); clients discover the registration endpoint from /.well-known/oauth-authorization-server.Some platforms, including Microsoft Copilot Studio, default to PKCE and DCR turned off. With those disabled, the authorize request omits required parameters and the server returns invalid_request. Enable PKCE and DCR-with-discovery, or supply a registered client_id.

MCP API (programmatic API key)

Need an API key? On Pro, create one in the API Console. Creating a key doesn’t grant every optional scope; see Authentication for feature access. For higher limits or managed credentials, contact sales. For scripts, servers, or your own MCP client: create an API key on Pro from the API Console, grant it the mcp scope, and send it as a bearer token to /mcp. No token exchange is needed. It shares your account’s MCP quota and billing. Enterprise customers can alternatively use issued client_id/client_secret credentials; see Authentication.

Endpoints

Methods

Example: search literature

search_literature supports Boolean operators, phrase search, and the same 25+ filters as the Search API. Call tools/list to see its full input schema.

Troubleshooting

  • 401 Unauthorized: the API key is missing, invalid, or revoked.
  • 403 User not authorized: the key or account doesn’t have the mcp scope.
  • invalid_request during browser authorization: confirm that the client enables PKCE and Dynamic Client Registration.
See Errors and rate limits for retry guidance.