Jasper

Read a Jasper workspace's brand voices, audiences, style guides and knowledge base, and generate copy via Jasper's AI.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Jasper connector does

The Jasper MCP server connects a Jasper workspace — an enterprise marketing-copy platform — to Claude, ChatGPT and any MCP-compatible agent. Its seven tools read your brand voices, audiences, style guides and knowledge base, then generate copy through Jasper's own AI engine. Sign-in is OAuth 2.0 with one generic scope.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Jasper tools (7)

  • generate-content
  • get-jasper-agents
  • get-jasper-audiences
  • get-jasper-brand-voices
  • get-jasper-style-guides
  • run-jasper-agent
  • search-knowledge-base

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The single OAuth scope is a wildcard. Jasper's RFC 9728 descriptor at https://mcp.jasper.ai/.well-known/oauth-protected-resource declares exactly one entry in scopes_supported: mcp. It names no object and no verb, so it cannot exclude anything. Granting it grants whatever the server implements now and whatever Jasper registers later — including, were the update and delete operations its REST API already offers ever to be added, those. The read-only boundary described on this page is enforced by Jasper's choice of tools,
  • No cost visibility, and no published rate. Two tools spend credits and none can read the workspace's balance, even though Jasper's REST API exposes a usage endpoint. The per-action rate card is the only path Jasper disallows in its robots.txt, so the cost of a call cannot be looked up before you run one. Do not blanket auto-approve generate-content or run-jasper-agent.
  • Publishing exists in Jasper, just not here. Jasper's GEO Agent can publish to a connected Webflow site from inside Jasper's own application, behind an explicit approval step. Whether invoking that agent through run-jasper-agent can reach the same path is unresolved — we did not test it, since triggering a publish is precisely the irreversible action this research does not perform.
  • The read-only annotations understate what a call does. All seven tools carry readOnlyHint: true and no destructiveHint: true, including the two that generate. A client treating that flag as "safe to auto-run" will auto-run billable calls.
  • openWorldHint: false on a tool with a web-search parameter. run-jasper-agent accepts WEB_SEARCH in its tools array while declaring it does not interact with the open world. The fetching happens inside Jasper, but the annotation does not convey that.
  • Business plan required. Jasper restricts API access — and therefore the MCP server — to its Business tier, so this connector is unavailable on lower plans regardless of Claude tier.
  • Nothing in the tool surface publishes. If you wanted an agent that drafts and posts, this is only the first half. The connector produces copy; distribution is manual, or belongs to Jasper's in-app Webflow integration, or to a separate automation product such as Zapier.
  • Model provenance is unavailable and unselectable. Jasper routes generation across model providers with documented fallbacks, its generation endpoints take no model parameter, and their responses return no model field.
  • The deployed remote server was not directly read. We read Jasper's published npm package, whose manifest builds a remote server from the same registration code but ships only the local build. The endpoint requires authentication, so no live tools/list was performed and no tool schema was read from the wire. Directory, documentation and source agree on all seven names.
  • No prompts or resources are claimed for the remote server. The npm package registers three MCP *resources* — jasper://brandvoices, jasper://audiences and jasper://styles — alongside the seven tools, all GET-only reads of the same data. Whether the hosted server declares a resources capability could not be checked without authenticating, so treat the resource surface as unverified for the remote endpoint.
  • The no-training commitment is narrower than it first reads. Jasper's trust page says company data and outputs are "never used to train third-party LLMs" — a claim scoped to third parties, made on a marketing page rather than in the privacy policy, which does not discuss knowledge bases or training at all.
  • Rate limits are per workspace, not per user. Jasper's documented defaults are 105 requests per minute on generation and knowledge-search routes, and 200 per minute on the listing routes, with style guides lower at 60 per minute. One busy agent consumes the whole workspace's budget.

Frequently asked questions

Can the Jasper connector publish content anywhere?

No. All seven tools return generated text to the agent and stop there. Jasper's source registers four GET calls and three POST calls, and every POST is a generation or search endpoint. Nothing writes to a CMS, a social account, a campaign or a scheduler, and no tool carries a publish parameter. Publishing stays a copy-paste step you perform yourself.

Can the connector change my Jasper brand voice or style guide?

No, and this is the important one for a marketing team. The three brand tools are plain GET requests against the voices, audiences and styles endpoints. Jasper's REST API does offer update and delete operations for voices and knowledge items, but the connector registers none of them, so a session cannot alter what future generations inherit.

Does each Jasper generation call cost credits?

Yes. Jasper's help centre states that API and MCP usage is charged on the credit system, and credits are consumed per action. The per-action rate is not on the open web: the credits rate card is the single path disallowed in Jasper's robots.txt. No connector tool reads usage either, so an agent can spend with nothing able to check the balance first.

Which AI model actually writes the content Jasper returns?

Jasper does not commit to one. Its documentation states the AI Engine configures a priority-order of fallbacks per endpoint and per use case to route around third-party model provider downtime. So the model behind generate-content and run-jasper-agent can change between calls, and the connector surfaces no field naming which model produced a given output.

Why is every Jasper tool annotated read-only when two of them generate content?

Because Jasper applies the annotation by workspace effect, not by HTTP method. All seven tools declare readOnlyHint true and none declares destructiveHint true, yet three issue POST requests. The label is defensible in that nothing is stored or altered, but it hides that two of those calls spend metered generation quota.

What can the Jasper connector read from my workspace?

Your entire brand knowledge layer. The tools return every brand voice with its full text, every audience with its description, every style guide including custom instructions and term substitutions, and semantic search across your uploaded knowledge documents with matching text chunks returned inline. That is proprietary company material entering the agent's context.

What OAuth permissions does the Jasper MCP server request?

One scope named mcp, which grants everything the server implements. Jasper's own RFC 9728 descriptor declares scopes_supported as that single value. It names no object and no verb, so consent cannot separate reading a brand voice from spending generation quota, and it would cover any tool Jasper adds later.

What do I need before connecting Jasper to Claude?

A Jasper Business plan and a paid Claude plan. Jasper states that API access is only available to customers on the Business plan, and that the Claude side needs a Pro, Max, Team or Enterprise account. Your network must also reach both mcp.jasper.ai and api.jasper.ai. Generating an API key additionally requires an Admin or Developer role.

Sources

More Sales & CRM connectors

  • Abency

    Run a marketing agency's social, SEO, ads, WordPress and email from an AI agent.

  • Actively

    Read per-account sales intelligence — agent memory, decisions, signals — from an AI agent.

  • Adobe Journey Optimizer

    Inspect campaigns, journeys and channel configurations in Adobe Journey Optimizer from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Jasper to work.

Connect Jasper once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.