Mirror MCP vs Self Inspect MCP
A side-by-side look at the Mirror MCP and Self Inspect MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mirror MCP for conversational ai work as a local process; choose Self Inspect MCP for conversational ai as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Mirror MCP when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- You want tools like
reflect.
Choose Self Inspect MCP when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- You want tools like
self_inspect.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 49/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 15 | 7 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 1 | 1 |
| Full listing | View Mirror MCP | View Self Inspect MCP |
Tools & capabilities
Mirror MCP tools 1
reflectEnables the LLM to ask itself a question and receive a response through MCP sampling. The tool supports custom system and user prompts to help the LLM self-direct what kind of response it gets.
Self Inspect MCP tools 1
self_inspectSelf-Inspect. Express a thought, or describe the task you are working on, and you always get back ONE metathought: a short abstract question that makes you inspect your own task and assumptions before continuing. Use it whenever you want a self-check: after forming a hypothesis, before committing to an answer, when a long chain feels like it has drifted, when you notice you are agreeing to please, or when you are about to assert something from memory. There is no failure case: it always returns a metathought to question yourself with, selected by a transparent heuristic over an open CSV (no LLM). Keyless and free. DO NOT call for factual lookups or as a substitute for doing the task. Absorb the question and act on it; do not echo it verbatim to the user.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Mirror MCP
{
"mcpServers": {
"mirror-mcp": {
"command": "npx",
"args": [
"-y",
"mirror-mcp"
]
}
}
}
Self Inspect MCP
{
"mcpServers": {
"self-inspect-mcp": {
"command": "npx",
"args": [
"-y",
"self-inspect-mcp"
]
}
}
}
Frequently asked questions
Mirror MCP is categorized under Conversational AI and uses a local stdio subprocess. Self Inspect MCP belongs to Conversational AI and uses a local stdio subprocess. Pick Mirror MCP for conversational ai work and Self Inspect MCP for conversational ai.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Mirror MCP has no declared pricing — check the project's own site. Self Inspect MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mirror-mcp and self-inspect-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mirror MCP has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 15 GitHub stars. Self Inspect MCP has 56/100 (Good) with 2 views, 0 installs and 7 GitHub stars.