Jasper + your AI assistant: chat, time and leave from Claude

Jasper runs an MCP server, so an AI assistant that supports remote MCP servers can read and act on your Jasper workspace as you: post in chat, log time, request leave, work through ClickUp tasks and more.

Available All plans

Connect Claude Read the setup guide

What you can do

Ask your assistant to log yesterday's time against the right client, or start and stop your timer.
Check your leave balance, request leave, or approve a request you are allowed to approve.
Catch up on a channel, search messages and post a reply without leaving your editor.
Work through your ClickUp tasks: list them, comment, update them and create new ones.
Read your own mail, if you switch that on.

What syncs

Area	Access	Tools
Chat: conversations, messages, search, threads, pins, reactions	Read and write	11
Time tracking: timer, entries, summaries, clients, projects	Read and write	12
Leave: overview, request, cancel, approve, reject	Read and write	5
Calendar: calendars and events, create, update, delete, reply	Read and write	6
ClickUp tasks: your tasks, spaces, lists, comment, update, create	Read and write	7
Mail: shared inboxes, scheduled mail, and your own mail (read-only)	Read and write	11
People: you, members, who is online, status	Read and write	6
Notifications	Read and mark as read	3
Calls and recordings: lists only	Read	2
Jasper assistant and translation	Ask	2

Set up in 4 steps

Who can do this: Anyone in your workspace, for themselves. Your organisation needs API access turned on.

Copy the server address: https://heyjasper.ai/mcp.
Claude or Claude Desktop: open Customize, then Connectors, click Add, then Add custom connector, name it Jasper and paste the address. On Team and Enterprise plans an owner adds it first under Organization settings, then Connectors. Claude Code: run claude mcp add --transport http jasper https://heyjasper.ai/mcp.
Cursor: add {"mcpServers": {"jasper": {"url": "https://heyjasper.ai/mcp"}}} to ~/.cursor/mcp.json. Other assistants: add a remote MCP server with the same address.
When the browser opens, sign in to Jasper and approve the access your assistant asks for.

Permissions we ask for, and why

Your assistant asks for these scopes when you connect, and Jasper's approval screen lists them. Every tool calls Jasper's API as you, so it sees only what you can see, under the same permissions, IP allowlist and rate limits.

Permission	Why Jasper needs it
`mcp:use`	Lets the assistant use Jasper's MCP server.
`messenger:read`	Read chat, threads, pins, presence and status, call lists and shared inboxes, and translate text.
`messenger:write`	Post, reply, react, open direct messages, delete messages, set your status and work on shared-inbox threads.
`time-tracking:read`	Read your timer and time entries, clients and projects, leave, calendars and events, and ClickUp tasks.
`time-tracking:write`	Start and stop the timer, log and edit time, request and approve leave, change calendar events and change ClickUp tasks.
`organization:read`	List the members of your organisation.
`chat:write`	Ask the Jasper assistant a question.
`mail:read`	Read your own mailboxes. Refused until you switch on Allow my AI assistant to read my mail.

Your data

Each tool call goes through Jasper's own API with your sign-in, so it sees only what you can see.
Every successful change an assistant makes is recorded in your organisation's audit log as "AI tools (MCP)".
What your assistant does with the results is up to its provider, under your agreement with them.
You can revoke an assistant's access at any time under Personal settings, then OAuth Tokens. Switching off mail access signs out every app that had it.

Our privacy policy covers what we store, where, and for how long.

Limits and what is not synced

Your organisation needs API access on. New workspaces start with it off; it turns on when an owner or admin creates an organisation token under Personal settings, then API Tokens.
120 requests to the MCP server a minute per person, and each tool call also counts against your API rate limit. Personal mail tools are limited to 30 a minute and 1,000 a day.
Assistants that sign in through the browser get 63 tools. The two scheduled-mail tools need a personal token with the mail:token scope.
Browser sign-in works from claude.ai, claude.com, chatgpt.com, vscode.dev, Cursor and apps on your own computer. Other assistants can send a personal token instead.
Calendar and shared-inbox tools only help if your workspace already uses Jasper's calendar and shared inboxes.
There are no direct tools for code review, the wiki or uptime monitoring yet. The Jasper assistant tool can answer questions about reviews and the wiki.

Common questions

Which assistants work with Jasper?

Any assistant that supports remote MCP servers over Streamable HTTP. Jasper accepts browser sign-in from Claude, ChatGPT, Cursor and VS Code; other assistants can send a personal token.

Can the assistant see more than I can?

No. Each tool calls Jasper's API with your sign-in, so the same permissions apply.

Can it read my email?

Only if you switch on Allow my AI assistant to read my mail in Personal settings. Mail access is read-only, and switching it off signs out every app that had it.

Are changes logged?

Yes. Each successful change an assistant makes is recorded in your organisation's audit log as "AI tools (MCP)".

How do I disconnect an assistant?

Revoke it under Personal settings, then OAuth Tokens, or remove the connector in the assistant.