ottoauthMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_GATEWAY_URL | No | Relay destination URL for webhook events. | |
| OTTOAUTH_BASE_URL | Yes | Base URL of the Ottoauth service. | |
| WEBHOOK_RETRY_MAX | No | Maximum number of retries (default 8). | |
| OTTOAUTH_WEBHOOK_HOST | No | Host for webhook receiver (default 127.0.0.1). | |
| OTTOAUTH_WEBHOOK_PATH | No | Path for webhook receiver (default /webhooks/ottoauth). | |
| OTTOAUTH_WEBHOOK_PORT | No | Port for webhook receiver (default 3789). | |
| WEBHOOK_RETRY_BASE_MS | No | Base retry delay in milliseconds (default 2000). | |
| OTTOAUTH_WEBHOOK_SECRET | No | Secret for validating webhook signatures. Recommended for production. | |
| AGENT_GATEWAY_AUTH_TOKEN | No | Optional bearer token for gateway. | |
| WEBHOOK_EVENT_STORE_PATH | No | Path to event store file (default .ottoauth-webhook-events.json). | |
| OTTOAUTH_WEBHOOK_ALLOW_UNSIGNED | No | Set to '1' to allow unsigned webhooks (dev only). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ottoauth_http_requestA | Generic Ottoauth passthrough tool. Use this if no endpoint-specific tool matches your request. |
| ottoauth_create_accountA | Create a new Ottoauth account (agent) and return credentials, including the private key. |
| webhook_statusA | Get webhook receiver and relay status, including configured gateway and event counts. |
| webhook_list_eventsA | List received webhook events with optional status filtering and pagination. |
| webhook_get_eventB | Get a specific webhook event by id. |
| webhook_replay_eventA | Force a webhook event to be re-queued and relayed immediately to the configured gateway. |
| webhook_set_gatewayB | Update relay destination for webhook forwarding (can override env config at runtime). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.