A
licenseB
qualityD
maintenanceMCP server for Microsoft Teams that exposes 73 tools to manage teams, channels, chats, messages, meetings, planner, calendar, apps, tabs, scheduling, search, and authentication via the Graph API.
73
17 npm
MIT
mcp-ignite-server
by Eric2XU
Related Servers
Alternatives to mcp-ignite-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables an AI agent to discover and call bounded Microsoft 365 tools for reading calendar, mail, Teams channels, SharePoint, and Power Platform metadata through MCP, with synthetic fixtures by default and optional Microsoft Entra/Graph tenant integration.8MIT
- FlicenseNot gradedqualityAmaintenanceEnables developers to build, run locally with debugging, and deploy to the cloud custom remote MCP endpoints hosted on Azure Functions, with built-in Microsoft Entra authentication. Sample projects demonstrate snippet CRUD and QR code tools, resource templates, prompt workflows, and an interactive weather demo UI.-
- AlicenseDqualityBmaintenanceEnables MCP clients to securely access and operate a Microsoft 365 tenant through the full Microsoft Graph API, covering mail, calendar, files, Teams, SharePoint, Planner, OneNote, Excel, admin, security, and more with 219 tools and guarded write capability.219MIT
- AlicenseCqualityDmaintenanceExposes Microsoft Fabric operations as MCP tools, with 105 tools across 17 domains including lakehouses, warehouses, notebooks, pipelines, and real-time analytics, handling long-running operations and supporting multiple authentication modes.100MIT
- AlicenseAqualityBmaintenanceMCP server for Microsoft 365 via the Microsoft Graph API, providing read-only access to profile, calendar, email, Teams chats, OneDrive files, and meeting transcripts from any MCP client.1612 npm3MIT
TDQS
A4/5.0
Scored across 7 tools
Disambiguation4/5
Most tools target clearly different resources: sessions, speakers, favorites, and schedule. get_favorites and get_my_schedule are conceptually similar user-session lists, but their descriptions distinguish favorites from schedule.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern using get_ or search_ prefixes, with resources and modifiers clear across the set. No casing or verb-style inconsistencies.
Tool Count5/5
Seven tools cover the conference content surface (sessions, speakers, user lists) without redundancy or bloat. The count is well-scoped for a specialized Ignite server.
Completeness4/5
Core discovery is covered: list/search sessions, get details, list/search speakers, and retrieve personal session collections. The main minor gap is the lack of mutation tools for favorites/schedule, but for a read-only conference data server the surface is functional.
Maintenance
ActivityInactive
ResponsivenessNo issues