MCPs for real work.

This page tracks the MCP servers I've been building around document generation, execution, Microsoft integrations, and live artifact workflows. The common thread is simple: make models useful inside systems people actually need.

Document generation

mcp-ms-office-docs

Generates DOCX, PPTX, and XLSX files from templates so document creation can be automated without losing structure or presentation quality.

•Built for template-based Microsoft Office document generation.
•Supports Word, PowerPoint, and Excel outputs.
•Useful when an agent needs to produce polished business artifacts instead of plain text.

GitHub link coming soon

Execution + visualization

Code Interpreter MCP

Spins up code-powered analysis and visualizations so the system can move from reasoning to charts, computed outputs, and runnable artifacts.

•Designed for generated visualizations and execution-heavy tasks.
•Useful when a workflow needs computation, transformation, or plotted output.
•Bridges conversational requests with concrete generated artifacts.

GitHub link coming soon

Identity + integration

Microsoft Authentication Server

Handles Microsoft Graph authentication for MCP workflows, including OAuth initiation, callback handling, token refresh, logout, and persistent token storage.

•Supports Microsoft Graph scopes across mail, calendar, contacts, files, tasks, chat, teams, and sites.
•Persists tokens in MongoDB and proactively refreshes them before expiration.
•Provides endpoints for auth initiation, status checks, token retrieval, refresh, and logout.

GitHub link coming soon

Interactive document workflows

Live URL / Artifact MCP

Generates a URL that can be displayed inside an artifact, then updates that URL in real time as you chat with the MCP server.

•Built so users can chat with a document-backed workflow and see changes reflected live.
•Designed to work with DOCX and PowerPoint files.
•Turns documents into interactive surfaces instead of static exports.

GitHub link coming soon

Why these matter

I'm interested in MCPs that close the loop between language models and actual outputs: generating Office files from templates, authenticating against Microsoft services, running code for visualizations, and turning documents into live, chat-driven experiences.

Design principles

•Practical over theoretical: each server exists to unlock a real workflow.
•Artifacts matter: the output is often a document, visualization, or live surface, not just text in chat.
•Integration is the product: auth, execution, generation, and interactivity all need to work together.

What's emerging

The larger pattern here is interactive artifact infrastructure. Instead of treating chat as the final destination, these MCPs let conversation drive documents, presentations, spreadsheets, visualizations, and live URL-based surfaces that can be rendered back to the user in real time.