What Librarians Need To Know About Scite MCP & Institutional Access

Students and researchers have a new way to work with scientific literature by connecting tools like Claude or ChatGPT to Scite via the MCP protocol. This allows AI assistants to pull from Scite's citation database while you chat. You can search literature, check citation context, and even access full texts without leaving your AI tool. And setting it up only takes a few minutes.
One thing to keep in mind: your institutional access doesn't come from your Claude or ChatGPT account. It comes from your Scite account. If you set up the connection without signing into the correct Scite account, you'll still get Scite's functionality, but you won't have access to the licensed content your institution has already negotiated and paid for.
Here's how the access process works, how to link your account to your institution's license, and what to do if things aren't working as expected.
It Starts with Your Scite Account, Not Your AI Tool
When you add the Scite MCP to an AI client like Claude, ChatGPT, or another supported tool, you'll need to sign in to Scite using OAuth. This sign-in sets the permissions for your session. Whatever access that Scite account carries, the MCP session inherits. If the account is associated with an institutional license, you'll also get full-text access and article links that work through your library's catalog.
In practice, you can think of the AI tool as just the interface. Scite handles the actual work. So, it matters more if your Scite account has access than your Claude account.
Three Ways Your Account Gets Recognized
Institutional access gets attached to a Scite account in one of three ways.
The first is campus IP. Sign into Scite from a campus network, and the IP range match ties your account to the institutional license automatically. Off-campus users who haven't yet established their institutional connection can start by logging in once from campus or via VPN, and the license attaches.
The second is institutional email. If the email address on your Scite account is your university address (the one ending in .edu or your institution's domain), the system will match it automatically. No additional steps required.
The third is single sign-on (SSO). If your institution has configured SAML, users who log into Scite through SSO are automatically recognized. SSO isn't something end users can self-configure. It's set up at the organizational level by account admins working with Scite's Implementations Team.
For most academic licenses, once your account is linked to your institution, it stays connected. You can use Scite on or off campus, on any device, and with any AI client. If you link your account correctly the first time, you won't need to do it again.
What To Tell Students Before They Set Up The MCP
The most reliable setup path is straightforward: when adding the Scite MCP connection, students will sign into their Scite account as part of the process. Using their institutional email for that account is the surest way to ensure the license gets recognized.
Once that's in place, the connection works the same way regardless of which AI tool the student is using. Students can confirm institutional access by visiting their subscription page. Librarians are encouraged to share this link during onboarding or in setup documentation. This approach avoids fielding individual support requests and gives students immediate confirmation that everything is configured correctly.
When It Works In One AI Tool, But Not Another
Sometimes a student finds that Scite works in Claude but not in ChatGPT, or vice versa. There are usually two main reasons for this.
The first reason is mismatched accounts. If the student used a different Scite account during each setup, or set one up while on campus and the other while off campus, before the license was attached, the sessions are drawing from different account permissions. The fix is making sure the same institutional Scite account is used for every MCP connection.
The second is a known ChatGPT behavior: MCP connections can silently disconnect. The tool may appear set up even when the connection has dropped without any error message. Refreshing the Scite connection in ChatGPT's settings and making sure the student is actively tagging @Scite when prompting usually resolves it. When troubleshooting, start with the subscription page. If institutional access shows as active there, the Scite side is working correctly, and the issue is in the client. MCP is a relatively new standard, and individual platforms are still working through edge cases. Some friction during setup is normal and tends to resolve as the technology matures.
Search Results Aren't Filtered By Your Holdings, & That's A Good Thing
A common question is whether Scite shows articles from a library's holdings first in search results.
The answer is no.
Results are ranked by relevance and citation signals, not by what the library subscribes to. Holdings only affect how users access a paper, not whether it appears in the results. For each result, Scite offers several ways to access the full text: through your institution's proxy or catalog links, open access if available, or Article Galaxy for anything that falls outside both. This way, researchers get the most relevant results regardless of their institution's specific agreements, with their library's subscriptions determining the path to the full text.
That's a meaningful distinction for librarians explaining the tool's value to faculty and students. The search isn't filtered to what the institution owns. It's filtered by what's scientifically relevant. The library's license determines the click-through experience.
Getting Your Patrons Set Up Right The First Time
A few things that make a practical difference during implementation:
- Encourage students to use their institutional email when setting up their Scite account. It's good practice, and it's the surest way to make sure their license is recognized when they add the MCP connection.
- Include a link to the subscription page in setup guides or LibGuides related to AI research tools. This allows students to verify their access independently.
- For institutions with SAML configured, note that SSO Scite login is an alternative path to institutional recognition, useful for students who may not have or use a .edu email address. SSO via SAML is available to any institutional license holder that chooses it as an option, at no additional cost.
Researchers worldwide use Scite to better understand research, surface debates in the literature, avoid citing retracted or contradicted studies, and strengthen their writing. Getting the institutional access piece right means students benefit from the full version of that capability, rather than the free tier, whenever they use Claude, ChatGPT, or other connected AI tools.
