Skip to main content

Announcing StackOne Defender: leading open-source prompt injection guard for your agent Read More

SharePoint MCP Server
for AI Agents

Production-ready SharePoint MCP server with extensible actions — plus built-in authentication, security, and optimized execution.

SharePoint logo
SharePoint MCP Server
Built by StackOne StackOne

Coverage

19 Agent Actions

Create, read, update, and delete across SharePoint — and extend your agent's capabilities with custom actions.

Authentication

Agent Tool Authentication

Per-user OAuth in one call. Your SharePoint MCP server gets session-scoped tokens with zero credentials stored on your infra.

Agent Auth →

Security

Agent Protection

Every SharePoint tool response scanned for prompt injection in milliseconds — 88.7% accuracy, all running on CPU.

Prompt Injection Defense →

Performance

Max Agent Context. Min Cost.

Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every SharePoint call.

Tools Discovery →

What is the SharePoint MCP Server?

A SharePoint MCP server lets AI agents read and write SharePoint data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's SharePoint MCP server ships with pre-built actions, fully extensible via the Connector Builder — plus managed authentication, prompt injection defense, and optimized agent context. Connect it from MCP clients like Claude Desktop, Cursor, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.

All SharePoint MCP Tools and Actions

Every action from SharePoint's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.

Sites

  • List Sites

    Search and retrieve SharePoint sites across the organization using keyword search. This is the primary entry point for discovering sites - use "*" to list all accessible sites or provide specific search terms to find sites by name, description, or content.

  • Get Site

    Retrieve complete metadata for a specific SharePoint site by its unique identifier, including configuration details, timestamps, and optionally related resources like document libraries and lists. Use this after list_sites to get full site details or to verify site existence before performing operations.

  • Search Sites

    Find SharePoint sites matching a keyword search query with relevance-ranked results. Use this when you have a search term or site name fragment from a user and need to find matching sites. Unlike list_sites, search is required here and results are ordered by relevance rather than alphabetically.

Items

  • List Items

    Retrieve all items from a SharePoint list as structured data records with their field values. Supports filtering by column values and selecting specific columns. IMPORTANT - You must use expand=fields to get column data as field values are not included by default.

  • Get Item

    Retrieve a single item from a SharePoint list by its ID with complete metadata and field values. Use this to get detailed item data before updates, verify item existence, retrieve the web URL for sharing, or get the eTag for optimistic concurrency control.

Other (14)

  • Get Site By Path

    Retrieve a SharePoint site using its URL hostname and server-relative path instead of an opaque ID. This is the preferred method when you have a SharePoint URL from a user, document link, or browser address bar and need to resolve it to a site resource with its API-usable ID.

  • List Subsites

    Retrieve all immediate child subsites nested under a parent SharePoint site. Use this to navigate site hierarchies, discover departmental or project sites organized under a parent team site, and build site tree structures for navigation interfaces.

  • Get Root Site

    Retrieve the tenant's root SharePoint site collection without needing to know its ID. This is the primary entry point for discovering the organization's SharePoint structure, hostname, and top-level sites when starting fresh without prior context.

  • Get Site Columns

    Retrieve all site column definitions available at the site level for schema discovery. Site columns are reusable metadata field templates that can be added to multiple lists within the site, promoting consistent data schemas across the organization.

  • Get Site Content Types

    Retrieve all content type definitions available at a SharePoint site for understanding document and item templates. Content types bundle metadata columns with settings and behaviors, enabling consistent categorization of documents like contracts, invoices, or project documents across lists and libraries.

  • List Site Lists

    Retrieve all SharePoint lists in a site including document libraries, custom data lists, task lists, and system lists. Use this to discover available structured data containers before querying their items or to inventory a site's data assets.

  • Get List

    Retrieve detailed metadata for a specific SharePoint list including its template type, content type settings, creation date, and web URL. Use this to verify list existence, get sharing URLs, or understand list configuration before performing data operations.

  • Get List Columns

    Retrieve the complete schema of all columns in a SharePoint list including their data types, validation rules, and configuration. Essential for understanding list structure before querying items, building forms, or mapping data fields.

  • Get List Operations

    Retrieve the status of long-running background operations on a SharePoint list such as bulk imports, content type synchronization, or schema changes. Use this to monitor async operation progress, identify failed operations, or audit operation history.

  • List Site Drives

    Retrieve all document libraries (drives) available in a SharePoint site including their storage quota, ownership, and configuration. Use this to discover available file storage locations before browsing files or uploading documents.

  • Get Drive

    Retrieve detailed metadata for a specific SharePoint document library including current storage quota status, ownership information, and configuration. Use this to check storage availability before uploads, monitor quota usage, or get the shareable web URL.

  • List Drive Root Children

    List all files and folders at the root level of a SharePoint document library. Returns item metadata including name, size, type (file/folder), MIME type, and timestamps. Use list_drive_item_children to browse into subfolders.

  • List Drive Item Children

    List all files and folders within a specific folder in a SharePoint document library. Use this to navigate into subfolders after using list_drive_root_children to browse the root level.

  • Get Drive Item

    Retrieve complete metadata for a specific file or folder in SharePoint, including size, MIME type, permissions, and sharing links.

Set Up Your SharePoint MCP Server in Minutes

One endpoint. Any framework. Your agent is talking to SharePoint in under 10 lines of code.

MCP Clients

Agent Frameworks

Claude Desktop
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

More Documents & Knowledge MCP Servers

Confluence

133+ actions

Lokalise

101+ actions

ClickUp

92+ actions

Discourse

67+ actions

Google Drive

47+ actions

JotForm

44+ actions

Figma

39+ actions

SharePoint MCP Server FAQ

SharePoint MCP server vs direct API integration — what's the difference?
A SharePoint MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling SharePoint. A SharePoint MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling SharePoint at runtime. StackOne provides both.
How does SharePoint authentication work for AI agents?
SharePoint authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own SharePoint account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are SharePoint MCP tools vulnerable to prompt injection?
Yes — SharePoint MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — documents, messages, tickets, records, or free-text fields — is a potential vector. StackOne Defender scans every tool response before it enters the agent's context — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.
What is the context bloat of a SharePoint agent and how do I avoid it?
Context bloat happens when SharePoint tool schemas and API responses eat your SharePoint agent's memory, preventing it from reasoning effectively. A single SharePoint query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.
Can I limit which actions my SharePoint agent can access?
Yes — you can limit which actions your SharePoint agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my SharePoint MCP server?
Yes — you can create custom agent actions for your SharePoint MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research SharePoint's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a SharePoint MCP server?
Skip a SharePoint MCP server if your integration is purely software-to-software — direct SharePoint API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call SharePoint actions at runtime.
What AI frameworks and AI clients does the StackOne SharePoint MCP server support?
The StackOne SharePoint MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.

Put your AI agents to work

All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.