Jasper
Connect Jasper to write on-brand content, run marketing agents and templates, edit images, and track how AI answers describe your brand.
You paste one value into PopMCP: a Jasper API key, from the API Tokens page in your workspace's settings.
Paid plan required before this connector works
No one reviews you, but Jasper only offers its API on the Business plan, and API access has to be on for your workspace.
- Typical wait
- None if your workspace already has API access. Otherwise it depends on Jasper's sales team, because the Business plan starts with a conversation with them.
- Cost
- Jasper quotes the Business plan individually, from jasper.ai/pricing. Agent runs and GEO runs can use credits on top, which sit alongside seat pricing. PopMCP adds nothing to this.
- Blocked until approved
- Everything. Without API access there are no Developer tools in Jasper's settings, so there is no key to paste.
- Works meanwhile
- Read Jasper's API reference, and connect your other tools in PopMCP. There is no sandbox or trial key to try first.
Where to apply: If you are on Business, ask a workspace Admin or Developer to open Settings, then Developer tools, then API Tokens at app.jasper.ai/settings/dev-tools/tokens. If it is missing, ask your Jasper account team to turn on API access. If you are not on Business, request a demo at jasper.ai/api.
- Only an Admin or Developer can make a key. Other people in the workspace do not see the page.
- Jasper's image tools need the Image API, which Jasper describes as an API subscription on the Business plan.
- Products need Product IQ on the workspace. GEO regions and one-off runs need their own entitlements. Without them those calls answer 403 while everything else works.
- Generating counts as a write in PopMCP, so a new read-only connection cannot generate until an owner or admin allows write actions.
- Setup time
- 2 min
- Auth
- API credentials
- API base URL
- https://api.jasper.ai/v1
- Rate limits
- Jasper limits each workspace per minute: 105 requests for commands, templates, Agent runs and Knowledge search, 200 for most reads and for Knowledge and voice writes, 60 for style guides and 30 for each image endpoint. Over the limit it answers 429. Your Customer Success Manager can raise them.
Before you begin
- A Jasper workspace on the Business plan with API access. Jasper's API is not available on other plans
- The Admin or Developer role in that workspace, or someone who has it, because only they can make a key
- Credits on your Jasper plan if you will run Agents or GEO analyses
- The Image API on your plan if you want the image editing tools, and Product IQ if you want the product tools
Get your credentials
Open API Tokens in Jasper
Sign in to Jasper and go to Settings, then Developer tools, then API Tokens. The link goes straight there. If you cannot see Developer tools, your role is not Admin or Developer, or your workspace does not have API access: ask a workspace admin, or your Jasper account team.
Make a token and copy it
Generate a new token and name it something you will recognise, like PopMCP. Copy it straight away. Jasper's tokens have no permission options: a token can do everything in the workspace, so treat it like a password.
API Tokens
Tokens that let other tools use this workspace through Jasper's API.
This view is a simplified sketch: the labels on your page may differ slightly. Each token belongs to this workspace.
Paste the key into PopMCP
In PopMCP, paste the token into API key and connect. PopMCP checks it by reading your brand voices from Jasper. New connections start read-only, so your AI can read your brand context, documents and GEO results and search Knowledge, but cannot generate anything until an owner or admin allows write actions.
Connect in PopMCP
Open your workspace, choose Jasper in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| API keysecret | In Jasper open Settings, then Developer tools, then API Tokens, and make a token. Only an Admin or Developer can do this. Stored encrypted and used only on our servers.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Jasper immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP marks the Jasper connection Verified and labels it with the email domain of your workspace, like Jasper workspace (acme.com), since Jasper's API does not report a workspace name. Asking the AI to show your brand context returns your voices, audiences and style guides.
Troubleshooting
"Jasper did not accept this API key..."
Why: The key was copied incompletely, or it has been deleted.
Fix: Open API Tokens in Jasper, make a new token and paste only the token.
"Jasper knows this key but will not let it use the API..."
Why: The workspace does not have API access. Jasper offers the API on the Business plan.
Fix: Ask your Jasper account team to turn on API access, then try again.
"That is an OAuth access token..."
Why: An access token from a Jasper OAuth client was pasted. Those expire within a day.
Fix: Make a token on the API Tokens page and paste that instead.
The AI says it cannot generate content
Why: The connection is read-only, which is how every new connection starts.
Fix: An owner or admin turns on write actions on the Jasper connector page in PopMCP.
Image or product tools answer 403
Why: The workspace does not have that feature. Images need the Image API, and products need Product IQ.
Fix: Ask your Jasper account team to add it. Everything else keeps working in the meantime.
An Agent run stops with a message not to repeat it
Why: The task took longer than a tool call can wait, and it may already have used credits.
Fix: Ask the AI to use run_agent_streaming, which keeps what was written so far, or give it a smaller job.
Tools fail with 429
Why: Jasper limits each workspace per minute: 105 for generation and Knowledge search, 200 for most reads, 60 for style guides, 30 for each image tool.
Fix: Wait a minute and try again. Your Jasper Customer Success Manager can raise the limits.