SharePoint

Live

OAUTH 2.0

DOCUMENT MANAGEMENT

Files & Documents

Every document library, team site, and file your organization stores lives in SharePoint. SharePoint MCP gives your agent authenticated access to files and lists scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the SharePoint account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: Permissions enforced. 90-day audit trail.
SharePoint
agent · Acme Q3
Run
Find all SOW documents updated in the last 30 days across all project sites.
S
sp_search
93ms
Document agent
11 SOW documents updated in the last 30 days across 4 project sites. Most recent: Acme Corp SOW v3 (updated 2 days ago, Legal site). 3 flagged as pending approval in document metadata.
Sources: SharePoint, 4 sites, last 30 days
sharepointmcp
11 docs
18:29
Message Claude...

Tools your document agent reaches for on SharePoint, scoped per user.

CALL ANY TOOL
List sites and document libraries, browse and retrieve files, and search across all accessible SharePoint content.
sp_sites_list
List sites
List SharePoint sites the user has access to.
Parameters
Name
Type
Required
Description
search
string
Optional
Search by site name
limit
integer
Optional
Max sites
sp_lists_get
Get list
sp_items_list
List items
sp_file_get
Get file
sp_search
Search SharePoint
Build your Agent
Drop the toolkit in, point it at the user, and your document agent can use SharePoint from the first run.
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["sharepoint"], toolNames: ["sp_sites_list", "sp_lists_get", "sp_items_list"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["sharepoint"], toolNames: ["sp_sites_list", "sp_lists_get", "sp_items_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["sharepoint"], toolNames: ["sp_sites_list", "sp_lists_get", "sp_items_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/sharepoint",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start using SharePoint.
Search & find
Copy the prompt
Copied
Search SharePoint for [keyword].
Copy the prompt
Copied
Find all SOWs updated this month.
Copy the prompt
Copied
List all files in [library name] on [site].
Copy the prompt
Copied
Find contracts shared with [email].
Files & metadata
Copy the prompt
Copied
Get metadata for [file name] on [site].
Copy the prompt
Copied
List files in [document library].
Copy the prompt
Copied
Which files were modified today?
Copy the prompt
Copied
Get download link for [file name].
Sites & libraries
Copy the prompt
Copied
List all SharePoint sites I have access to.
Copy the prompt
Copied
List document libraries on [site name].
Copy the prompt
Copied
Which sites have been updated this week?
Copy the prompt
Copied
Find all pages in [site] with [keyword].
SEE HOW AUTH WORKS
Users authorize SharePoint once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
SharePoint
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
SharePoint
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
SharePoint
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
SharePoint
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
Same per-user auth pattern across other document agents and MCP connectors. Working code, live demos, fork what fits.
OPS
Email-to-calendar scheduling agent
Parse scheduling intent from Gmail threads and create Google Calendar events with the right attendees and timezone.
ENGINEERING
Engineering standup agent
Aggregate GitHub and GitLab activity, link to Jira, and post a daily standup digest to Slack. No async updates.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.
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 so attribution, audit, and scope stay accurate.
// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
SharePoint today. Others 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 SharePoint 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 SharePoint oauth 2.0 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 SharePoint?
Yes. Pass a tool name filter to listScopedTools so the document agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches SharePoint.
What happens when a user revokes SharePoint 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.
Can the agent read files in sites the user has no access to?
No. SharePoint inherits the authorizing user's site and library permissions. Sites the user cannot access in the browser are equally blocked for the agent. Microsoft 365 permission checks apply at every call.
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"": {
""sharepoint"": {
""url"": ""https://mcp.scalekit.com/sharepoint"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.sharepoint]
url = ""https://mcp.scalekit.com/sharepoint""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""sharepoint"": {
""url"": ""https://mcp.scalekit.com/sharepoint"",
""type"": ""http""
}
}
}