AI assistant connector (MCP)

The connector lets an AI assistant answer questions from your Presify data over the Model Context Protocol (MCP). It is read-only: an assistant can never change settings, enroll people, or write anything. Answers are limited to what the connecting person can already see in Presify, plan-gated features stay plan-gated, and every connection can be revoked at any time under Settings, then Connections.

Two ways to connect

• Sign in from the assistant (most people; no token)

  Claude, ChatGPT, Microsoft Copilot Studio, Perplexity, and most other MCP clients connect with the server URL alone. Add Presify as a custom connector there, and the assistant walks you through a Microsoft sign-in and a Presify approval page. Nothing to copy besides the URL.

• Personal access token (developer tools)

  Claude Code, scripts, and the Anthropic API authenticate with a bearer token instead. Create one under Settings, then Connections; it is shown once, acts as you, and expires after a year.

The server URL for both is shown on Settings, then Connections. On the production app it is:

https://app.presify.io/api/mcp

Set it up per assistant

• Claude (web, desktop, mobile)

  Settings, then Connectors, then "Add custom connector". Name it Presify, paste the server URL, select Add, then sign in and approve. On Team and Enterprise plans an org owner may need to enable it for members first.

• Claude Code

  Create a personal access token, then run: claude mcp add --transport http presify https://app.presify.io/api/mcp --header "Authorization: Bearer YOUR_TOKEN"

• ChatGPT

  Enable developer mode under Settings, then Apps, then Advanced settings. Add a custom connector with the server URL and OAuth, then approve. On Business, Enterprise, and Edu plans a workspace admin enables custom connectors first.

• Microsoft Copilot Studio

  In your agent: Tools, then Add a tool, then New tool, then Model Context Protocol. Use the server URL with OAuth 2.0 and dynamic discovery. Your Power Platform data policies apply.

• Other MCP clients (Perplexity, Mistral, Cursor, VS Code, and more)

  Anywhere a custom MCP connector is supported, paste the server URL and complete the sign-in, or use a personal access token where only headers are supported.

What your assistant can answer

• Workspace and health: plan and seat usage, Microsoft 365 connection health, recent notices.
• People and presence: the monitored roster, who is online now, presence summaries over any range, per-person statistics, a person’s day timeline (ordered presence segments with local times), side-by-side comparisons.
• Coverage and patterns: the team coverage grid and flagged presence patterns, on plans that include them.
• Reports and audit: generated reports with short-lived download links, report schedules, and the audit trail for owners.

Presence is polling-sampled activity data. Answers are evidence for a conversation, not a verdict about a person.

Security and revocation

• Connecting always shows who is connecting what, to which workspace, before anything flows.
• Tokens are stored only as hashes and expire on their own; revoking a connection (or removing a member) cuts access immediately.
• Connection and revocation events land in your audit log. Owners and admins can see and revoke every connection in the workspace.
• Answers go to the AI provider you connected, under that provider’s terms. Connect only providers your organization has approved.

Troubleshooting

• Authorization errors after it worked before: the connection was revoked or expired. Reconnect from the assistant, or create a fresh token.
• A temporarily-unavailable message: the connector is paused for maintenance. Connections are kept; service resumes without reconnecting.
• Missing tools or shorter answers: your role or plan does not include them. The tool list adapts per person and per plan.

For developers and agents

Presify is a standard MCP server behind OAuth 2.0 (authorization code with PKCE, dynamic client registration). Everything a client needs is discoverable:

MCP endpoint

POST only. Stateless Streamable HTTP with JSON responses; Bearer token from the OAuth flow or a personal access token. initialize, ping, and the public documentation resources (resources/list, resources/read) need no token; every tool is read-only. https://app.presify.io/api/mcp

MCP server card

Pre-connection discovery: server URL, transport, protocol revision, OAuth details, and the full read-only tool catalog with input schemas. https://app.presify.io/.well-known/mcp/server-card.json

OAuth 2.0 authorization server metadata (RFC 8414)

Endpoints, grant types (authorization_code, refresh_token), PKCE S256, and open dynamic client registration (RFC 7591). https://app.presify.io/.well-known/oauth-authorization-server

Protected resource metadata (RFC 9728)

Names the resource, its authorization server, and the single read-only scope. The 401 challenge from the endpoint points here. https://app.presify.io/.well-known/oauth-protected-resource/api/mcp

OpenAPI 3.1 description

The whole public machine surface, with the current MCP tool catalog under x-mcp. https://presify.io/openapi.json

API versioning and deprecation policy

Permanent paths, protocol-revision negotiation, and Deprecation plus Sunset headers at least 90 days before any removal. https://presify.io/docs/api-versioning

Site index for AI assistants (llms.txt)

What Presify is, when to use it, and how an agent calls it. https://presify.io/llms.txt