MCP server

Connect your workflows and agents to AymarTech MCP

The client you already run can change a cover, fix an article, or check indexing. AymarTech carries out the action your token allows.

ConnectHow to connect

AymarTech MCP

You

Change the cover photo of the article we published today. Make it a bright desk, the product on the left, and a short headline in our brand colors.

What MCP is

MCP is how Claude, ChatGPT, or the agent you already use does work inside AymarTech. You ask in a sentence. The client calls the matching AymarTech tool. AymarTech runs that action when your token allows it, and keeps the record.

How to connect

Create a token on your AymarTech login

Name the token and keep only the scopes that client needs. You can limit it to specific projects and set an expiry. AymarTech shows the secret once. It starts with aym_mcp_. AymarTech stores only a hash.

Point the client at this server

In Claude, ChatGPT, or another MCP client, add a custom remote server. URL: https://app.aymar.tech/mcp. Header: Authorization: Bearer, then the token. This is not an install from an app store.

Ask in the chat you already use

The client calls only the tools on that token. Signing in to WordPress, Shopify, Webflow, or Google still happens in AymarTech, by you.

Revoke the token to disconnect

Revoke it on that AymarTech login, or let the expiry date pass. The next request stops before any tool runs.

The address your client needs

The server speaks Streamable HTTP. Send the token on every request as a bearer credential. The secret always starts with aym_mcp_.

Server address

https://app.aymar.tech/mcp

Authorization header

Authorization: Bearer aym_mcp_…

Replace aym_mcp_… with the token from your AymarTech login. Do not send the project API key. That key is not accepted as MCP authentication.

{
  "mcpServers": {
    "aymartech": {
      "url": "https://app.aymar.tech/mcp",
      "headers": {
        "Authorization": "Bearer aym_mcp_…"
      }
    }
  }
}

What you can ask

These are prompts a person would type. Under each one is the real tool the client uses, and the scope that tool requires.

Fix an article

The onboarding article sounds stiff. Rewrite the introduction in our brand voice and leave the rest of the post as it is.

The client saves the revised article with update_article. Editing does not by itself publish. If the article is already live, the save can sync to your CMS, and that sync still has to be checked before you treat the public page as updated.

Uses

  • update_article · content:write

Add a section

Add a section to the CRM comparison that explains how pricing is usually structured. Keep the current title.

There is no separate “add a section” action. The client reads the article and saves the full revised version, including the new section, with update_article.

Uses

  • update_article · content:write

Change a title

Change the title of yesterday’s article to “A simpler way to onboard new users.”

update_article can change the title, slug, and SEO fields without rewriting the body.

Uses

  • update_article · content:write

Check indexing status

Has Google accepted an indexing request for the onboarding article, and is the live URL confirmed?

That question is a read. get_publication_status reports the provider lifecycle, the confirmed live URL, and indexing checkpoints. Asking the client to request indexing is a different action, request_article_indexing, and it needs publishing:write. Google accepting the request is not the same as indexing the page.

Uses

  • get_publication_status · content:read

Adjust the content plan

Look at next week’s plan. Drop the generic CRM tip and move the onboarding topic to Monday.

Reading the plan uses list_article_suggestions. Rejecting, editing, or rescheduling a suggestion that has not been generated yet uses update_article_suggestion. A brand-new calendar is request_content_plan, which needs planning:write and does not itself spend an article credit.

Uses

  • list_article_suggestions · content:read + projects:read
  • update_article_suggestion · content:write

Tools and the scopes they need

Every name below is a tool the AymarTech MCP server registers, with the scope checked before it runs. A missing scope stops the call. It does not skip the check.

A new token includes these scopes and does not include billing: projects:read, projects:write, content:read, content:write, planning:write, generation:write, publishing:write, monitoring:read, integrations:write, social:write, uploads:write, monitoring:write

See your projects

projects:read

Look up projects this login can already open, read the business and SEO profile, see what setup is still missing, and check whether a provider is connected. Credentials are not included.

Does not create a project, change settings, or reveal CMS passwords, OAuth tokens, or webhook secrets.

  • list_projects
    projects:read
  • get_project_context
    projects:read
  • get_project_setup_status
    projects:read
  • get_agent_workflow
    projects:read
  • get_next_actions
    projects:read
  • get_usage_and_costs
    projects:read
  • get_integration_guide
    projects:read
  • get_integration_status
    projects:read
  • list_integration_targets
    projects:read
  • test_integration
    projects:read

