MCP Server Development for Microsoft Tools

Job title: Build a Low-Latency MCP Server for Excel, Microsoft Project and Word
I’m looking for an experienced developer to build a Model Context Protocol (MCP) server and tools that allow an AI assistant to interact with Microsoft Excel, Microsoft Project and Microsoft Word through a connector.
The solution must be responsive, reliable and designed so its core functionality can later support a web application with multiple users.
Proposed functionality
The initial scope will be agreed before development, using these workflows as the starting point:
- Excel: Read and update worksheets, cells, tables and formulas, while preserving workbook formatting.
- Microsoft Project: Read and update tasks, dates, dependencies, milestones, resources and progress, while respecting scheduling behaviour.
- Word: Create and edit documents, populate templates, and update text and tables while preserving formatting.
- Cross-application workflow: Demonstrate a workflow such as reading project progress, updating an Excel tracker and generating a Word status report.
Please specify which application versions and environments your proposal supports, including desktop applications, cloud documents and file formats. Clearly distinguish live editing in an open application from processing saved files.
Technical requirements
- A working MCP server with clearly defined tools, input validation, structured results and useful error messages.
- Integration with an agreed AI client or connector, demonstrated end to end.
- Low latency for routine operations. Propose measurable response-time targets and benchmark them against agreed file sizes and workloads.
- Performance reporting that separates MCP/backend processing time from Microsoft service delays and AI response time.
- A modular backend that a future web application can reuse, with a clear approach to concurrent users, authentication and separation of user data.
- Secure credential handling and appropriate access permissions.
- Reliable handling of timeouts, throttling, retries and conflicting edits, including protection against duplicate changes.
- Clear disclosure of required Microsoft licences, third-party libraries, hosting costs and platform limitations.
I’m open to your recommended technology stack. Please explain the integration approach for each Microsoft application and any components that must run on a user’s computer.
Deliverables and milestones
1. Architecture and feasibility: Confirm supported environments, connector compatibility, initial tool list, performance targets and acceptance criteria.
2. Working prototype: Demonstrate a read and write operation in each application through the chosen connector.
3. Complete MVP: Deliver the agreed tools and cross-application workflow, with functional and performance testing.
4. Handover: Provide source code, deployment instructions, configuration examples, documentation and a walkthrough.
Acceptance will include verifying that changes save correctly, files reopen without corruption, the connector works as demonstrated, and agreed latency and concurrency targets are met.
Please include in your proposal
- Examples of MCP servers or Microsoft Office integrations you have built.
- Your proposed architecture and integration method for each application.
- How you would achieve low latency and support a future web application.
- Key limitations, dependencies and ongoing costs.
- Your estimated timeline, price and milestone breakdown.
- Your approach to source-code ownership, dependency licences and support after delivery.
Suggested skills: Model Context Protocol, API Integration, Microsoft Office, Microsoft Graph, Backend Development, OAuth, Python, TypeScript or C#/.NET.