SezzleOps MCP
by onatozmenn
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEZZLE_ENV | No | Environment: sandbox or production. | sandbox |
| MCP_HTTP_HOST | No | Host for HTTP transport. | 127.0.0.1 |
| MCP_HTTP_PORT | No | Port for HTTP transport. | 3000 |
| MCP_TRANSPORT | No | Transport: stdio or http. | stdio |
| SEZZLE_API_KEY | No | Your Sezzle API public key. Required for production. | |
| SEZZLE_READ_ONLY | No | If true, mutation tools are not registered. | true |
| SEZZLE_API_SECRET | No | Your Sezzle API private key. Required for production. | |
| MCP_HTTP_AUTH_TOKEN | No | Bearer token for non-loopback HTTP bind. Required if binding to non-loopback address. | |
| SEZZLE_API_BASE_URL | No | Base URL for Sezzle API. Default for sandbox: https://sandbox.gateway.sezzle.com, for production: https://gateway.sezzle.com. | |
| SEZZLE_MERCHANT_UUID | No | Your Sezzle merchant UUID. Required for production. | |
| SEZZLE_WEBHOOK_SECRET | No | Your Sezzle webhook signing secret for HMAC-SHA256 verification. | |
| MCP_HTTP_ALLOWED_HOSTS | No | Allowed hosts for non-loopback HTTP bind. Required if binding to non-loopback address. | |
| MCP_HTTP_ALLOWED_ORIGINS | No | Allowed origins for non-loopback HTTP bind. Required if binding to non-loopback address. | |
| SEZZLE_PERMISSION_PROFILE | No | Permission profile: read, finance, webhooks, support, or admin. | read |
| SEZZLE_REQUIRE_CONFIRMATION | No | If true, mutations require explicit confirmation with preview_id. | true |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/onatozmenn/sezzle-merchant-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server