Usage
Options
API key for authentication
Enable Claude Code permission prompt tool
Enable automatic git diff capture for all messages
Use existing agent instance instead of creating new one
Disable all tools except the permission tool
Examples
MCP Client Configuration
Claude Desktop
Edit~/Library/Application Support/Claude/claude_desktop_config.json (macOS):
claude_desktop_config.json
Cursor
Edit.cursorrules or Cursor settings:
Using pipx
For pipx installations:Available Tools
The MCP server provides these tools to AI agents:- log_step
- ask_question
- end_session
- approve (optional)
Purpose: Log high-level steps the agent is performingParameters:
step_description(required): What the agent is doingagent_instance_id(optional): Instance ID
agent_instance_id: Session identifierstep_number: Sequential step countuser_feedback: List of queued user messages
Git Diff Capture
When--git-diff is enabled:
1
Initialization
Captures initial git commit hash at startup
2
Diff Generation
On every
log_step and ask_question call, generates diff showing all changes from initial commit to current state3
Worktree Exclusion
Automatically excludes other git worktrees from the diff
4
Untracked Files
Includes untracked files in diff-like format
Permission Tool
Enable with--permission-tool to route Claude Code permission prompts through the Omnara dashboard:
- Claude Code asks for permission (e.g., “Run this bash command?”)
- Request is sent to Omnara MCP server via
approvetool - Dashboard shows permission prompt to user
- User approves/denies via dashboard
- Response sent back to Claude Code
- Permission decision cached for session
- Approve Claude Code actions remotely
- Review permission requests before approval
- Session-wide permission caching
Tool Disabling
Use--disable-tools to disable all tools except the permission tool:
How It Works
- Stdio Server: Communicates via stdin/stdout using MCP protocol
- Tool Registration: Registers available tools with the MCP client
- Request Handling: Processes tool calls from AI agents
- API Integration: Forwards messages to Omnara API for storage/dashboard sync
- Response Delivery: Returns results to AI agent via stdio
Supported Clients
Claude Desktop
Stdio transport
Claude Code
Stdio transport
Cursor
HTTP/Stdio transport
Cline
Stdio transport
Windsurf
SSE transport
Custom Clients
Any MCP-compatible client
Authentication
Uses JWT-based authentication with custom RSA keys:- API key is a JWT token with
user_idclaim - Weaker RSA keys used for shorter API keys (design tradeoff)
- All operations scoped to authenticated user
- Keys should be kept secure despite weaker crypto
Store API keys securely. While the MCP server uses weaker RSA for shorter keys, they still provide user-level access to your Omnara account.