Agent-Native Calendar
by BuilderIO
Agent-Native Google Calendar - manage events, sync, and public booking
Runs in the cloud★ 7,620MITUpdated 2 months ago
Install
Sezzlee OpenAPI
Overview
Description from the maker (original English)
Expose an OpenAPI document to agents as a search-first tool catalog over your existing API.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Docs, sheets & office work
- You need to fill in: SEZZLEE_OPENAPI_CONFIG
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
SEZZLEE_OPENAPI_CONFIG
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"openapi": {
"command": "npx",
"args": [
"-y",
"@sezzlee/openapi-mcp"
],
"env": {
"SEZZLEE_OPENAPI_CONFIG": "your-value"
}
}
}
}Run this in your terminal
claude mcp add openapi --env SEZZLEE_OPENAPI_CONFIG=your-value -- npx -y @sezzlee/openapi-mcpFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"openapi": {
"command": "npx",
"args": [
"-y",
"@sezzlee/openapi-mcp"
],
"env": {
"SEZZLEE_OPENAPI_CONFIG": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"openapi": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sezzlee/openapi-mcp"
],
"env": {
"SEZZLEE_OPENAPI_CONFIG": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- Path to the server config file
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account sezzlee, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Docs, sheets & office worki
- More stars than 0% of the other 2169 servers in this category
- Published to the registry more recently than 58% of the other 2169 servers in this category
- Basic checks equal to or better than 100% of the other 2169 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Sezzlee OpenAPI safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: SEZZLEE_OPENAPI_CONFIG
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 22 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Excel MCP Server
by haris-musa
Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.
Runs on your computer★ 4,276MITUpdated 5 days ago
Install
MCP Server for Excel
by sbroenne
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
Runs on your computer★ 847MITUpdated 3 days ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
@sezzlee/openapi-mcp
MCP server that exposes an OpenAPI (Swagger 2.0 / OpenAPI 3.0–3.2) document as sezzlee's search-first tool catalog — search_tools, load_tool, invoke_tool, read_result — over a remote backend, calling it with fetch.
Status:
1.0.0, stable. Install withnpm install -g @sezzlee/openapi-mcpor run it with
npx -y @sezzlee/openapi-mcp; the binary issezzlee-openapi.
How this differs from the embedded SDK
The NestJS SDK sits inside your backend process: it discovers endpoints from your own controllers/routes and replay each MCP call through your existing pipeline, so your authentication and authorization run exactly as they do today.
openapi-mcp is a separate service. It has no access to a backend's process or pipeline — it reads the backend's OpenAPI document to learn what operations exist (the ingestion rules), and calls the backend over the network for every invocation, attaching a credential it resolves itself (how a credential is chosen and written). This is the only path for a backend that has no embedded SDK integrated into it.
Everything an embedded SDK declares in code, a document declares in one x-sezzlee extension per operation, and a host that cannot edit the document declares under operations in this config: selection, tool name, prefix, behaviour hints, argument curation, variants, families, search terms and revisions (the x-sezzlee extension). A backend that routes many capabilities through one endpoint (POST /Rest/InvokeDynamicMethod/{methodId}) lists them in that operation's x-sezzlee.family; each member becomes its own tool, with its own name, description and body, and the dispatch key stays hidden.
Quick start
The server reads its configuration from the file named by SEZZLEE_OPENAPI_CONFIG. Build the package first (this repository never runs @sezzlee/core's consumers against a stale dist):
pnpm turbo run build --filter=@sezzlee/openapi-mcpA minimal config — a local document, opt-in selection so at least one operation is exposed, default stdio transport:
{"source": "./openapi.json", "selection": { "default": "include" } }
SEZZLEE_OPENAPI_CONFIG=/absolute/path/to/config.json node packages/servers/openapi-mcp/dist/cli.jssource is either a path (resolved relative to the config file's own directory) or an http(s):// URL. On startup the server ingests the document, builds the catalog, prints a one-line-per-diagnostic-code summary to stderr, and then serves stdio or listens for streamable HTTP, depending on transport.kind.
A config that fails validation, or that names an environment variable that is not set, stops the process with a message on stderr and exit code 2. A document that ingests with a fatal diagnostic, or a catalog with a fatal diagnostic (name_collision, invalid_name, ambiguous_selection, …), stops it with exit code 1.
Configuration
All keys below are read from the SEZZLEE_OPENAPI_CONFIG JSON file and validated with a zod schema (src/platform/config.ts) that rejects unknown keys.
| Key | Type | Default | Notes | |
|---|---|---|---|---|
transport.kind | "stdio" \ | "http" | "stdio" | — |
transport.host | string (http only) | "127.0.0.1" | Must stay loopback (127.0.0.1, ::1, localhost) unless tokenExchange is configured — see below | |
transport.port | int, 0–65535 (http only) | 8787 | — | |
transport.path | string starting with / (http only) | "/mcp" | — | |
transport.resource | url (http only) | required | The OAuth protected-resource identifier advertised at /.well-known/oauth-protected-resource | |
transport.authorizationServers | array of url, min 1 (http only) | required | — | |
transport.allowedHostnames | array of string (http only) | [] | Extra Host header values accepted, on top of the localhost defaults | |
tokenExchange | object | not configured | RFC 8693 token exchange; required for an http transport to authenticate a caller (see Rules) | |
tokenExchange.tokenEndpoint | url | required | — | |
tokenExchange.clientId | string | required | — | |
tokenExchange.clientSecret | { fromEnv: string } | required | — | |
tokenExchange.clientAuth | "basic" \ | "post" | "basic" | client_secret_basic or client_secret_post |
tokenExchange.audience | string | not sent | — | |
tokenExchange.resource | url | not sent | — | |
tokenExchange.scope | string | not sent | — | |
tokenExchange.schemes | array of string, min 1 | required | The security scheme names the exchanged token satisfies | |
source | string, non-empty | required | A local file path (relative to the config file) or an http(s):// URL to the OpenAPI document | |
reload.intervalSeconds | integer ≥ 10 | not set | Re-reads source this often, plus up to 10% jitter. Conditional on the last ETag/Last-Modified for an http(s) source; a body identical to the served one is ignored | |
reload.onSignal | boolean | true | SIGHUP re-reads source. Without a reload block the document is read once at startup and SIGHUP keeps its default action | |
baseUrl | url | not set | Replaces the document's root servers | |
serverVariables | record\ | not set | Overrides for the document's server variable defaults | |
hoistPathPrefix | string starting with / | not set | A leading path segment moved from every route into the base URL | |
outputSchema | "document" \ | "omit" | "document" | omit for a backend whose responses do not match its document |
requestBodyRequired | "document" \ | "always" | "document" | always treats an undeclared requestBody.required as true |
strict | boolean | false | Raises openapi_document_invalid from a warning to a fatal diagnostic | |
selection.default | "include" \ | "exclude" | "exclude" | Whether an operation is exposed when no rule matches it (opt-in by default) |
selection.rules | array of { route?, method?, decision } | [] | route/method are matched the same way the embedded SDKs match a controller route | |
operations | record\ | {} | Laid over each operation's x-sezzlee field by field; a key that names no operation is fatal. A field here may not also be set through names, searchTerms or revision.operations |
| names | record\ | {} | Overrides a tool's name; the value must match `^[a-z][a-z0-
Only the beginning is shown; read the rest in the repo