Rise MCP Server

The Rise MCP server lets an AI assistant — Claude, ChatGPT, Gemini, or Microsoft 365 Copilot — answer questions about your Rise reporting data, build and save reports, and link you straight back into the Rise web app. You ask in plain language ("what's our headcount?", "average salary in Engineering", "save April birthdays as a report") and the assistant does the work using your Rise login and your permissions.

It's the same reporting surface that powers the Rise web chatbot, exposed over an open standard so the AI tools you already use can talk to it.

What is MCP?

The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external systems. An MCP server exposes a set of tools; an MCP client (your AI assistant) calls those tools on your behalf. Rise runs the server — you point your assistant at it once, sign in, and from then on the assistant can work with your Rise data inside any chat.

You don't write code to use it. If you're building a programmatic integration instead, use the REST API.

The server endpoint

MCP URL	https://mcp.risepeople.com/mcp
Transport	Streamable HTTP (remote — nothing to install)
Authentication	OAuth 2.0 — you sign in to Rise and approve access

This single URL is all most clients need. Pick your assistant under Connect your AI tool in the sidebar for step-by-step setup.

Prerequisites

• A Rise account with reporting access. The assistant can only see reports you can already open in Rise.
• An AI assistant that supports custom MCP connectors. See the per-client guides for the plan/edition each one requires.
• Org approval, where your AI tool requires it. Some assistants (notably Microsoft 365 Copilot and enterprise editions of ChatGPT) require an administrator to register or approve a connector before individual users can add it.

Availability. Public AI-assistant connectors are rolling out per Rise account. If sign-in succeeds but no reports appear — or your assistant can't reach the server — your account may not be enabled yet. Email developers@risepeople.com with your company name and the assistant you're connecting.

How authentication works

Every connection uses OAuth 2.0. The flow is the same regardless of which assistant you use:

1. You add the server URL to your assistant.
2. The assistant discovers Rise's authorization server automatically (via the RFC 9728 metadata Rise publishes at https://mcp.risepeople.com/.well-known/oauth-protected-resource).
3. A Rise sign-in page opens. You log in and approve the requested scopes.
4. The assistant receives a token and uses it on every call.

A few properties worth knowing:

• You only see what you can see. Your identity and organization are read from your signed-in token, never from anything the AI types. The assistant cannot reach another company's data or any report you couldn't already open in Rise.
• Read-only by default. Running and reading reports needs reports:read. Saving or editing a custom report needs reports:write, which you approve separately — if you don't grant it, the assistant simply can't write.
• Tokens are short-lived. Access tokens expire after about an hour; your assistant refreshes them transparently. You can revoke access at any time from your Rise account or by removing the connector in your assistant.

For the full OAuth details — grant types, scope reference, token lifetimes, and how to register an OAuth application if your assistant asks for a client ID — see Authentication.

Supported clients

Assistant	Guide	What you'll need
Claude (claude.ai & Claude Desktop)	Connect Claude	Pro, Max, Team, or Enterprise
ChatGPT	Connect ChatGPT	Developer mode (Plus/Pro) or an admin-published connector (Business/Enterprise/Edu)
Gemini	Connect Gemini	Gemini CLI, or Gemini Enterprise / Agentspace
Microsoft 365 Copilot	Connect Microsoft 365	Copilot Studio + an admin to publish the agent

New to the assistant side? Start with what you can ask for example prompts and the full list of things the assistant can do.

Data, privacy & security

• Your token, your permissions. Rise validates your token on every request and forwards it to the same gateway the Rise web app uses, so all the usual permission, audit, and rate-limit policies apply. There is no back door that bypasses your access rules.
• No identity by argument. The assistant can't pass an organization_id or employee_id to act as someone else — those are read from your token and any attempt to override them is rejected.
• Scoped consent. You approve exactly which scopes the assistant gets, and writing is always a separate, explicit grant.
• Your AI provider sees the results. Whatever the assistant retrieves from Rise becomes part of that chat, subject to your AI provider's data handling. Connect Rise only to assistants and accounts your organization trusts with HR and payroll data.

Limits

• The assistant follows the same rate limits as the rest of the Public API.
• A single non-aggregating query returns at most 100 rows for display — the assistant will tell you "here's the first N of M" and offer to summarize, narrow, or save the full report instead. Server-side totals, averages, and breakdowns aren't subject to that cap.

Support

• Setup or access problems: developers@risepeople.com
• Status: status.risepeople.com
• Security disclosures: security@risepeople.com