Resources · Claude connector

Claude Jasper connectorWhat Claude can do in your Jasper account.

The Claude Jasper connector exposes 7 tools. 5 of them read your brand context, 2 produce content through Jasper, and 0 are left undocumented. Below: what Claude pulls from Jasper, what it generates, what Jasper requires first, and where sources differ.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes once Claude can reach your Jasper brand kit

Marketing teams spend a lot of effort keeping every draft on-brand. With this connector, Claude reads the brand voices, audiences, style rules and knowledge your team already set up in Jasper, and it can ask Jasper itself to produce copy or run one of its marketing agents. You describe the result you want; Claude decides which of these tools to call.

Draft in the right voice from the first try. A content lead wants a product launch post: Claude checks get-jasper-brand-voices and get-jasper-audiences, then calls generate-content so Jasper writes with the voice, audience and style rules you configured.

Ground claims in your own material. Before writing a sales one-pager, Claude queries search-knowledge-base for relevant documents about the release, instead of relying on what it assumes about your product.

Hand a task to a specialised agent. get-jasper-agents lists the marketing agents available to your workspace, and run-jasper-agent sends one of them to work on a task you describe.

What it will not do: the reading tools only look at your brand context, and the sheet has no tool to edit a voice, an audience or a style guide. Jasper's guide does not say whether generated content is saved in your workspace. And nothing starts by itself on a schedule or an event: that kind of background job is the domain of an automation tool, a separate trade covered by the Integrations hub.

Vocabulary

Five words before you connect

The vocabulary Claude uses around this connector, quickly.

Connector
The link you set up once between Claude and an account you already own, so Claude can work in that account while it answers.
Tool
One named action a connector lets Claude take. Claude chooses the tools it needs by itself, and the directory lists each one by name.
Authorization
The login screen of the service itself, where you give Claude the access it will use. Granted once per person, and revocable.
Approval
The confirmation Claude waits for before doing something that changes your account, shown in the conversation when it matters.
MCP
The shared standard connectors are built on, which is what lets an assistant such as Claude talk to an outside service like Jasper.
Connect

Connect Jasper to Claude in three steps

  1. 01

    Find Jasper in Claude

    Open Claude's settings, go to Customize and then Connectors, and look for Jasper in the list. On a Team or Enterprise workspace, an Owner or Primary Owner switches the connector on before each member can sign in.

  2. 02

    Start the connection

    Click Connect on its row, then sign in to Jasper in the consent window Jasper opens. If the link stops working later, use Disconnect and connect again from the same list.

  3. 03

    Review the authorization screen

    Read the authorization screen before you accept. It is Jasper's screen, not Claude's, and it sets which brand items the access covers. You can withdraw that access later from your Jasper account.

Tools

The 7 tools, split by what they do

Jasper gives Claude 7 tools: 5 that read your account, 2 that change something in it.

Two groups: what Claude reads from Jasper and what it asks Jasper to produce. Tool names stay exactly as Claude displays them.

  • 5 read
  • 2 write

What Claude reads (5)

5 tools

Five tools that look at your brand context and leave it untouched.

get-jasper-agents

Returns the Jasper agents your workspace can use for marketing tasks, so Claude knows which specialised helpers exist before picking one.

When it helps
you want to know which agents your team has made available before you hand one a task.

Sourcedevelopers.jasper.ai · September 17, 2026 ↗

get-jasper-audiences

Fetches the target audiences defined in your Jasper workspace, so Claude can pitch the same message differently to each group you already described in Jasper, with its own concerns.

When it helps
one summer sale, two posts: one for students, one for business buyers.

Sourcedevelopers.jasper.ai · September 17, 2026 ↗

get-jasper-brand-voices

Reads the brand voices available to your workspace. Claude uses them to match tone and wording instead of improvising a style of its own.

When it helps
a new hire drafts a LinkedIn announcement and it must sound like the rest of your channel.

Sourcedevelopers.jasper.ai · September 17, 2026 ↗

get-jasper-style-guides

Retrieves the style guide configuration of your workspace: the house rules Jasper applies to its output for your team.

When it helps
you want Claude to follow your team's house rules before it drafts anything.
Watch out
it reads the rules; the sheet offers no tool to edit them.

Sourcedevelopers.jasper.ai · September 17, 2026 ↗

search-knowledge-base

Searches the Jasper knowledge base for documents and information relevant to your request, so Claude drafts from your own material rather than from assumptions.

When it helps
you ask for a sales one-pager on a new release and the specs sit in documents your team uploaded.

Sourcedevelopers.jasper.ai · September 17, 2026 ↗

What Claude produces (2)

2 tools

Two tools that make Jasper produce work. No source details their confirmation, so the general rule below applies.

generate-content

Approval: see the rule

