MCP setup wizard

Connect the Jymni MCP server to your agent.

One tool call turns a proposed action into a practical, structured next step—before your agent acts.

Get an MCP token

Add Jymni to your MCP client Save your token as JYMNI_API_KEY, then paste this configuration.

{
  "mcpServers": {
    "jymni": {
      "type": "streamable-http",
      "url": "https://www.jymni.com/mcp",
      "headers": {
        "Authorization": "Bearer ${JYMNI_API_KEY}"
      }
    }
  }
}

Connected tool: consult_ethics

Client-specific help

Tool parameters

Start with one. Add context when it helps.

Only proposed_action is required. The remaining parameters help Jymni give more specific counsel.

Required

1 parameter

proposed_actionstring: The exact action the agent is about to take or recommend.

Optional context

9 parameters

objectivestring: The goal the action should serve.
actorstring | object: The acting agent and human operator.
stakeholdersstring[]: People or groups materially affected.
known_factsstring[]: Evidence already verified.
uncertaintiesstring[]: Important unknowns or disputed claims.
constraintsstring[]: Deadlines, rules, promises, or limits.
optionsstring[]: Real alternatives the agent can consider.
contextobject: Authority, reversibility, sensitivity, domain, and stage.
idempotency_keystring: A stable key for safe retries.

Inside context: authority, reversibility, sensitivity, deployment_stage, domain, and quadrant_focus. See accepted values.

Try one sentence

Text in. A next move out.

Input consult_ethics

Publish the outage summary before the facts are verified.

Output gather_information

Verify the facts with the incident owner before publishing.

Purpose is responsible; the factual basis is incomplete.

The full response also includes safeguards, missing facts, red lines, and structured scores. Jymni advises; it does not authorize the action.