Connect Claude, Cursor or another AI tool to your PressaGen pages with MCP

Create an API token in your dashboard, then add https://pressagen.com/api/mcp to an AI tool that supports MCP, and it can read your pages. For now AI tools can only read; tools for editing and publishing will come later.

What an AI tool can read

Once connected, your AI tool has six tools, all read-only:

• list_pages: lists your pages, with each one’s address, whether it is published and whether it has unpublished changes.
• get_page: reads one page’s cards and text, including changes you have not published yet.
• list_templates: lists the templates, by audience, purpose or language if you like.
• get_template: reads one template’s cards and text.
• get_schema: describes each card type and its fields.
• get_account: shows your plan, page count and image room, and what this token may do and when it expires.

Ask the AI to check a page for typos or suggest a template, then make the changes yourself in the editor.

Connect in three steps

1. Create a token: near the bottom of your dashboard, open API and MCP, fill in Token name, choose Create token, then Copy. It is shown only this once; see API tokens.
2. Add the address and your token to your AI tool, as the next section shows.
3. Try a tool: ask the AI to list your PressaGen pages. It calls list_pages, and the pages it names should match your dashboard.

Set up your AI tool

Claude Code

Run this in your terminal:

claude mcp add --transport http pressagen https://pressagen.com/api/mcp \
  --header "Authorization: Bearer <your token>"

Add --scope user to use it in every project. Do not use --scope project: it writes the token into the project’s .mcp.json, which is shared through version control. Type /mcp in Claude Code to check the connection.

Claude Desktop

In Claude, go to Customize > Connectors and choose Add custom connector. Enter https://pressagen.com/api/mcp as the URL, choose No sign-in under Authentication, and under Request headers pick authorization with the value Bearer <your token>, with a space after Bearer.

• Request headers are in beta in Claude and open to a limited set of organizations. If you do not see that section, use Claude Code or Cursor for now.
• Headers cannot be changed once the connector is added, so to switch tokens, remove the connector and add it again.
• On a Claude Team or Enterprise plan, an Owner adds the connector for the whole organization, so every member would read your account. Do not set it up that way.

Cursor

Add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "pressagen": {
      "url": "https://pressagen.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <your token>"
      }
    }
  }
}

You can write the value as Bearer ${env:PRESSAGEN_TOKEN} instead, so Cursor reads the token from an environment variable and the file holds none. Avoid the project’s own .cursor/mcp.json, which travels with the project.

What it can and cannot do today

AI tools cannot yet:

• Create, edit, publish or delete pages; tools for editing and publishing will come later.
• Read other people’s pages, or your pages’ newsletter subscribers.
• Connect from an MCP client running inside a web page; use Claude Code, Claude Desktop or Cursor.

Each account can make up to 120 requests a minute; past that, wait for the next minute. The address takes Streamable HTTP requests by POST only, in MCP 2026-07-28, or in 2025-11-25, 2025-06-18 and 2025-03-26 after initialize.

Keep your token safe

• A token is your account: anyone who has it can do everything it allows.
• Keep it where only you can read it, and never paste it into a chat or a document.
• Give each tool its own token. When you stop using one, choose Revoke under API and MCP, and tools using it stop working at once.

Questions

Will the AI tool change my pages?

No. All six tools only read; none creates, changes or publishes anything. When editing and publishing tools arrive, only a token with Create and edit pages, and upload images or Publish pages ticked will be able to use them.

Why does the AI see something different from my public page?

When a page has unpublished changes, get_page reads the version in your editor. Visitors keep seeing what you last published until you publish again from the editor.

Related: API tokens: how to create, scope and revoke them