Agent 365 Bridge for Claude Code

Connect Claude Code to Microsoft Agent 365 MCP servers — giving Claude direct access to Outlook Mail, Calendar, Word, Excel, PowerPoint, Teams, SharePoint, OneDrive, Copilot Search, Knowledge, and User Profile data through the enterprise-grade MCP tooling gateway.

Architecture

┌─────────────┐      stdio       ┌──────────────────┐     HTTPS + Auth     ┌─────────────────────────┐
│ Claude Code  │ ◄──────────────► │  MCP Proxy Bridge │ ◄──────────────────► │  Agent 365 MCP Servers  │
│ (CLI / IDE)  │   MCP protocol   │  (this project)   │   StreamableHTTP    │  (Mail, Calendar, Word, │
└─────────────┘                  └──────────────────┘                      │   Teams, SharePoint...) │
                                                                           └─────────────────────────┘

The bridge runs as a local stdio MCP server that Claude Code connects to. When Claude calls a tool (e.g. createMessage, getEvents), the bridge authenticates with Azure Entra ID using delegated permissions and forwards the call to the appropriate Agent 365 MCP server — acting on behalf of the signed-in user.

Two-Layer Disk Caching

Claude Desktop enforces a 5-second timeout on tools/list requests. Since discovering 14 Agent 365 servers takes ~20 seconds, the bridge uses a two-layer caching strategy to serve tools instantly:

sequenceDiagram
    participant User
    participant Login as npm run login
    participant Disk as ~/.agent365-bridge/
    participant Bridge as Bridge Process
    participant Claude as Claude Desktop

    Note over User,Login: One-time setup
    User->>Login: npm run login
    Login->>Login: Device code auth
    Login->>Disk: auth-record.json
    Login->>Login: Discover 14 servers (56 tools)
    Login->>Disk: tools-cache.json

    Note over Bridge,Claude: Every subsequent launch
    Claude->>Bridge: initialize
    Bridge->>Disk: Load tools-cache.json
    Bridge-->>Claude: initialize response
    Claude->>Bridge: tools/list
    Bridge-->>Claude: 56 tools (instant, <1ms)
    Note over Bridge: Discovery runs in background (~20s)
    Claude->>Bridge: tools/call SearchMessages
    Note over Bridge: Waits for live discovery if needed
    Bridge-->>Claude: Email results

Compatibility Layer

The bridge automatically fixes common MCP compatibility issues:

1. Schema Sanitization: Strips oneOf, allOf, and anyOf from tool schemas (which Anthropic API rejects), merging properties where possible.
2. Name Deduplication: Detects tools with identical names across different servers (e.g. GetDocumentContent in both Word and Excel) and automatically namespaces them (e.g. GetDocumentContent_Word) to prevent collisions.

Why this project exists?

While Microsoft provides a rich set of tools for building and managing AI agents, there is currently a "protocol gap" for 3rd-party coding agents like Claude Code:

1. Protocol Translation: Claude Code and most local IDEs speak the stdio dialect of the Model Context Protocol (MCP). However, the Agent 365 Tooling Gateway (the enterprise cloud back-end) speaks StreamableHTTP. This project acts as the necessary protocol translator.
2. Access to the "Synthetic Workforce": Agent 365 is designed to be the control plane for a new generation of autonomous agents. This bridge allows Claude to tap into that same infrastructure, giving a 3rd-party LLM the same enterprise-governed tools used by Microsoft's first-party agents.
3. Action over Search: Unlike pure semantic search tools (like WorkIQ), this bridge focuses on deterministic actions. It exposes the granular Tooling Servers for Mail, Excel, Word, and Teams, allowing Claude to manipulate data, not just find it.
4. Developer-First Auth: It simplifies the complex "Frontier Preview" and "StreamableHTTP" authentication handshake into a standard MCP sign-in flow that just works.

Status

✅ Production-tested and working — Successfully authenticated and discovered 20+ tools from Microsoft Agent 365 MCP servers (Mail, Excel, Knowledge, and more confirmed).

Prerequisites

Setup Guide

Step 1: Install & Build

git clone https://github.com/ITSpecialist111/Agent365-Bridge.git
cd Agent365-Bridge
npm install
npm run build

