Connect an AI Assistant
Connect Claude, Cursor, VS Code, or any MCP-aware client to Nashra's MCP server at https://app.nashra.ai/mcp so it can work across your workspace for you — posts (Markdown, partial edits, sends), resources, landing pages built by Nashra's composer, the Hub, subscribers, tags, segments, automations, and Insights. Covers the Settings → AI agents (MCP) pane with the MCP link and one-click Connect, the consent screen, disconnecting apps, all 70 tools (including share kits), which tools each team role gets, how each change uses one AI assist while reading is free, who test emails can go to, and what sending requires.
What MCP is
MCP (Model Context Protocol) is an open standard that lets AI assistants call an application's functions directly, instead of you copying data back and forth by hand. Nashra runs an MCP server so a connected assistant — Claude, Cursor, or any other MCP-aware client — can read and manage your workspace on your behalf, using the same underlying actions as the Nashra dashboard.
Connecting a client
Everything starts in Settings → AI agents (MCP), in the Account group. It holds your MCP link, https://app.nashra.ai/mcp, with a Copy button, and a Connect button for Claude, Cursor, and VS Code.
Add the server
- Claude: click Connect. Nashra copies the link and opens Claude's connectors page. Choose Add custom connector and paste it.
- Cursor and VS Code: click Connect. The app opens and offers to add Nashra for you.
- Any other MCP client: click Copy and add a new server with that link.
Approve in your browser
Your client opens a browser window to sign in and approve access. Nashra's server supports OAuth discovery and dynamic client registration, so most clients complete this automatically. The consent screen reads Connect Claude to Nashra (or the app's name), shows the account you're Signed in as, and lists what the app will be able to do: Read and edit your posts and subscribers and Publish and send posts when you ask. Check it, then click Connect, or Cancel to back out.
Start using it
Once connected, ask your assistant to draft a post, add a link to your Hub, or check how last week's email did. It calls the matching tool automatically.
Nashra recognizes Claude, ChatGPT, Cursor, and VS Code by where the approval sends you, not by the name an app gives itself, and shows their real logo. Any other app shows the name it registered with, an initial instead of a logo, and a You’ll return to line naming the address approval sends you to. If that address isn't the app you expect, click Cancel.
Seeing and disconnecting apps
Once you've connected an app, it appears under Connected apps in Settings → AI agents (MCP), with when you last used it — Used today, Used yesterday, or Last used and a date. Click Disconnect to cut that app off. It loses access straight away and has to ask for your approval again to reconnect.
Connections belong to you, not to a workspace. One approval covers every workspace you're a member of, and disconnecting only ever affects your own connections.
The server identifies itself as nashra, version 1.0.0. Access is secured with OAuth 2.1 with PKCE — you don't need an API key. MCP requests get the same limit as the REST API, 60 a minute — see Rate Limits.
AI assists
Every change an AI client makes through Nashra uses one AI assist, from the same monthly allowance as Nashra's built-in AI. Reading is free: listing, looking things up, and pulling Insights cost nothing.
- Charged only when it works. A change that comes back with an error changed nothing and uses nothing.
- Taking things down is always free. Unpublishing, deleting, cancelling a scheduled email, unsubscribing someone, and pausing an automation never use an assist, so you can always take something offline. Switching workspaces is free too.
- Landing pages count once.
create-landing-pageandedit-landing-pageuse one assist each — the composer run — not two. - When the allowance runs out, every other change is refused before it runs, with a message that it refills on the 1st. Reads and take-downs keep working.
Each tool that uses an assist says so in its description, so your assistant knows before it calls it. On Free, a change that uses one also reports how many assists are left. get-workspace tells your assistant how many assists you've used this month against your plan's allowance. See AI assists for each plan's allowance.
These tools can create, edit, publish, and delete real content and subscribers — and send-post emails your actual subscriber list. Before asking your assistant to send anything for real, use send-test-post to preview it first.
Sending email
Your assistant never writes an email's HTML. send-post, schedule-send-post, and send-test-post all send the email version Nashra prepared from the post with your workspace's template — masthead, footer, and unsubscribe link included. If a post's body changed since that version was prepared (for example, the assistant just rewrote it), the send tools refuse it until the post is opened once in Nashra, which prepares the email again within a few seconds.
Emails go out from your own sender address unless the assistant picks another — list-sending-identities shows the ones you can use.
Test emails can only go to your own address, a team member's address, or one of your workspace's sender addresses — the same rule as Send test in the editor. Ask for a test to anyone else and the assistant gets an error back.
What you can ask for
The assistant composes these tools on its own, so most requests translate into one or more tool calls without you needing to name them:
- "Draft a post about our Q3 launch and put it in the Product category" →
list-categories,create-post - "Tighten the second paragraph of that draft" →
get-post,edit-post - "Send a test of this post to me before it goes out" →
send-test-post - "Schedule this for Thursday at 9am to the Newsletter segment" →
list-segments,schedule-send-post - "Build a landing page for my coaching offer, then publish it" →
create-landing-page,get-landing-page,publish-landing-page - "Add my new YouTube video to the top of my Hub" →
add-hub-link,reorder-hub-links - "Tag everyone on this list as
webinar-oct" →tag-subscribers - "Which posts did best this month?" →
list-top-content - "Which workspace am I in — switch me to the other one" →
list-workspaces,switch-workspace
The assistant only has the 70 tools listed below — it can't do anything in Nashra that isn't backed by one of them. Writes run through the same checks the dashboard uses: plan limits when publishing or creating, and account health, sending quota, and payment status before a send. Sending — now or scheduled — needs a paid plan or a payment method on file, just like sending from the editor.
Every tool carries a readable title and tells your client whether it only reads, only adds something new, or changes or removes something that already exists. Most clients, Claude included, ask you to confirm before running one that changes or removes something.
Access and permissions
An MCP connection acts as the Nashra account that approved it, in the workspaces that account belongs to — use list-workspaces and switch-workspace to move between them. There are no separate scopes to configure.
An assistant can do only what your role allows in the workspace you're in, the same as the dashboard:
| Who | Tools they get |
|---|---|
| The workspace owner | All 70 |
| Full access | All 70 |
| Publishing | Posts, Subscribers, Tags & segments, plus Insights and Workspace — 40 tools |
| Automations | Resources, Landing pages, Hub, Automations, plus Insights and Workspace — 37 tools |
Insights and Workspace tools are open to every member; list-top-content leaves out the kinds of content your role doesn't cover. A tool you can't use isn't offered to your assistant at all. The role is checked in the active workspace, so switching workspaces can change the list. When someone leaves, removing them from the team also cuts their assistant off from the workspace. See Team & Roles for how roles work.
Some tools also need a verified email address, just like in the dashboard: publishing a post and every send or test send; creating, changing, publishing, unpublishing, or deleting a resource; creating, editing, publishing, or unpublishing a landing page; every change to the Hub; and starting or pausing an automation.
Tools
Nashra's MCP server exposes 70 tools. Your client sees each by the name below and a readable title.
Posts
| Tool | What it does |
|---|---|
list-posts | Lists posts with optional search, status filter (draft, published, scheduled, or sent), category filter, and pagination. Read-only. |
get-post | Gets one post: its body in Markdown (or editor JSON), status, category, and email open and click rates. Read-only. |
create-post | Creates a draft post, optionally with a title, a body in Markdown, and a category. Nothing is published or sent. |
edit-post | Changes part of a post's body — swaps exact pieces of text for new Markdown — without rewriting the rest. Anything you changed since the assistant read the post is kept. |
update-post | Changes a post's title, slug, or category, or replaces its whole body. Refuses to overwrite blocks Markdown can't carry, such as embeds or buttons, unless told to. |
delete-post | Moves a post to the trash. It leaves your website straight away, and any email scheduled for it is cancelled. It can be restored from the dashboard for 30 days, but restoring doesn't reschedule the email. |
publish-post | Publishes a post on your website at a given slug, after checking plan limits. Returns the live URL. |
unpublish-post | Takes a post off your website, back to draft. |
send-test-post | Sends a test of the post's email to one inbox your workspace owns. |
send-post | Emails a post now — to everyone, or to one segment. |
schedule-send-post | Schedules a post's email for a date and time in the workspace's timezone — to everyone, or to one segment. |
unschedule-send-post | Cancels a post's scheduled email before it goes out — one send, or every scheduled send of the post. The post itself is untouched and can be scheduled again. |
list-categories | Lists your post categories. Read-only. |
create-category | Creates a post category (up to 100 per workspace). |
get-share-kit | Gets a post's share kit — the caption and Instagram carousel that Share on social media turns into images — and the text ready to post on each network, with the tagged link and where it goes. The link appears once the post is live. Read-only. |
update-share-kit | Changes a post's share caption, the words its quote slide marks, or its Instagram carousel (up to eight slides). Only the fields you give change. The images are still made in Nashra, from Share on social media. |
Resources
| Tool | What it does |
|---|---|
list-resources | Lists your resources with their status, public URL, and sign-up count. Read-only. |
get-resource | Gets one resource: headline, sign-up form, what the reader gets, follow-up email, status, URL, and sign-ups. Read-only. |
create-resource | Creates a draft resource. Add the cover image in the dashboard. |
update-resource | Changes a resource. On a live resource the change shows straight away. |
publish-resource | Puts a resource live, or switches a live one between listed on your Hub and unlisted. |
unpublish-resource | Takes a resource offline, back to draft. Everyone who signed up stays a subscriber. |
delete-resource | Permanently deletes a resource. The subscribers it brought in stay. |
Landing pages
| Tool | What it does |
|---|---|
list-landing-pages | Lists your landing pages with their status and public URL. Read-only. |
get-landing-page | Gets one landing page: settings, status, URL, an outline of its sections, and whether the composer is done, still working, or has a question. Read-only. |
create-landing-page | Creates a draft and has Nashra's page composer build it from a brief — the offer, who it's for, the one action it asks for, and real details to use. Takes about a minute. Nothing is published. |
edit-landing-page | Asks the composer to change a page in words, like "rewrite the hero for founders". It can't pick images, change the theme, or edit the title or slug. The draft it replaces stays in version history. |
publish-landing-page | Publishes the page's current draft, or pushes a live page's latest edits live. |
unpublish-landing-page | Takes a live page offline and off your Hub. The page and its draft stay. |
delete-landing-page | Deletes a landing page. The subscribers it brought in stay. |
Hub
| Tool | What it does |
|---|---|
get-hub | Gets your Hub: URL, whether it's published, headline and bio, sections in order, and links. Read-only. |
update-hub-profile | Changes the Hub's headline and the bio line under it. |
add-hub-link | Adds a link to the end of your links. Nashra takes the page's title and image for the card unless you give a label; a video link shows under Videos. |
update-hub-link | Changes a link's label or address, or makes it the featured link. |
remove-hub-link | Takes a link off your Hub. |
reorder-hub-links | Puts your links in a new order. |
update-hub-sections | Reorders the Hub's sections and shows or hides them. The masthead always stays first. |
Subscribers
| Tool | What it does |
|---|---|
list-subscribers | Lists subscribers with optional search, status filter (subscribed, unsubscribed, or unconfirmed), and pagination. Read-only. |
get-subscriber | Looks up one subscriber by UUID or email. Read-only. |
create-subscriber | Adds a subscriber with an email and optional name, tags, notes, and custom attributes. |
add-subscribers | Adds up to 50 subscribers at once. Anyone already on your list is updated instead, and someone unsubscribed stays unsubscribed. One invalid address refuses the whole batch. |
update-subscriber | Updates a subscriber by UUID or email — only the fields you provide change. |
unsubscribe-subscriber | Unsubscribes someone, as their own unsubscribe link would. They stay on record, and only they can subscribe again. |
delete-subscriber | Deletes a subscriber entirely. |
New subscribers added by an assistant don't get a confirmation email.
Tags & segments
| Tool | What it does |
|---|---|
list-tags | Lists your tags. Read-only. |
create-tag | Creates a tag, optionally with a color — and, if asked, a segment of everyone carrying it. |
update-tag | Renames a tag or changes its color. Automations that use it follow the new name. |
delete-tag | Deletes a tag from everyone. Refused while an automation triggers on or checks it. |
tag-subscribers | Adds tags to up to 100 subscribed people, creating tags that don't exist yet. Tag-triggered automations run for each of them. |
untag-subscribers | Removes tags from up to 100 subscribers. The tags themselves stay. |
list-segments | Lists your segments with their subscriber counts and rules. Read-only. |
create-segment | Creates a segment from rules — tags, email, a custom field, subscription date, engagement — and reports how many match now. |
update-segment | Renames a segment or replaces its rules. Sends and automations aimed at it reach whoever matches the new rules. |
delete-segment | Deletes a segment. The subscribers in it aren't touched. |
Automations
| Tool | What it does |
|---|---|
list-automations | Lists your automations: started or paused, trigger, and number of steps. Read-only. |
get-automation | Gets one automation's trigger and steps in order, with how many subscribers are waiting at or have passed each step. Read-only. |
create-automation | Creates an automation, paused, optionally with its trigger. Within your plan's number of automations. |
set-automation-trigger | Sets what starts it: someone subscribing (anywhere, or from one form or resource), or a tag being added or removed. |
add-automation-step | Adds a step: send an email, wait, add or remove tags, or a condition that splits into yes and no branches. |
remove-automation-step | Removes a step. Subscribers waiting at it leave the automation. |
start-automation | Starts it, so its trigger catches people and its emails go out. Refused while your account can't send or a step is incomplete. |
pause-automation | Pauses it until it's started again. |
delete-automation | Permanently deletes an automation. The posts its emails used stay. |
Insights
| Tool | What it does |
|---|---|
get-insights | Your workspace's numbers over a date range (30 days by default), as Insights shows them: subscriber growth, email performance, and website traffic. Read-only. |
list-top-content | How each post, landing page, resource, and Hub link did, best first, with a verdict against your own usual. Read-only. |
get-content-insights | The numbers for one post, landing page, resource, or the Hub: traffic and sources, subscribers it brought in, and for a post its email results. Read-only. |
Workspace
| Tool | What it does |
|---|---|
get-workspace | Gets the active workspace: name, website URL, language, plan, and this month's subscribers, email sends, and AI assists against your plan's limits. Read-only. |
list-sending-identities | Lists the sender addresses you can send from, marking the workspace default and yours. Read-only. |
list-workspaces | Lists every workspace the authorizing account belongs to, and marks the active one. Read-only. |
switch-workspace | Switches the active workspace. Fails if the account doesn't belong to it. |