About misskey-mcp-server
misskey-mcp-server is an unofficial MCP server for Misskey, with basic support for posting notes and retrieving a user's notes. It is for users who want to perform these actions through MCP tools; many listed API operations remain unimplemented.
Key features
- 01Post notes to Misskey
- 02Retrieve notes by user
- 03Invoke actions through MCP tools
- 04Many listed API operations remain unimplemented
Use cases
- 01Post a Misskey note through an MCP client
- 02Retrieve notes published by a specific user
MCP support
The MCP server exposes tools to post notes and retrieve user notes. Other Misskey API operations listed in the README are not implemented.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project README
misskey-mcp-server
misskey-mcp-server is an unofficial MCP (Model Context Protocol) server for Misskey.
Currently, it only has the bare minimum functionality: posting notes.
So, I would appreciate contributions (PRs) from everyone!
Features
MCP Tools Implementation Status
| MCP Tool Name | Misskey API Endpoint | Status |
|---|---|---|
| post_misskey_note | /notes/create | ✅ |
| get_misskey_note | /notes/show | ❌ |
| get_misskey_timeline | /notes/timeline | ❌ |
| get_misskey_user | /users/show | ❌ |
| get_misskey_user_notes | /users/notes | ✅ |
| get_misskey_user_following | /users/following | ❌ |
| get_misskey_user_followers | /users/followers | ❌ |
| get_misskey_notifications | /i/notifications | ❌ |
| get_misskey_mentions | /notes/mentions | ❌ |
| get_misskey_antenna | /antennas/show | ❌ |
| get_misskey_antenna_notes | /antennas/notes | ❌ |
| get_misskey_channel | /channels/show | ❌ |
| get_misskey_channel_notes | /channels/notes | ❌ |
| get_misskey_gallery | /gallery/posts/show | ❌ |
| get_misskey_gallery_posts | /gallery/posts | ❌ |
| get_misskey_page | /pages/show | ❌ |
| get_misskey_drive_files | /drive/files | ❌ |
| post_misskey_reaction | /notes/reactions/create | ❌ |
| delete_misskey_reaction | /notes/reactions/delete | ❌ |
| post_misskey_follow | /following/create | ❌ |
| delete_misskey_follow | /following/delete | ❌ |
| post_misskey_renote | /notes/create (renote) | ❌ |
| post_misskey_reply | /notes/create (reply) | ❌ |
| get_misskey_search | /notes/search | ❌ |
| get_misskey_search_by_tag | /notes/search-by-tag | ❌ |
| get_misskey_hashtags | /hashtags/trend | ❌ |
| get_misskey_emoji | /emojis | ❌ |
| get_misskey_meta | /meta | ❌ |
| get_misskey_instance | /federation/instances | ❌ |
| get_misskey_stats | /stats | ❌ |
Usage
Install
From go install
GOBIN="$HOME/go/bin" go install github.com/ganyariya/misskey-mcp-server/cmd/misskey-mcp-server@latest
Build your own
git clone https://github.com/ganyariya/misskey-mcp-server
cd misskey-mcp-server
go build -o misskey-mcp-server cmd/misskey-mcp-server/main.go
Setup
Setup your mcp.json as below.
{
"mcpServers": {
"misskey-mcp-server": {
"command": "misskey-mcp-server",
"args": [],
"env": {
// https://misskey-hub.net/ja/docs/for-developers/api/token/
"MISSKEY_API_TOKEN": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
// http or https
"MISSKEY_PROTOCOL": "https",
// your misskey server's domain
"MISSKEY_DOMAIN": "misskey.io",
"MISSKEY_PATH": ""
},
"disabled": false,
"autoApprove": []
}
}
}
Thanks to reference
- MCP Go Implementation
- MCP Server References
- Misskey Go API SDK
get_misskey_user_notes
Retrieves notes for a specific Misskey user.
Arguments:
userId(string, required): The ID of the user whose notes you want to retrieve.
Example Request:
{
"userId": "some_user_id"
}
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.