Set up a project

projects:write

Create a project, update its profile, answer setup questions, and set the schedule, translations, and auto-publishing.

Does not publish an article. Auto-publishing is rejected until the selected destination is connected. A token limited to a fixed project list cannot create a project.

  • create_project
    projects:write

    Unavailable when the token is limited to a fixed project list.

  • configure_project
    projects:write
  • configure_automation
    projects:write
  • start_project_setup
    projects:write
  • answer_project_setup_questions
    projects:write

Read content and status

content:read

Read the content plan, articles, translations, images, generation progress, and whether a publish actually went live.

Does not edit an article, replace an image, or change what is published.

  • list_article_suggestions
    content:read

    Also needs projects:read.

  • list_articles
    content:read

    Also needs projects:read.

  • get_generation_status
    content:read
  • get_article
    content:read
  • list_article_images
    content:read
  • get_article_image_status
    content:read
  • get_publication_status
    content:read
  • list_project_knowledge
    content:read
  • list_article_translations
    content:read
  • get_article_translation
    content:read
  • get_instagram_profile
    content:read
  • list_instagram_posts
    content:read
  • get_instagram_publication_status
    content:read

Edit content

content:write

Update article text and SEO fields, import an article, archive an unpublished article, edit translations, and change keywords, internal links, and products.

Does not publish, unpublish, or schedule. Those stay on publishing:write, or social:write for an Instagram project.

  • update_article
    content:write
  • create_article
    content:write
  • archive_article
    content:write
  • update_article_suggestion
    content:write
  • request_article_translations
    content:write
  • update_article_translation
    content:write
  • retry_article_translation
    content:write
  • archive_article_translation
    content:write
  • replace_article_image
    content:write

    Older compatibility tool. Prefer create_asset_upload and complete_asset_upload.

  • regenerate_article_image
    content:write

    Also needs generation:write, and uses one AymarTech credit.

  • upsert_project_keyword
    content:write
  • archive_project_keyword
    content:write
  • upsert_internal_link
    content:write
  • set_internal_link_enabled
    content:write
  • upsert_product
    content:write
  • set_product_enabled
    content:write
  • archive_product_image
    content:write
  • reorder_product_images
    content:write

Queue a content plan

planning:write

Ask AymarTech to build a new content calendar for a project that is already configured.

Does not spend an article credit by itself, and it does not publish the suggestions.

  • request_content_plan
    planning:write

Start generation

generation:write

Start an article from a topic you name, or from a suggestion already on the plan. A new generation uses one AymarTech credit.

Does not edit an existing article. Image regeneration also needs content:write and uses one credit of its own.

  • request_article_generation
    generation:write
  • generate_article_from_suggestion
    generation:write
  • regenerate_article_image
    generation:write

    Also needs content:write, and uses one AymarTech credit.

Change what is live

publishing:write

Publish, update, or unpublish a blog article, schedule it, set the blog publication policy, and queue a Google Indexing API request for a published URL.

A queued publish is not a live page. Check get_publication_status. Google accepting an indexing notification is not the same as indexing the page. Public demo links need a platform-wide administrator token.

  • request_article_publication
    publishing:write
  • schedule_article
    publishing:write
  • request_article_indexing
    publishing:write
  • configure_publication_policy
    publishing:write

    Blog projects. An Instagram project needs social:write instead.

  • approve_channel_autonomy
    publishing:write

    Blog projects. An Instagram project needs social:write instead.

  • set_article_demo_status
    publishing:write

    Platform-wide administrator token only.

Read operational health

monitoring:read

Read a snapshot of setup, generations, publishing, incidents, notifications, and recent MCP writes.

Does not retry work or change content.

  • get_operations_overview
    monitoring:read

Retry and check quality

monitoring:write

Retry a failed setup workflow, and run the publication quality check. That check does not use a credit.

Does not publish the article.

  • retry_agent_operation
    monitoring:write
  • request_article_quality_check
    monitoring:write

Change a connection

integrations:write

Choose a publishing target that is already authorized, turn a provider off for the project, and submit a changed sitemap to Search Console.

Does not log in to WordPress, Shopify, Webflow, Google, or any other provider. You still approve those connections in AymarTech. A sitemap submission is limited to once per project per 24 hours and does not mean the article was indexed.

  • select_integration_target
    integrations:write
  • disable_integration
    integrations:write
  • submit_updated_sitemap
    integrations:write

