Skip to content
Reachype
TR EN

Reachype for AI assistants

Connect your Reachype workspace to ChatGPT, Claude, Claude Code or Cursor, and ask about your brand, your content calendar and your results in the assistant you already use. The connection runs on the Model Context Protocol (MCP), an open standard for giving an assistant access to an app.

What it does

Once connected, your assistant can read what you can already see in Reachype: your workspace and brand profile, the content calendar and idea backlog, campaigns, products, the latest research report, and performance figures. With your permission it can also rewrite the copy of a planned post, and start a UGC video ad or a carousel.

It works inside one workspace that you choose when you connect, and it can only do what your own role in that workspace allows. If your role changes or you leave the workspace, the connection follows. It is a way to use Reachype from another place, not a separate product: nothing here is sold inside ChatGPT or Claude, and plans and credits are managed in Reachype only.

Before you start

  • A Reachype account with access to a workspace.
  • The workspace’s AI assistant access switched on. People who can manage the workspace control it under Settings → Workspace → AI assistant connections.
  • An assistant that supports remote MCP servers with sign-in: ChatGPT, Claude (claude.ai), Claude Code or Cursor.

How to connect

Every assistant needs the same address. It is the only thing you paste; you then sign in to Reachype and choose what to allow.

Reachype MCP server URL

https://mcp.reachype.com/mcp

What happens when you connect

  1. Your assistant opens a Reachype sign-in page in your browser. Sign in as usual, including two-factor if you use it.
  2. You choose one workspace and the permissions to grant: read is always on, edit is on by default, and generate is off unless you turn it on.
  3. You approve, and the assistant returns with access. A different workspace needs a separate connection.

ChatGPT

  1. In ChatGPT, open Settings and add a custom app or connector. Developer mode may need to be switched on first, depending on your plan.
  2. Paste the server URL above as the MCP server address and choose OAuth as the authentication.
  3. Follow the Reachype sign-in, approve, then start a chat and select Reachype from the tools menu.

Claude

  1. In claude.ai, open Settings → Connectors and choose Add custom connector.
  2. Give it the name Reachype and paste the server URL above.
  3. Click Connect, approve on the Reachype page, then enable the connector in a chat.

If you add Reachype from Claude’s connector directory rather than with the address above, you get a version without generation: it reads your workspace and edits planned copy, but it cannot start videos or carousels, because Claude’s directory does not list media-generation tools. For the full set, generation included, add Reachype as a custom connector with the server URL above.

Claude Code and Cursor

Claude Code: run this once in a terminal, then use /mcp inside Claude Code to sign in.

claude mcp add --transport http reachype https://mcp.reachype.com/mcp

Cursor: add this to your MCP configuration (for example .cursor/mcp.json), then sign in when Cursor asks.

{
  "mcpServers": {
    "reachype": {
      "url": "https://mcp.reachype.com/mcp"
    }
  }
}

Menus move around as these products change. If a label above does not match what you see, look for “custom connector”, “custom app” or “MCP server” in the assistant’s settings.

What your assistant can do

Reachype gives the assistant the following tools. It chooses between them from what you ask; you never call them by name. Each example is a sentence you could type.

Read

Look things up. These never change anything.

  • Workspace overview get_workspace_overview

    Summarise the connected Reachype workspace: its name and plan, your role, the projects (brands) you can access with their ids, the brand basics of the selected project, and the credit balance and usage for the current billing period.

    Example“Which projects are in my Reachype workspace, and how many credits do I have left this month?”

    Needs: Read permission

  • Brand profile get_brand_profile

    Read the full brand profile of one project: identity, positioning, audience and personas, voice (tone, writing style, preferred and forbidden words), messaging, and an excerpt of the brand guidelines.

    Example“Summarise our brand voice from Reachype in five bullet points, and list the words we should never use.”

    Needs: Read permission

  • Content performance get_marketing_performance

    Read measured performance of published content for the project’s active plan period, grouped by channel, content pillar, format, campaign or funnel stage, with how many posts were measured and whether that supports a conclusion (has_evidence).

    Example“Which channel and content pillar performed best in the current plan period, and is there enough data to say so?”

    Needs: Read permission

  • Marketing dashboard get_marketing_dashboard

    Read one analytics dashboard of the project over a period: headline figures (spend, revenue, ROAS, CPA, conversions, impressions, clicks, orders, installs) beside the previous period, breakdowns by platform, campaign, ad, keyword, audience, product or app, and significant changes.

    Example“Show me last month’s marketing dashboard compared with the month before, and point out the biggest changes.”

    Needs: Read permission

  • Social account insights get_channel_insights

    Read one connected social account of the project (Instagram, TikTok, YouTube or X): followers, typical post, engagement rate, posting rhythm, the last 28 days against its own history, results by format and posting time, best and weakest posts, and findings.

    Example“How is our Instagram account doing, and which posting times and formats work best for it?”

    Needs: Read permission

  • Planned content list_content_items

    List planned content items — the dated content calendar — of the project, optionally filtered by channel, status or date range, as summaries plus the total number that matched.

    Example“What is on the content calendar for the next two weeks, and what is still a draft?”

    Needs: Read permission

  • Content item get_content_item

    Read one planned content item in full: hook, brief, call to action, draft copy, schedule slot, priority, publication status, and the objective, pillar and campaign it serves.

    Example“Open the post scheduled for Friday and show me the hook, the draft copy and the call to action.”

    Needs: Read permission

  • Content ideas list_content_ideas

    List backlog content ideas of the project in the order the Ideas board shows them (highest score first, then newest), with status, score, channels, format and notes.

    Example“What are the five highest-scored ideas in our backlog?”

    Needs: Read permission

  • Campaigns list_campaigns

    List the project’s marketing campaigns with their dates, status, channels and funnel stage.

    Example“List our active campaigns with their dates and channels.”

    Needs: Read permission

  • Search workspace search_workspace

    Keyword search across the project’s planned content, backlog ideas, campaigns, research findings, channel strategies and knowledge-base documents. Returns references (type, id, title, snippet), not whole documents.

    Example“Search my workspace for everything we have on “free shipping”.”

    Needs: Read permission

  • Products list_products

    List the products set up in the project — what UGC ads and product visuals are made from — with title, brand, variant, status and whether each is ready.

    Example“Which of my products are ready to be used for a UGC ad?”

    Needs: Read permission

  • Latest research get_latest_research

    Read the project’s most recent finished competitor and market research report: executive summary, market landscape, opportunities, threats, recommendations and the competitors analysed.

    Example“What did the latest competitor research find, and what does it recommend?”

    Needs: Read permission

  • Generation status get_generation_status

    Read where a UGC ad run or a carousel stands: queued, running, succeeded, failed or canceled, the current stage, a user-safe error, and links to the finished video or slide images.

    Example“Is my video ad finished yet?”

    Needs: Read permission

