Let your AI client draft. You review on the calendar.
Connect Claude, Cursor or ChatGPT to NioConnect, ask for a post, and it lands as a draft you approve. Six tools, and only one writes.
A standard way for an AI client to use NioConnect
The Model Context Protocol (MCP) is an open standard for connecting AI clients to the tools of other products. NioConnect runs an MCP server, so the client you already use can look at your workspace and save drafts for you to review.
Your client, your account
Claude, Cursor or ChatGPT connect to NioConnect the way they connect to any MCP server. You keep using the client you already use.
It reads before it writes
Five of the six tools only read: your channels, a platform’s rules, your posts and your workflows. The sixth saves a draft.
You approve every post
A draft lands on your calendar. Nothing reaches a platform until you schedule it, and your approval rules still apply.
How does it work? Pick a prompt and watch.
Your AI client calls NioConnect’s tools. Everything it saves lands on your calendar as a draft, never straight onto a platform.
- Draft a launch post for Bluesky and Mastodon. Do not schedule it.
- Checking which channels are connected and what Bluesky accepts.
list-channels({})2 channels: Bluesky and Mastodon, both healthyget-platform-rules({ platform: "bluesky" })Text, images with alt text, threadscreate-post({ channelIds: ["bsky", "mstdn"], content: "Our spring release is live..." })Saved as a draft. Nothing is scheduled.- Saved as a draft on your calendar. Nothing goes out until you review it and schedule it yourself.
API key. Run this in your terminal. It works from any folder.
claude mcp add --transport http nioconnect <your workspace MCP address> --header "Authorization: Bearer <your key>"list-channelsget-platform-rulescreate-postlist-postslist-workflowsget-workflow
Works with five AI clients
The same six tools, whichever client you use.
- Claude CodeAPI keySet up
- CursorAPI keySet up
- Claude DesktopRemote connectionSet up
- claude.aiRemote connectionSet up
- ChatGPTRemote connectionSet up
Product names and logos belong to their owners and are used only to identify compatibility. NioConnect is not affiliated with or endorsed by them.
Connect an AI client in three steps
Pick a client, copy one thing, paste it where that client expects it. Remote clients sign you in; the others take a key.
Copy your workspace address
In NioConnect open Developers and choose Claude Desktop. The address there is yours.
Connector address<your workspace MCP address>Add it to Claude Desktop
In Claude Desktop, add a custom connector from its settings and paste this address as the connector URL.
Sign in and allow
Claude Desktop opens NioConnect so you can sign in. Press Allow, then ask for a draft.
You sign in and press Allow. Nothing is pasted and nothing is stored. The connection acts with your role, checked on every call, and can use only the six tools.
Placeholders only. The Developers page in the app fills in your own address and key. Full Claude Desktop guide
Six tools, and only one writes
Everything else is read only. The one that writes saves a draft.
| Tool | What it does | Access |
|---|---|---|
list-channelsList connected channels | See which accounts the workspace publishes to, with the id each other tool needs and whether the connection is healthy. | Read only |
get-platform-rulesRead a platform's rules | Ask what one platform accepts: media, threads, communities and the extra settings a post needs. | Read only |
create-postCreate a draft post | Save a post to the calendar as a draft. A time is only set when you ask for one, and a time in the past is refused. | Writes a draft |
list-postsList scheduled and published posts | Read a page of posts, newest first, including ones waiting on a teammate to approve. | Read only |
list-workflowsList workflows | Read the workflows that copy one channel to another, with status, schedule and counters. | Read only |
get-workflowGet one workflow | Open a single workflow to see its channels, status, schedule and when it posts next. | Read only |
An assistant gets the same rules as you
Nothing about connecting an AI client loosens how publishing works.
Same validation as you
A post an assistant creates is checked against the same platform rules as one you write. One a platform would refuse comes back with the reason, and nothing is saved.
Approval still applies
When your workspace requires approval, a scheduled post waits for it like any other. Assistants save drafts by default and cannot publish immediately.
You can tell what it made
A post created through an AI client is marked as made by an AI assistant on the calendar and in the post details, so nothing arrives unlabelled.
Emergency stop and revocable keys
An emergency stop holds an assistant’s posts like anyone’s. Revoke a key or a connection and access ends at once. A key never has more than its Member’s permissions.
Prompts that work with the six tools
Copy one into your client. It reads your channels and rules, and saves a draft when you ask for one.
- Which of my channels are connected, and are any unhealthy?
- What does Bluesky accept in a post?
- Draft a launch post for Bluesky and Mastodon. Do not schedule it.
- What is scheduled this week, and is anything waiting on approval?
- Which workflows copy one channel to another, and when do they post next?
- Draft a three post thread about our release for Mastodon.
Building something of your own? Use an API key
Keys are for clients that read a config file. They carry no more power than the person who made them.
Create a key in the app
Open Developers and create an API key. You see it once, so copy it then. Claude Code and Cursor take a key; the other clients sign in instead.
Create and revoke an API keyA key acts as its Member
A key has the permissions of the Member who made it, and no more. There are no key scopes. Remove or demote the Member and the key is limited at once.
Revoke it any time
Revoke a key or a connection and access ends immediately. An emergency stop holds an assistant’s posts like anyone’s.
MCP or a key, nothing else yet
There is no SDK or command line tool today. Connect through MCP or an API key, with the six tools above.