Step 2: Create an Azure AD App Registration

You need an Azure AD app registration to authenticate with the Agent 365 platform. Follow these steps in the Azure Portal:

2a. Register the application

1. Navigate to Microsoft Entra ID → App registrations → New registration
2. Fill in the details:
   • Name: Agent365-Claude-Bridge (or any name you prefer)
   • Supported account types: "Accounts in this organizational directory only" (Single tenant)
   • Redirect URI: Leave blank
3. Click Register

2b. Collect the required details

From the app registration Overview page, copy these two values:

2c. Create a client secret (optional — server deployment only)

Note: If you're only using Claude Code / Claude Desktop with the default Device Code sign-in flow, you can skip this step entirely. The Device Code flow is a public client flow and does not require a client secret.

A client secret is only needed if you plan to:

• Deploy the bridge as an HTTP server with On-Behalf-Of (OBO) auth (AUTH_MODE=obo)
• Use Application permissions with Client Credentials (AUTH_MODE=client_credentials)

1. Go to Certificates & secrets (left sidebar)
2. Click New client secret
3. Enter a description (e.g. Agent365 Bridge) and choose an expiry period
4. Click Add
5. Copy the "Value" immediately — this is your AZURE_CLIENT_SECRET

⚠️ The secret value is only shown once. If you lose it, you'll need to create a new one.

2d. Add API Permissions

1. Go to API permissions (left sidebar)
2. Click Add a permission → APIs my organization uses
3. Search for Agent 365 Tools (or the app ID ea9ffc3e-8a23-4a7d-836d-234d7c7565c1)
4. Select Delegated permissions and add the scopes you need:

5. Click Grant admin consent for [your organization] (blue button at the top)
6. Verify that each permission shows a green ✅ checkmark under Status

2e. Enable public client flows

This is required for the device code sign-in flow:

1. Go to Authentication (left sidebar)
2. Scroll to Advanced settings at the bottom
3. Set "Allow public client flows" to Yes
4. Click Save

Step 3: Configure the .env file

Create a .env file in the project root with your credentials:

# Azure Entra ID Authentication
AZURE_TENANT_ID=your-directory-tenant-id
AZURE_CLIENT_ID=your-application-client-id

# Client secret — only needed for OBO (server) or client_credentials mode.
# For the default Device Code flow (Claude Code / Claude Desktop), leave this blank or omit it.
# AZURE_CLIENT_SECRET=your-client-secret-value

# Agent 365 Configuration
MCP_PLATFORM_ENDPOINT=https://agent365.svc.cloud.microsoft
MCP_PLATFORM_AUTHENTICATION_SCOPE=ea9ffc3e-8a23-4a7d-836d-234d7c7565c1/.default

# Runtime
NODE_ENV=development

Step 4: Sign In (One-Time)

Sign in to Microsoft 365 and cache your credentials:

npm run login

You'll be prompted to visit a URL, then tools will be discovered and cached:

Agent 365 Bridge — Sign In & Setup

Step 1: Sign in to Microsoft 365
[agent365-bridge] SIGN IN REQUIRED
[agent365-bridge] Go to: https://microsoft.com/devicelogin
[agent365-bridge] Enter code: XXXXXXXX

✅ Authentication successful!
   Credentials cached at: ~/.agent365-bridge/auth-record.json

Step 2: Discovering Agent 365 MCP servers...

✅ Discovered 56 tools across 14 servers

🎉 Setup complete!
   Claude Desktop will now load all tools instantly.

To complete sign-in:

1. Open https://microsoft.com/devicelogin in your browser
2. Enter the code shown in the terminal
3. Sign in with your Microsoft 365 account
4. Wait for tool discovery to complete (~20 seconds)

Note: This only needs to be done once. Both credentials and the tool list are cached to disk. Tokens refresh automatically on subsequent launches. Run npm run logout to clear cached credentials.

Step 5: Register with Claude Code / Claude Desktop

For Claude Code (CLI):

npm run register

This registers the bridge as a global MCP server in Claude Code. After this, Agent 365 tools are available in any Claude Code session.

