Scholar Gateway MCP

Live

OAUTH 2.0

AI

AI

Connect to Scholar Gateway to search Wiley's peer-reviewed academic literature — 8M+ articles from 2,000+ journals spanning sciences, healthcare.

  • Acts as the user: Every tool call runs as the authorizing user. Access and audit trail stay intact.
  • Credentials stay vaulted: AES-256 encrypted, resolved at request time, never stored in LLM context.
  • Scoped before every call: Per-user permissions enforced automatically. 90-day audit trail included.
Scholar Gateway MCP
agent · Acme Q3
Run
Semanticsearch in Scholar Gateway MCP
S
scholargateway_semanticsearch
85ms
Scholar Gateway MCP agent
Searches a full-text academic corpus and returns relevant passages with citation metadata. when to use: use this tool f.
Sources: Scholar Gateway MCP
scholargatewaymcp
1 tool call
18:29
Message Claude...

Scholar Gateway MCP tools for AI agents

CALL ANY TOOL
1 tool covering semanticsearch.
scholargateway_semanticsearch
Searches a full-text academic corpus and returns relevant pa
Searches a full-text academic corpus and returns relevant passages with citation metadata. when to use: use this tool for research questions, factual claims, literature-backed explanations, evidence-based summaries, and any response where academic support would improve accuracy, credibility, or depth. submit queries as complete natural language questions — preserve the full intent and do not reduce to keywords. for ambiguous or polysemous terms, expand to full context before searching (e.g. use 'multiple sclerosis' not 'ms'). cite all substantive claims inline using author-year format with doi hyperlinks. when not to use: do not use for general web searches, non-academic topics, or when the question requires real-time or proprietary data not covered by the academic corpus.
Parameters
Name
Type
Required
Description
query
string
Required
Natural language research question. Preserve intent, scope, and structure. Rewrite for semantic clarity but do not compress to keywords. Expand acronyms and add field context for ambiguous or polysemous terms.
end_year
string
Optional
Inclusive upper bound for publication year filter. Omit to include publications up to the present.
includeRetractedContent
boolean
Optional
Whether to include retracted publications in results. Default false; set true only when retraction history is itself the subject of inquiry.
start_year
string
Optional
Inclusive lower bound for publication year filter. Omit to search across all available years.
topN
integer
Optional
Number of passages to return. Higher values improve recall for broad or multi-faceted queries; lower values are appropriate for narrow or well-defined topics.
Build your Agent
Same auth pattern across every framework.
Python · LlamaIndex
from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="scholargateway")

mcp = MultiServerMCPClient({
"scholargateway": {
"url": "https://mcp.scalekit.com/scholargateway",
"headers": {"Authorization": "Bearer " + token}
}
})
tools = await mcp.get_tools()
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "scholargateway" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/scholargateway
// Pass: Authorization: Bearer + token
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "scholargateway" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/scholargateway
// Pass: Authorization: Bearer + token
from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="scholargateway")
# Connect to MCP at https://mcp.scalekit.com/scholargateway
# Pass: Authorization: Bearer + token
Try these prompts
Paste any prompt into your agent to get started.
Get started
Copy the prompt
Copied
What can I do with Scholar Gateway MCP?
Copy the prompt
Copied
Show me all available tools in Scholar Gateway MCP.
SEE HOW AUTH WORKS
User authorises once. Every agent call after uses their token with scope enforcement.
1
Authorize
Your user connects
Scholar Gateway MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Scholar Gateway MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Scholar Gateway MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Scholar Gateway MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other connectors.
No items found.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
One connector today. Ten tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Scholar Gateway as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Scholar Gateway OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Scholar Gateway?
Yes. Pass a tool name filter to listScopedTools so the AI agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Scholar Gateway.

What happens when a user revokes Scholar Gateway access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Does article access respect Wiley licensing?
Yes. Searches across Wiley's 8M+ peer-reviewed articles run with the authorizing user's Scholar Gateway entitlements, so full-text access matches what that user's institution licenses.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""scholargateway"": {
""url"": ""https://mcp.scalekit.com/scholargateway"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.scholargateway]
url = ""https://mcp.scalekit.com/scholargateway""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""scholargateway"": {
""url"": ""https://mcp.scalekit.com/scholargateway"",
""type"": ""http""
}
}
}