Muninn (munn.is)

muninn_mirror_connect

Start the connection flow for a mirror provider. Returns a URL for the user to open in their browser. After approving, call muninn_mirror_status to confirm. Paid plan. provider: 'gdrive' (Google Drive, push-only: copies out of Muninn, never back) is the working mirror; 'github' is not available yet and is refused.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "provider": "<provider>"
    },
    "name": "muninn_mirror_connect"
  }
}

Input Schema

Name	Required	Description	Default
`provider`	Yes	The mirror provider to connect: 'gdrive' for Google Drive (push-only). 'github' is not available yet and returns an error.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description discloses that the tool returns a browser URL, requires user approval, belongs to a paid plan, and that 'gdrive' is push-only with copies never coming back. It also warns that 'github' is unavailable and refused, which is important behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the action, followed by the return value, next step, prerequisite, and provider constraints. Every sentence adds operational value with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of an output schema, the description explains the key return value (a URL) and the required follow-up step. It also covers pricing, provider availability, and push-only semantics, making the definition complete enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds useful meaning beyond the schema by explaining that 'gdrive' is push-only ('copies out of Muninn, never back') and that 'github' is not available yet and is refused, though much of this overlaps with the schema's own parameter description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: 'Start the connection flow for a mirror provider.' It clearly distinguishes the tool from its follow-up sibling by stating that after approval the agent should call muninn_mirror_status to confirm.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context, including a prerequisite ('Paid plan') and an explicit follow-up ('After approving, call muninn_mirror_status to confirm'). It also states that 'github' is refused, but it does not explicitly frame when to choose this over other mirror tools such as designate or push.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Muninn (munn.is) tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?