For Claude Desktop, add the bridge to your config file (%APPDATA%\Claude\claude_desktop_config.json):

{
  "mcpServers": {
    "agent365-bridge": {
      "command": "node",
      "args": ["C:/path/to/your/Agent365/dist/index.js"]
    }
  }
}

Step 6: Use Claude Code

Open Claude Code — Agent 365 tools will appear automatically. Try:

> Search my Outlook inbox for emails about the Q4 report
> Create a new Word document summarizing the project status
> List my upcoming calendar events for this week
> Post a message in the Engineering team channel
> Find files in SharePoint related to the budget
> Create an Excel workbook with monthly revenue data

Universal MCP Support (Claude Desktop & Others)

This bridge complies with the Model Context Protocol (MCP) specification, meaning it can be used with any MCP-compatible client, not just Claude Code CLI.

adding to Claude Desktop (Windows/Mac)

To use Agent 365 tools inside the Claude Desktop app:

1. Open your config file:

   • Windows: %APPDATA%\Claude\claude_desktop_config.json
   • Mac: ~/Library/Application Support/Claude/claude_desktop_config.json

2. Add the bridge configuration:

{
  "mcpServers": {
    "agent365-bridge": {
      "command": "node",
      "args": [
        "C:/path/to/your/Agent365/dist/index.js"
      ]
    }
  }
}

Note: Update the path to match where you cloned this repository.

3. Restart Claude Desktop. The tools will appear in the 🔌 menu.

Available MCP Servers

The bridge connects to all 13 Agent 365 MCP servers:

Agent 365 Bridge vs. Microsoft WorkIQ

While this bridge connects Claude to the core Agent 365 infrastructure for action and orchestration, Microsoft also provides WorkIQ, an "intelligence layer" for M365.

Using Both Together

For the best experience, we recommend running both servers side-by-side in Claude. This gives Claude "hands" (the bridge) and a "brain" (WorkIQ).

Claude Desktop Configuration (%APPDATA%/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "agent365-bridge": {
      "command": "node",
      "args": ["C:/Path/To/Agent365-Bridge/dist/index.js"]
    },
    "workiq": {
      "command": "npx",
      "args": ["-y", "@microsoft/workiq", "mcp"]
    }
  }
}

[!NOTE] WorkIQ is currently in Public Preview. For setup instructions and admin consent details, visit the official WorkIQ repository.

Authentication Modes

Project Structure

├── src/
│   ├── index.ts                    # Entry point
│   ├── auth/
│   │   ├── token-provider.ts       # Device Code / Client Secret / Bearer auth
│   │   └── token-cache.ts          # JWT token caching with auto-refresh
│   ├── config/
│   │   ├── configuration.ts        # Loads .env + ToolingManifest.json
│   │   └── types.ts                # TypeScript interfaces
│   ├── discovery/
│   │   └── server-discovery.ts     # Discovers MCP servers (manifest or gateway)
│   └── proxy/
│       ├── mcp-proxy-server.ts     # stdio MCP server for Claude Code
│       └── tool-forwarder.ts       # Forwards tool calls to remote servers
├── scripts/
│   ├── setup.ts                    # Interactive setup wizard
│   ├── register-claude.ts          # Registers bridge with Claude Code CLI
│   └── start-mock.ts              # Starts mock server for development
├── ToolingManifest.json            # Declares 13 available MCP servers
├── .mcp.json                       # Claude Code project-level MCP config
├── .env.example                    # Environment variable template
├── package.json
└── tsconfig.json

npm Scripts

Troubleshooting

References

• Agent 365 Tooling Servers Overview
• Agent 365 SDK and CLI
• Agent 365 CLI Install (requires .NET 8+: dotnet tool install --global Microsoft.Agents.A365.DevTools.Cli --prerelease)
• Agent 365 Samples
• MCP Server Reference
• Frontier Preview Program

Disclaimer

Authentication & Liability: This project is an open-source bridge and is not an official Microsoft product. It uses your own Azure AD App Registration and operates under the context of the signed-in user. You are responsible for managing the security of your client secrets and tokens. The maintainers of this repository accept no liability for any data loss, security breaches, or unexpected charges incurred by using this software. Use at your own risk.