Asks Jasper to produce copy using your configured voices, audiences, style rules and knowledge, plus any context Claude passes along. Workspace defaults fill in whatever Claude leaves unspecified.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule below applies.
When it helps
an email campaign about a quarterly update, in your usual voice.
Watch out
Jasper's guide does not say whether the output is saved in your workspace.

Sourcedevelopers.jasper.ai · September 17, 2026 ↗

run-jasper-agent

Approval: see the rule

Starts one of your Jasper agents on a marketing task Claude describes, and brings its result back into the chat. Like content generation, it falls back on workspace defaults for voice, audience and style guide.

What Claude asks for
nothing specific is documented; rely on the general rule in the approvals section.
When it helps
a marketing task you would rather hand to one of the agents your team set up in Jasper.

Sourcedevelopers.jasper.ai · September 17, 2026 ↗

Approvals

What Claude checks with you first

By default, Claude stops and asks before each action it takes on an account on someone's behalf, with the prompt shown in the conversation.

On Team and Enterprise workspaces, owners decide whether a member may let some actions through without being asked every time. They can also restrict what a connector does for the whole organization, for instance keeping reading and closing writing, and nobody lifts that from a personal account. Claude also works with the rights of the person who connected: Jasper's consent form covers only the brand items that person can already reach, nothing beyond.

Plans

Which plans include it

None of the 819 sheets in the official directory shows plan availability, so the answer for Jasper is published nowhere by Anthropic.

Anthropic publishes the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and on Team and Enterprise an Owner or Primary Owner enables them first. Jasper's own guide states something narrower; the limits section below puts both side by side. For the live state on your account, open the Jasper sheet in the official directory.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you, so nothing is produced on a schedule or when a campaign starts.

This connector is documented by its publisher only: no page of Claude's help center covers it. The tool list is an observed floor, not a promise, since an administrator can open actions that no public sheet shows. The partner badge is not a security audit, and Anthropic says on every sheet that it does not choose the tools a publisher exposes nor guarantee how they behave. The Claude activecampaign connector page covers another marketing account seen through the same lens.

Two official sources disagree

Which Claude plans can use the Jasper connector?

What this page followsNeither side is outdated. Anthropic's rule covers every connector, while Jasper's line targets this one but comes from the publisher, not from Anthropic. Check the directory sheet on your own account before relying on either.

Need help

Need help connecting Jasper to Claude?

A person reads every message.

FAQ

Questions about the Claude Jasper connector

01What can Claude do with the Jasper connector?
Claude can read the brand context your team keeps in Jasper and ask Jasper to produce on-brand work. Five tools look up brand voices, audiences, style guides, available agents and your knowledge base. Two tools act: one generates content with your configured context, the other runs a Jasper agent on a marketing task. Jasper's guide adds that Claude detects when to use these tools from your request, so you describe the result rather than naming a tool.
02Can Claude change my brand voices or style guides in Jasper?
Not with the tools on the directory sheet. The five reading tools only look at voices, audiences, style guides, agents and knowledge, and Jasper itself describes that access as read-only. The two tools that act produce content or run an agent; the guide does not say whether their output is saved in your workspace. As with any connector, a tool list is an observed floor, since an administrator can open actions no public sheet shows.
03Does Claude ask before generating content through Jasper?
By default, Claude asks for confirmation before each action it takes on an account for someone. No source describes a confirmation specific to generate-content or run-jasper-agent, so that default rule is what covers them. On Team and Enterprise workspaces, owners decide whether members may let some actions run without a prompt every time, and they can restrict the connector for the whole organization, for example to reading only. Members cannot undo that setting.
04Which Claude plans can use the Jasper connector?
No official source from Anthropic publishes plan availability connector by connector, and none of the directory's sheets shows it. Anthropic's general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner enabling them first on Team and Enterprise. Jasper's own guide states a narrower list, quoted in the limits section of this page. The directory sheet on your account is what to check.
05Does Claude see everything in our Jasper workspace?
No. When you connect, Jasper's consent form lets you authorize access only to the Jasper IQ items you already have access to, so Claude works within your own rights. A colleague with access to other voices or audiences will get different results. On top of that, an owner of a Team or Enterprise workspace can narrow what the connector does for the whole organization, and members cannot lift that restriction themselves.
06Why does Claude not use my knowledge documents by default?
Because Jasper applies workspace defaults only to style guide, brand voice and audience. When Claude calls generate-content or run-jasper-agent without naming those, Jasper falls back on your defaults for each one separately. Knowledge and product context have no workspace default, so they are not added automatically. Ask Claude to search your knowledge base first, or name the documents you want used, and the output will reflect them. Nothing else needs to change.
07Should I use Claude or an automation tool with Jasper?
They cover different needs, so pick by the job. Claude works inside a conversation: you describe a piece of content, it pulls your brand context and asks Jasper to produce it, and nothing happens once you stop. It does not generate posts on a schedule or react to an event. If you need recurring content produced in the background, that is an automation tool's work. For on-demand, on-brand drafting, the connector fits.