Every Mastodon account this server can act as, and which instance each lives on. Mastodon is federated, so an account is a token plus an instance: the same handle on two servers is two different people. Use the handle from here as the account argument on any other tool.

Authenticate against the instance and return the live profile. Use this to confirm a token still works, or when the user says 'me' or 'my' and you need their handle.

What this instance actually allows: the character limit, how many attachments and poll options, media size ceilings, the software version, and the server rules. Worth reading before drafting anything long, because the character limit is per instance and ranges from 500 to 11,000.

Change your display name, bio, or the four metadata fields on your profile. Only the arguments you pass are changed. Public the moment it runs, so it needs confirm: true.

Publish a status. Handles text, media with alt text, a content warning, a poll, a reply, visibility, and native scheduling. The character limit is per instance, so check get_instance_info before drafting anything long: it ranges from 500 to 11,000. Public the moment it runs, so it needs confirm: true.

Publish several statuses as one thread, each replying to the last. Every part is checked against this instance's character limit before anything is posted, so a thread never half-publishes because part four was too long. Media, a poll and the content warning apply to the first part. Public the moment it runs, so it needs confirm: true.

Change the text, content warning, media alt text or poll of a status that is already published. Mastodon keeps a public revision history and the post keeps its boosts, replies and favourites, which is why editing beats delete-and-repost. Call get_status_source first to get the exact text you are editing. Public the moment it runs, so it needs confirm: true.

The plain-text source of one of your own statuses, exactly as it was typed, plus its content warning. This is what to edit from: the rendered content is HTML with links rewritten, so editing that back would mangle every link in the post.

Every published version of a status, oldest first. Mastodon keeps edits public, so this works for anyone's post, not only your own.

Delete one of your own statuses. This cannot be undone and it discards every boost, reply and favourite it had. To fix a mistake, prefer edit_status, which keeps all of that. Needs confirm: true.

A single status by id, with its media, poll, link preview and engagement counts.

A status together with everything above and below it, nested into the real reply tree. Mastodon returns two flat lists and leaves the structure to you; this rebuilds it. Read this before replying, so the reply lands with context.

Statuses queued with scheduled_at that have not published yet.

Change when a scheduled status will publish. Minimum five minutes ahead.

Cancel a status that was scheduled but has not published.

Statuses a connected account has favourited, newest first.

Statuses a connected account has bookmarked. Unlike favourites, bookmarks are private.

Favourite a status.

Remove your favourite from a status.

Boost a status to your followers. To add a comment instead, post a status quoting its URL: Mastodon has no native quote post.

Undo a boost.

Bookmark a status. Bookmarks are private, unlike favourites, which the author can see.

Remove a bookmark.

Pin one of your own statuses to the top of your profile.

Unpin a status from your profile.

Stop being notified about replies to this thread, without leaving it. The tool nobody reaches for until a post goes unexpectedly wide.

Start being notified about this thread again.

Vote in a poll by option index, counting from zero. A vote cannot be changed or taken back, so it needs confirm: true.

Translate a status into your language using the instance's translation backend. Only works on instances that have configured one, which is a minority, so a 404 here means the feature is off rather than that the status is missing.

The accounts that favourited a status. Federation means this is only who your instance knows about, not necessarily everyone.

The accounts that boosted a status, as far as your instance knows.

Report an account, optionally with specific statuses, to your instance's moderators. Optionally forwards to the account's home instance. This reaches human moderators, so it needs confirm: true.

Statuses from the accounts and hashtags you follow, newest first. Pass since_hours to read a time window rather than a fixed count.

Everything public posted by accounts on your own instance. On a small themed instance this is the most useful timeline there is; on mastodon.social it is a firehose.

Everything public your instance has federated in from the rest of the network. Large and unfiltered: use search or a hashtag timeline if you are looking for something specific.

Public statuses carrying a hashtag. Hashtags are how discovery works on Mastodon, since there is no algorithmic feed, so this is the main way to find a conversation.

Statuses from the accounts on one of your lists. Find list ids with get_lists.

Statuses by one account, newest first. Use exclude_replies when studying how someone writes, so replies do not dominate the sample.

Search for accounts, statuses or hashtags. Pasting a URL here with resolve on is also how you pull in a remote post or profile your instance has never seen. Note that most instances do not full-text search public statuses: a thin result set is usually the instance's policy rather than a bad query.

What is trending on this instance right now: hashtags, statuses, or links. Trends are per instance, not network-wide, so a small themed server shows something completely different from mastodon.social.

Hashtags you follow. Following a hashtag puts every public post carrying it into your home timeline, which is how you build a feed on a network with no algorithm. Neither existing Mastodon MCP server exposes this.

Follow a hashtag, so every public post carrying it appears in your home timeline. The main way to build a feed on Mastodon.

Stop a hashtag's posts appearing in your home timeline.

Accounts that have opted into being discoverable, newest or most recently active first. Scoped to your own instance unless you ask for the wider network. A way to find people on a network with no recommendation engine.

Accounts the instance suggests you follow, with the reason for each suggestion.

Direct conversations, newest first, each with its participants and last message. Mastodon direct messages are statuses with visibility 'direct', not a separate inbox, so anyone mentioned in one can see it. Neither existing Mastodon MCP server exposes conversations at all.

Full profile for any account: bio, counts, the metadata fields with their verification state, and whether you follow each other. Accepts @user@instance, a bare local username, or a numeric id. Resolves accounts your instance has never seen before.

Accounts that follow a given account. Pages automatically past the 40-per-request ceiling.

Accounts a given account follows. Pages automatically.

For each account named, whether you follow them, whether they follow you, and whether either of you has muted or blocked the other. One call for a whole list: use this before a bulk follow or unfollow rather than reading each profile.

Follow an account. On a locked account this sends a follow request instead.

Stop following an account.

Hide an account from your timelines without them knowing. Private and reversible; unlike a block, they can still see and reply to you.

Stop hiding an account.

Block an account. This is visible to them, removes any follow in either direction, and hides your posts from them. Reversible, but the follows do not come back. Needs confirm: true.

Remove a block. Any follows the block severed do not come back; both sides have to follow again.

Hide every account on an entire instance and remove their followers. This is the blunt instrument for a server that is a persistent problem rather than one account. Needs confirm: true.

Lift a domain block. Followers removed by the block are not restored.

Accounts you have muted.

Accounts you have blocked.

Accounts you feature on your own profile.

Whole instances you have blocked.

Accounts waiting for you to approve their follow. Only meaningful on a locked account.

Approve or reject a pending follow request. Rejecting is silent; they are not told.

Mentions, boosts, favourites, follows, poll results and edits to posts you interacted with. Filter by type to get only the ones that need an answer: 'mention' is the one a person actually has to deal with.

The last notification and home-timeline entry you marked read, shared across every client on this account. Pass the returned id as since_id to fetch only what is new.

Record how far you have read, so the next get_notifications with since_id returns only what is new. Syncs to the web app and every other client. Affects only your own view.

Remove a single notification from the list. This is not undoable.

Delete all notifications permanently. This is not the same as marking them read, and there is no undo. Needs confirm: true.

Your curated lists. Pass a list id to get_list_timeline to read it, which is the closest thing Mastodon has to a custom feed.

Create a curated list. Add accounts to it with add_to_list.

Delete a list. The accounts on it are not affected, only the list. Needs confirm: true.

The accounts on one of your lists.

Add accounts to a list. You have to already follow an account before you can put it on a list, which is the error people hit here.

Remove accounts from a list. They are not unfollowed.

Announcements from the people who run your instance: downtime, rule changes, moderation decisions. Worth checking when something stops working.