ottoauthMCP
Provides tools for interacting with the Ottoauth authentication service, including account creation, generic HTTP requests, and webhook event handling for automated workflows.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ottoauthMCP create a new account with email test@example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ottoauthMCP
Standalone MCP stdio server that proxies tool calls to Ottoauth HTTP endpoints.
Features
Discovers service endpoints from
GET /api/servicesdocs.Registers dynamic MCP tools per endpoint.
Refreshes discovered tools once every hour.
Includes a generic passthrough tool:
ottoauth_http_request.Includes a built-in account creation tool:
ottoauth_create_account.Runs an Ottoauth webhook receiver and relays incoming events to an agent gateway with retries.
Related MCP server: SentinelX Core MCP
Run
npm install
OTTOAUTH_BASE_URL=http://localhost:3000 npm startWebhook receiver defaults:
host:
127.0.0.1port:
3789path:
/webhooks/ottoauth
Important env vars:
OTTOAUTH_WEBHOOK_SECRET(recommended; validatesx-ottoauth-signature)OTTOAUTH_WEBHOOK_ALLOW_UNSIGNED=1(dev only)OTTOAUTH_WEBHOOK_PORT/OTTOAUTH_WEBHOOK_HOST/OTTOAUTH_WEBHOOK_PATHAGENT_GATEWAY_URL(relay destination)AGENT_GATEWAY_AUTH_TOKEN(optional bearer token to gateway)WEBHOOK_RETRY_BASE_MS(default2000)WEBHOOK_RETRY_MAX(default8)WEBHOOK_EVENT_STORE_PATH(defaults to.ottoauth-webhook-events.jsonin cwd)
Tests
npm testTest coverage includes:
parser and normalization edge cases
timeout and forwarding behavior
webhook signature, dedupe, retries, dead-letter
MCP stdio end-to-end flow
integration test using simple demo agent script from neighboring
autoauthrepo
MCP client config example
{
"mcpServers": {
"ottoauth": {
"command": "node",
"args": ["/absolute/path/to/ottoauthMCP/src/index.mjs"],
"env": {
"OTTOAUTH_BASE_URL": "https://your-ottoauth-domain.com"
}
}
}
}Available Tools
7 toolsottoauth_create_accountOttoauth Create AccountA
Create a new Ottoauth account (agent) and return credentials, including the private key.
Inputs: username (required), description, callback_url.
ottoauth_http_requestOttoauth HTTP RequestA
Generic Ottoauth passthrough tool. Use this if no endpoint-specific tool matches your request.
Inputs: path (required), method (required), body, query, +1 more.
webhook_get_eventWebhook Get EventB
Get a specific webhook event by id.
Inputs: event_id (required).
webhook_list_eventsWebhook List EventsA
List received webhook events with optional status filtering and pagination.
Inputs: limit, offset, status.
webhook_replay_eventWebhook Replay EventA
Force a webhook event to be re-queued and relayed immediately to the configured gateway.
Inputs: event_id (required).
webhook_set_gatewayWebhook Set GatewayB
Update relay destination for webhook forwarding (can override env config at runtime).
Inputs: gateway_url, gateway_auth_token.
webhook_statusWebhook StatusA
Get webhook receiver and relay status, including configured gateway and event counts.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
The webhook-specific tools are clearly distinct in purpose, and the generic passthrough tool explicitly defers to endpoint-specific tools. However, webhook_status and webhook_list_events both involve event counts/status, which could cause some initial confusion.
Most tools use snake_case with a domain prefix, but the pattern is inconsistent: some are verb-first (ottoauth_create_account), some are noun-phrases (webhook_status), and ottoauth_http_request breaks the verb_noun convention. The mixed prefixes make the set feel less uniform.
Seven tools is a well-scoped size for this server. Each tool covers a meaningful operation without redundancy, and the generic passthrough fills edge cases without bloating the surface.
The webhook event lifecycle is well covered with list, get, replay, and gateway configuration, plus account creation. Minor gaps exist such as no explicit account deletion or webhook clearing, but the generic HTTP passthrough mitigates dead ends.
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for toolhouse.ai. This does not rely on an external llm unlike the official server.4MIT
- AlicenseNot gradedqualityFmaintenanceAn MCP server that proxies tool calls to a running SentinelX Core instance with OIDC/OAuth authentication. It enables secure integration of SentinelX Core's HTTP agent capabilities through the MCP protocol.1MIT
- AlicenseNot gradedqualityDmaintenanceA production-grade MCP server designed for multi-tenant, authenticated, and observable AI agent systems, enabling secure tool execution across heterogeneous data sources.68MIT
- FlicenseNot gradedqualityDmaintenanceA standalone MCP server that exposes API endpoints as tools for AI assistants, using SSE transport.-