Vitally MCP Server

A Model Context Protocol server that exposes the Vitally customer success platform’s REST API to MCP-compatible clients such as Claude Desktop, Claude Code, VS Code, and Cursor.

Built in C# on .NET 10 and the official ModelContextProtocol SDK, hosted as a remote HTTP MCP server secured with Microsoft Entra (OAuth 2.1 / RFC 9728). Users connect by URL — no install, no executable, no per-user secrets to distribute.

Features

• Full CRUD coverage of 16 Vitally resource types via 93 tools: accounts, organisations, users, conversations, messages, notes, projects, project templates, project categories, tasks, NPS responses, admins, custom objects (and instances), meetings (with participants and transcripts), custom traits, and custom surveys.
• Permission-aware tools — every tool is annotated ReadOnly / Destructive / Idempotent / OpenWorld so MCP clients can enable or disable categories of operation in bulk and reason about retry safety. Beyond those advisory hints, tools/list is filtered per caller: a client is shown only the tools the signed-in user’s permission tier permits.
• EU and US data centres — defaults to EU (rest.vitally-eu.io); set Vitally:Region=US to point at {subdomain}.rest.vitally.io.
• Rate-limit-aware HTTP pipeline — auto-retries on 429 Too Many Requests honouring Retry-After and X-RateLimit-Reset, and logs a warning when remaining requests drop below threshold.
• Client-side field & trait filtering — responses are trimmed before they reach the LLM, each resource type with sensible defaults that exclude heavy fields (rich text, transcripts, full traits objects).
• Streamable HTTP transport (MCP 2026-07-28) in stateless mode — easy to scale horizontally, no sticky sessions required.
• OAuth 2.1 protection against Microsoft Entra, directly on both deployed targets. /.well-known/oauth-protected-resource exposes the metadata document so clients discover the authorisation server automatically. The Vitally API key is fetched on demand from Azure Key Vault via the server’s managed identity.

Using the server (FISCAL users)

Point your MCP client at:

https://vitally.fiscaltec.com/mcp

The first time you connect, your client will redirect you to a Microsoft sign-in to authenticate. Once authenticated, the server proxies your tool calls to Vitally using a service-account API key it fetches from Azure Key Vault.

Access & groups: authentication alone grants nothing — you must be in a sg-vitally-* Entra group for your access tier. See ACCESS.md for connecting, the group setup, and how access is granted or revoked.

Claude Desktop