> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scite.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Scite MCP
> Use Scite inside Claude, ChatGPT, and other AI tools: search the literature and pull citation stats without leaving the conversation.
Scite MCP is a hosted [Model Context Protocol](https://modelcontextprotocol.io/) 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
Open the Scite listing in ChatGPT, select **Install plugin**, and sign in with your Scite account. Use `@Scite` in a prompt to activate it.
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
| You want to… | Use | Setup |
| -------------------------------------------- | ----------------------------------------- | ---------------------------------------------------------------------------- |
| Use Scite in ChatGPT or Claude | The first-party plugin or connector above | Install, then sign in with Scite |
| Use Scite in another MCP-compatible AI tool | Scite's hosted MCP server | Connect the client to `https://api.scite.ai/mcp` and authenticate with OAuth |
| Build your own script, server, or MCP client | The MCP API | Call `https://api.scite.ai/mcp` with an `mcp`-scoped API key |
See [scite.ai/mcp](https://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](https://chatgpt.com/plugins/plugin_asdk_app_6952b3a3f1e881918951582d59483c78?q=scite) or [Claude Connectors Directory](https://claude.ai/directory/connectors/scite). 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](https://scite.ai/users/me/api). Creating a key doesn't grant every optional scope; see [Authentication](/authentication) for feature access. For higher limits or managed credentials, [contact sales](https://scite.ai/contact).
For scripts, servers, or your own MCP client: create an API key on Pro from the [API Console](https://scite.ai/users/me/api), 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](/authentication#enterprise-access).
## Endpoints
| Method | Path | Description |
| ------ | ------------- | ------------------------------------ |
| GET | `/mcp/info` | Server info and capabilities |
| POST | `/mcp` | JSON-RPC 2.0 endpoint for tool calls |
| GET | `/mcp/health` | Health check |
## Methods
| Method | Description |
| ------------ | ------------------------------------------------ |
| `initialize` | Returns protocol version and server capabilities |
| `tools/list` | Lists available tools and their schemas |
| `tools/call` | Execute a tool (e.g. `search_literature`) |
| `ping` | Heartbeat check |
## Example: search literature
```bash theme={null}
curl -X POST 'https://api.scite.ai/mcp' \
-H 'Authorization: Bearer ' \
-H 'Content-Type: application/json' \
-d '{
"jsonrpc": "2.0",
"id": "1",
"method": "tools/call",
"params": {
"name": "search_literature",
"arguments": {
"term": "\"machine learning\" AND healthcare",
"limit": 5,
"sort": "date",
"sort_order": "desc"
}
}
}'
```
`search_literature` supports Boolean operators, phrase search, and the same 25+ filters as the [Search API](/guides/search). 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](/errors-and-rate-limits) for retry guidance.