- Home
- Skills
- APIs & Backend
- AI Chief of Staff
AI Chief of Staff
Configure and troubleshoot the self-hosted Microsoft 365 MCP server for AI agents using Microsoft Graph.
$30
Works with the AI Agents you already use
AI Chief of Staff
Example session with this skill installed
Microsoft 365 MCP Setup Review
I’ll help you troubleshoot the setup using the repository’s documentation and the configuration details you choose to share. I have not accessed your Microsoft 365 tenant, inspected your local .env file, or verified live authentication.
1. Initial checks
| Area | What to verify | Why it matters |
|---|---|---|
| Environment configuration | Confirm the required variable names are present and populated locally. | Missing or mismatched configuration can prevent authentication. |
| Microsoft Entra application | Compare the tenant and application identifiers with the registered application. | Incorrect identifiers can cause token acquisition failures. |
| Authentication flow | Confirm the configuration matches the authentication method documented for the server. | Application permissions and delegated permissions behave differently. |
| Microsoft Graph permissions | Match the requested operation to its documented permission requirements. | A successful login does not guarantee authorization for every operation. |
| Administrator consent | Check whether required application permissions have received the appropriate consent. | Missing consent can result in authorization errors. |
| Server configuration | Follow the documented setup guide to verify the intended entry point and client configuration. | Incorrect startup settings can prevent the MCP client from connecting. |
2. Troubleshooting approach
Start by identifying the exact error category, such as token acquisition failure, HTTP 401, HTTP 403, or an MCP connection error.
Next, check the relevant configuration locally. Do not paste client secrets, access tokens, private keys, or unredacted environment files into the conversation.
For an HTTP 403 response, identify the affected operation and compare its documented permission requirements with the permissions actually granted to the application. Do not add broad permissions simply to make an error disappear.
For a connection failure, verify the documented startup command, transport configuration, and client settings before changing the application registration.
3. Next steps
- Identify the exact error message, with sensitive values removed.
- Check the relevant section of the setup or permissions guide.
- Apply only the configuration changes justified by the findings.
- Follow the repository's documented verification procedure.
- Record any unresolved limitation instead of claiming that authentication or connectivity has succeeded.
Scope: This skill provides documentation-based setup and troubleshooting guidance. It does not independently prove that a tenant is configured correctly or that a live Microsoft Graph request has succeeded.
- Read your context and instructions
- Compiled the ai chief
Connects securely to your tools. The creator never sees your data.
About this skill
Configuring a self-hosted Microsoft 365 MCP server is prone to authentication errors and permission mismatches. This skill provides the precise configuration steps and Microsoft Graph permission mappings required to connect your AI agent to a Microsoft 365 tenant.
What it does
- App registration guidance helps you register the Microsoft Entra ID application and configure OAuth 2.0 client credentials.
- Permission mapping identifies the specific Microsoft Graph application permissions required for mail, calendar, and file modules.
- Environment configuration assists in populating
.envfiles with tenant IDs and redacted secrets for secure local execution. - Connection troubleshooting diagnoses authentication failures, token errors, and server startup issues for Claude Desktop or Cursor.
- Capability validation explains which M365 features work under app-only flow and which are restricted by Microsoft API limitations.
How it works
- Inspection of the
ms365-ai-assistant-mcprepository to verify the existing configuration and entry points. - Permission selection using the internal guides to match required tools (e.g.,
Mail.ReadWrite) to the Entra ID app. - Setup execution following documented steps for installation, environment variables, and server initiation.
- Health checking via the built-in diagnostic tools to verify live Microsoft Graph reachability and authentication.
Frameworks & tools
This skill supports the Model Context Protocol (MCP) and Python-based server implementations. It focuses on Microsoft Graph API, Microsoft Entra ID (Azure AD), and OAuth 2.0 client-credentials flows.
Why this beats prompting it yourself
Generic prompts often fail to account for the strict limitations of app-only authentication, such as the lack of support for Excel endpoints. This skill uses specific repository documentation to ensure you don't waste time troubleshooting features that Microsoft explicitly restricts for service principals.
Use cases
- Configuring a new MCP server to allow Claude to read Outlook calendars.
- Fixing "403 Forbidden" errors during Microsoft Graph API requests.
- Setting up a secure
.envfile for a self-hosted M365 agent. - Verifying which Graph permissions follow the principle of least privilege for your tenant.
Known limitations
Does not support Excel workbook endpoints or general Teams channel messaging due to Microsoft app-only API restrictions. Requires an active Microsoft 365 tenant with administrative access.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
No support for Excel workbook endpoints or Teams channel messages. App-only flow lacks per-user isolation. Requires Microsoft 365 tenant admin rights for permission consent.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 22 days ago
- Accounts
Outlook
Anthropic
- Software
- Ms365 Ai Assistant MCP
PythonAware MCP
Git
Permissions
Allowed Hosts
File Scopes
Access to Microsoft Graph and the relevant AI agent platform is needed only when required by the user's chosen setup and troubleshooting workflow. File access is intended for reviewing the MCP server's setup instructions, configuration templates, and relevant project files. Network access may be needed to consult documentation or communicate with configured services. Environment variables may contain sensitive credentials, so users should keep secrets in local environment files or an approved secrets manager and never share them in prompts or logs. Microsoft Graph permissions must be configured according to the specific operations required and the principle of least privilege. This skill provides configuration guidance; it does not itself grant tenant permissions or guarantee successful live connectivity.