Run an Instagram project

social:write

On an Instagram project, update the profile, plan and generate posts, edit drafts, schedule them, and request publication.

Does not attach Instagram to a blog project. A business that does both uses two projects. Blog publishing uses publishing:write, not this scope.

  • update_instagram_profile
    social:write
  • request_instagram_plan
    social:write
  • request_instagram_generation
    social:write
  • create_instagram_post
    social:write
  • update_instagram_post
    social:write
  • archive_instagram_post
    social:write
  • schedule_instagram_post
    social:write
  • request_instagram_publication
    social:write
  • configure_publication_policy
    social:write

    Instagram projects. A blog project needs publishing:write instead.

  • approve_channel_autonomy
    social:write

    Instagram projects. A blog project needs publishing:write instead.

Upload an image

uploads:write

Reserve a short-lived upload link for a JPEG, PNG, or WebP image, then validate and attach the file after it is uploaded.

Does not publish the article the image belongs to.

  • create_asset_upload
    uploads:write
  • complete_asset_upload
    uploads:write

Read billing

billing:read

On a platform-wide administrator token, search customers and read a billing profile.

Not included on a normal account token. A signed-in user cannot grant this scope to themselves.

  • search_billing_customers
    billing:read
  • get_billing_customer
    billing:read

Change billing

billing:write

On a platform-wide administrator token, create a billing customer, update the local subscription, and record a payment.

Not included on a normal account token. These tools are not registered at all unless the token has platform-wide administrator access.

  • create_billing_customer
    billing:write
  • update_billing_customer
    billing:write
  • update_billing_subscription
    billing:write
  • record_billing_payment
    billing:write

An AI client can write to your site

A token is the permission you hand that client. Here is what a normal AymarTech token can change, what it cannot reach, where the record lives, and how you take it back.

What it can do

A new token includes the control-plane scopes and leaves billing off. On projects that login already opens, the client can edit an article, its title, and its cover, queue a content plan, and start a generation. A generation uses one AymarTech credit. Publishing, unpublishing, or scheduling a blog post also needs publishing:write. An Instagram project uses social:write for that kind of change. The project owner can do this. A viewer share can read. An editor or admin share can change the project.

What it cannot do

It cannot read a CMS password, an OAuth token, a webhook secret, or the project API key. That API key cannot sign in to MCP. content:write edits an article and does not publish it. The client cannot finish a login to WordPress, Shopify, Webflow, or Google. You do that in AymarTech. A project limit only removes projects. Billing tools are not on a normal token. One project is a blog or Instagram, not both. A queued publish, an accepted indexing request, and an accepted sitemap submission still have to be checked with get_publication_status before the public page counts as changed.

How you see what it did

Each write is stored on the token that made it: the tool name, the project, the status, and the time. The article text and any secret are not stored in that record. The token shows when it was last used. With monitoring:read, get_operations_overview lists that token's recent writes on one project — tool, status, error, and timestamps — plus publishing commands and whether a live URL is confirmed. The list is for the token that asks, not every token on the account.

How you revoke access

Revoke the token on the AymarTech login that owns it. The next request fails before MCP starts and before any tool runs. An expired token fails the same way. Deleting the chat in Claude or ChatGPT leaves the token valid.

Questions

It is the connection that lets Claude, ChatGPT, or another MCP client call AymarTech on your behalf. You ask in plain language. The client uses AymarTech’s tools. AymarTech allows only what that token’s scopes and your project role permit.

Add a custom remote MCP server at https://app.aymar.tech/mcp and send Authorization: Bearer plus your aym_mcp_ token. AymarTech does not ship a separate app-store plugin. The client has to support a remote MCP server with that header.

Only if the token includes publishing:write for a blog project, or social:write for an Instagram project, and your role on that project can publish. A queued request is not a live URL. The client should read get_publication_status before treating the page as published.

Revoke the token on that AymarTech login. Revoked and expired tokens are rejected before any tool runs. Deleting the chat in Claude or ChatGPT does not revoke the token. The token does.

No. request_article_indexing queues one Google Indexing API notification per article per 24 hours, and it needs publishing:write. get_publication_status shows what happened next. Google accepting the notification is a separate state from crawling or indexing the page.

Your panel, in the chat you already use

Connect AymarTech to an MCP client

Open AymarTech