misskey-mcp-server

An unofficial MCP server for Misskey that currently implements only a minimal subset of MCP tools—primarily posting notes (e.g., `post_misskey_note`) and `get_misskey_user_notes`; most other listed tools are unimplemented.

Evaluated Apr 04, 2026 (16d ago)

Repo ↗ Communication mcp misskey go agent-tools social-media notes

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Uses a Misskey API token provided via environment variable (better than hardcoding). However, the README does not specify how requests/errors are logged, whether secrets are redacted, or how token permissions are scoped. It also allows configuring protocol as `http or https`, so TLS enforcement depends on user configuration; no security hardening details are documented.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want a small, focused MCP bridge that can post notes to Misskey via an MCP workflow, and you only need the currently supported tools.

Avoid When

You need read-heavy or full-feature Misskey capabilities (timeline, search, reactions/follows/renotes/replies) or well-defined operational semantics (pagination, retries, error handling) for autonomous agents.

Use Cases

• Use an MCP-capable agent to create Misskey notes (toots) on a connected Misskey instance.
• Fetch notes for a specific Misskey user (limited to `get_misskey_user_notes`).

Not For

• Comprehensive Misskey automation (timeline, profiles, followers/following, notifications, search, etc.)—many tools are marked as not implemented.
• Production-grade reliability expectations until tool coverage and operational guidance are improved.

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: Misskey API token via env var (MISSKEY_API_TOKEN)

OAuth: No Scopes: No

Authentication to Misskey appears to be done via a single API token. The README does not describe fine-grained scopes or how permissions map to specific MCP tools.

Pricing

Free tier: No

Requires CC: No

No pricing information provided; repository appears to be a self-hosted open-source tool.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Tool coverage is very limited (only posting notes and a single read tool are marked as implemented).
⚠ No stated pagination conventions or retry/idempotency guidance in the README.
⚠ Because it’s unofficial and minimal, agent workflows that assume broader Misskey functionality will likely fail or be unavailable.

Alternatives

Use the Misskey REST API directly with your own small MCP/agent wrapper (or existing MCP templates). Other Misskey integration projects/SDKs (e.g., go-misskey) invoked from your own tooling. A different MCP server with broader Misskey tool coverage, if available.

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for misskey-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.