Skip to main content
Everything you do over MCP draws on the same subscription as the Surfer app. The plan, the credits, and the usage view are the ones you already have.

Plans that include MCP

MCP is included in the Pro, Peace of Mind, Enterprise, and AI Search Analytics plans. Some older plans and trials include it as well; the MCP tab in the app shows whether yours does. Actions that create or generate content count toward your plan limits. Reading data does not. If your organization’s plan stops including MCP, your connection stays, but requests for organization data fail with a permission error until the plan includes MCP again.

Tools that consume credits

The actions in this table consume credits. Reading data, replacing a document body, editing guidelines or settings, and deleting templates or voices do not. Enterprise and some older plans use AI Article credits. Surfer reserves one when generation starts and releases the Content Editor’s own credit. Other plans include AI Articles in the Content Editor. Reading, editing, and approving that article’s outline do not cost another credit. On plans with AI Article credits, if Surfer marks an article as failed, it releases the reserved credit. A retry reserves an available credit again; the released credit keeps its original expiry. Retrying an article that has not begun processing reuses its existing reservation.
A timeout does not mean the work failed or its credit was released. Check the job’s status before starting another run. A second Auto-Optimize run on the same editor charges again and cancels the first run, which is not refunded.
Creating a Content Editor accepts a retry key. With it, a retried create returns the original editor instead of charging for a second one. Your assistant does not always send one, so ask for retry keys when you create in bulk. Deleting a Content Editor in the app does not refund its credit, and the deleted editor still counts toward fair usage. No MCP tool deletes one (changes and deletions). Skills, the built-in playbooks that run a whole Surfer workflow from one request, call these same tools. A playbook that creates a Content Editor or generates an article follows the same credit rules as those actions above.
  • Every playbook can reuse an existing Content Editor. A rerun, or an article written from an outline, brief, or recommendation that an earlier playbook produced, spends no new Content Editor credit.
  • The article playbook creates a Content Editor only when none applies. It tells your assistant to send a retry key, so a retry after a timeout returns the editor already created and charges nothing extra.

When credits run out

When you run out of one of these credits, the tool call fails with a quota error. Your assistant cannot create more of that kind until the quota resets or your plan changes.
  • See what you have used on the Usage page.
  • To get more, an organization member with billing access opens Your subscription. It shows the options for your plan: upgrade or change the plan, contact sales, or request an upgrade from support.
  • Documents allowance per plan: the pricing page.
  • Auto-Optimize allowance: your plan’s limits; plans on fair usage follow the Fair Usage Policy.
No MCP tool call reports remaining credits. Before a run of tool calls that charge, you can check the Usage page in the app.
Creating a workspace, content template, or custom voice also fails with a quota error when you reach your plan’s allowance. These are limits on how many you can have, rather than credits spent per action. Remove unused templates or voices, or check your plan allowance before creating more.

Rate limit

Requests are rate limited per organization and per tool, and everyone connected to the organization shares each limit. When a tool hits its limit, its calls fail with a rate-limit error that says how long to wait, and other tools keep working; your assistant should wait and retry. Troubleshooting quotes the error. Search Console queries also use Google’s own quota for the property, which Surfer’s background imports share. Paging through a large property can delay Search Console refreshes in the app.

Timeouts and long-running tools

Some actions keep running after your client stops waiting for a response. Your assistant can check their progress. See the capabilities overview for the work Surfer can perform.
A call that returns early may already have started work and reserved or spent a credit. Ask your assistant to check the job’s state instead of starting it again.
Before retrying an unclear result:
  • Reading data: retrying does not spend a credit.
  • Creating a Content Editor: retry with the same retry key, if the first call used one. If you are not sure it did, have your assistant list the Content Editors and look for the keyword before creating it again.
  • Generating an article: check its status first. Surfer refuses another generation while the article is in progress or already complete. For failed articles, the credit rules above explain how released credits are reused.
  • Running Auto-Optimize: check the editor for an existing job first. A second run charges again and cancels the job already in progress.

Input limits

Surfer enforces limits on text length, list sizes, and report ranges. Your assistant receives the current requirements from the connected tools. If a request exceeds a limit, have it adjust the input or split the work into smaller requests. Check the credit rules before splitting an action that charges.

Limits your client adds

Surfer sets no per-client limit. Your client may cap the number of tools it loads or the time it waits for a call. The caps below are the client’s own, documented on the linked vendor pages.