Edit

Rewrite the copy of a planned post or an idea. Each edit shows what changed and can be undone.

  • Edit content item update_content_item

    Rewrite the copy of one planned content item — title, hook, brief or call to action — and return each changed field before and after, with a change id that can undo it.

    Example“Rewrite the hook of Friday’s post to be shorter and more direct.”

    Needs: Edit permission

  • Edit content idea update_content_idea

    Rewrite one backlog content idea — its title and/or notes — and return each changed field before and after, with a change id that can undo it.

    Example“Reword the title of our top idea so it leads with the benefit.”

    Needs: Edit permission

  • Undo a change undo_change

    Put back the fields one earlier edit changed, by its change id, and return what was restored.

    Example“Undo that last edit.”

    Needs: Edit permission

Generate

Price and start a UGC video ad or a carousel. These spend credits, so they are off unless you grant the generate permission.

  • Price a generation estimate_generation

    Work out what generating a UGC video ad or a carousel would make and what it would cost in credits, without starting anything, and return a quote_id valid for 10 minutes.

    Example“How many credits would a UGC video ad for our best-selling product cost?”

    Needs: Generate permission

  • Generate a UGC video ad create_ugc_ad

    Start a creator-style UGC video ad for one product of the project, with the same pipeline and price as UGC Studio, and return its run id at once.

    Example“Yes, go ahead and make that UGC ad at the price you quoted.”

    Needs: Generate permission

Credits and approvals

Generating through an assistant costs exactly the same credits as generating in Reachype: the same pipeline, the same price. You approve every generation.

To start one, the assistant first asks Reachype for a price. Nothing is started and nothing is charged at that point. The price is valid for 10 minutes and for exactly the settings it was quoted for. Your assistant then shows it to you and asks for your go-ahead, and only your approval of that price starts the generation. Asking twice with the same approval never starts a second one.

A workspace owner can also set a daily credit limit for generations started through assistants, and rate limits apply to every connection.

How to disconnect

In Reachype, open Settings → Security → Connected AI assistants and choose Disconnect next to the assistant. Access stops immediately.

People who can manage the workspace can see everyone’s connections to the workspace and disconnect any of them under Settings → Workspace → AI assistant connections. The same place has a switch that turns assistant access off for the whole workspace, which stops every existing connection at once.

You can also remove Reachype from the assistant’s own connector list. That removes it from the assistant, and disconnecting in Reachype is what ends the access on our side, so do both if you want to be sure.

How your data is handled

  • The assistant receives what a tool returns, such as brand details, calendar entries or performance figures, and it is processed by the assistant’s provider (OpenAI for ChatGPT, Anthropic for Claude, or the maker of your editor) under that provider’s own terms and privacy policy.
  • Reachype does not see your conversation. It receives only the requests the assistant sends to the tools above, and does not store the chat.
  • Reachype keeps a record of each connection (which assistant, which workspace, which permissions, when it was created and last used) until you disconnect it. Tool calls are logged with the tool name and the outcome, not with the values you or the assistant sent. Edits and generations are recorded the same way they are when you make them in Reachype.
  • Access tokens are short-lived. Reachype’s own social, ad and store connections are never shared with the assistant.

Read the full details in the privacy policy.

Questions and support

Write to support@reachype.com and mention the assistant you use. If something looks wrong with a connection, disconnect it first and tell us what you saw.

Reachype

This page lists the tools the connection offers today. It is generated from the live tool definitions, so it changes when they do.