RSS to Misskey and Sharkey: Auto-Post Notes From Your Feed

Updated: 2026-09-28

Short answer: in Misskey, go to Settings → API and create an access token with the write:drive permission, then open Accounts → Add new Misskey account in PostRSS and enter your server address together with the token. Open Цілі → Add feed, choose Misskey in Target settings and add your feed under Add source (Type = RSS feed, Link = your feed address). Every new item is posted as a note with its title, link and image. It works on misskey.io and any other Misskey server, and on the Sharkey, CherryPick, Foundkey and Iceshrimp forks. Misskey is included from the Professional plan.

Misskey is the third major ActivityPub platform after Mastodon and Pleroma, and the one with the largest presence in Japan. It federates with everything else on the Fediverse, so a note posted to a Misskey server reaches followers on Mastodon just as readily as followers on misskey.io. Its forks — Sharkey being the most widely deployed — behave the same way from an integration point of view.

Why this is one of the easier connections

There is no developer registration, no app submission and no review. You create an access token inside your own account settings, decide what it is allowed to do, and paste it in. Revoking it later is a single click on the same screen, and doing so affects nothing else about the account.

That model — the user issuing their own credential, scoped to what they want — is what most of the Fediverse does, and it is why platforms like this take two minutes to connect while a mainstream social network takes two weeks of app review.

Setting it up, step by step

1. In Misskey, open Settings → API and create an access token. Grant it the write:drive permission — without that, images cannot be uploaded and notes arrive as text only.
2. In PostRSS, open Accounts and choose Add new Misskey account. Enter the server address (misskey.io or whichever instance your account lives on) and the token.
3. Open Targets and click Add feed. One feed going to one destination is one Target.
4. In Target settings, choose Misskey and the account you just connected.
5. Click Add source. Set Type to RSS feed and paste your feed address into Link. Save.
6. Check the first item that arrives. PostRSS checks the feed every 5 minutes (every minute on Enterprise plans), so the wait is short.

What gets posted, and the Drive permission

Each new item becomes a note carrying the title, the link and the image. The image is uploaded to your Misskey Drive and attached to the note, which is why the token needs write:drive. This is far and away the most common setup mistake: a token created without that permission connects successfully and then produces notes with no pictures, which looks like a bug and is not.

Uploading rather than hot-linking also means the image belongs to your account. It keeps working if the original article's image is moved or removed, and it renders properly for followers on servers that do not fetch remote media.

Server limits are respected, not guessed

Misskey servers configure their own maximum note length, and administrators change it — 3,000 characters is common, but it is a setting, not a standard. PostRSS reads the limit from the server it is posting to rather than assuming one, so a note is trimmed to what that particular instance accepts.

The same applies to rate limiting. When a server asks a client to slow down, PostRSS waits rather than retrying immediately. On a small instance run by one person on a modest machine, that politeness is the difference between an integration administrators tolerate and one they block.

Sharkey, CherryPick, Foundkey, Iceshrimp

Misskey is open source and has been forked repeatedly, usually to add features or to take the project in a different direction. Sharkey is the most widely deployed of those forks today; CherryPick, Foundkey and Iceshrimp each have their own communities.

All of them keep the Misskey API, which means the connection is identical: server address, access token from Settings → API, same write:drive requirement. If you are unsure which software an instance runs, it usually says so in the footer or on its about page — and if it is one of these, it will work.

Where Misskey sits next to Mastodon

They federate with each other, so this is not an either-or. The practical differences are cultural and geographic: Misskey's centre of gravity is Japanese, its feature set is more playful (custom emoji reactions rather than a single favourite), and its instances tend to be smaller and more tightly themed.

For a publisher with any Japanese readership, connecting both is the obvious move — one feed, two Targets, audiences that barely overlap. Misskey sits on the Professional plan and Mastodon on Ultimate, which makes Misskey the cheaper of the two to reach.

What it does not do

PostRSS publishes items that appear in the feed after the Target starts running. Connecting an established feed does not import its back catalogue, which is deliberate — the alternative is a destination flooded with years of archive on day one.

It does not react, renote, follow or reply. The note is posted; everything social about the account stays with you.

Which plan includes it

Misskey is included from the Professional plan. Each destination you connect counts as one Target, and your plan sets how many Targets and how many posts a month you get. An annual subscription is cheaper than paying monthly. The current limits for every tier are on the pricing page, and the full list of 66 networks is on the supported networks page. The Misskey page has the short version.

Troubleshooting

• Notes arrive without images. The token is missing write:drive. Create a new one with that permission.
• Authentication fails. Check the server address is the instance your account actually lives on, and that the token has not been revoked in Settings → API.
• Notes are shorter than expected. That instance has a lower maximum note length. The limit is the server's, not the integration's.
• Posting is slow during busy periods. The server asked for a slower rate and PostRSS waited. This is intentional.
• Nothing is posting. Confirm the feed has published something new since the Target was created.

Etiquette on a small instance

Most Misskey and Sharkey servers are run by one person paying for a small machine, and an automated account is a guest on that infrastructure. Three things keep it welcome.

• Check the instance rules first. Many spell out their position on bots and automated posting. Most are fine with it when the account is clearly labelled; a few are not, and it is better to know before you connect.
• Mark the account as a bot in its profile. Misskey has the setting. It is honest, and clients use it to let people filter.
• Consider hosting your own. If your feed is busy, running your own instance means the load lands on your infrastructure rather than on a volunteer's.

One feed, several Fediverse destinations

Because they all federate, it is tempting to connect Misskey, Mastodon and Pixelfed to the same feed and reach everyone. It works, and it produces one visible side effect worth planning for: somebody following you on two of them sees the same article twice in the same timeline.

The usual answer is to split by content rather than by network. Mastodon takes everything, Pixelfed takes the items with images, and Misskey takes the feed most relevant to its audience — which, given where Misskey's centre of gravity is, is often a Japanese-language or Japan-relevant category if you have one.

Frequently Asked Questions

Why are my Misskey notes missing images?

The access token almost certainly lacks the write:drive permission. Images are uploaded to your Misskey Drive before being attached, so without it the note is posted as text only. Create a new token in Settings → API with that permission.

Does this work on servers other than misskey.io?

Yes. Any Misskey instance works — you enter its address along with a token created on that server.

Do Sharkey, CherryPick, Foundkey and Iceshrimp work?

Yes. They are Misskey forks that keep the same API, so the setup is identical: server address plus an access token from Settings → API.

What happens if a note is longer than the server allows?

PostRSS reads the note length limit from the server it is posting to and trims to fit, rather than assuming a fixed number. Different instances configure different limits.

Can people on Mastodon follow my Misskey posts?

Yes. Misskey speaks ActivityPub, so notes federate to Mastodon and the rest of the Fediverse, and followers there see them in their normal timeline.

Which plan includes Misskey?

The Professional plan, which also covers the blogging, CMS and team-chat destinations. Mastodon sits on Ultimate, so Misskey is the cheaper of the two Fediverse microblogging destinations to reach.

The bottom line

Misskey is a two-minute connection with one thing to get right: give the access token the write:drive permission so images come through. After that, every new article posts itself as a note that reaches Misskey, Sharkey and Mastodon followers alike. It is included from the Professional plan.