Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Description from the maker (original English)
Find the right MCP server or skill for a task: ranked, install-ready results from 50K+ servers.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://api.lookupd.com/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"lookupd": {
"command": "npx",
"args": [
"-y",
"lookupd",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add --transport http lookupd https://api.lookupd.com/mcpclaude mcp add lookupd -- npx -y lookupd mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"lookupd": {
"url": "https://api.lookupd.com/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"lookupd": {
"command": "npx",
"args": [
"-y",
"lookupd",
"mcp"
]
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"lookupd": {
"type": "http",
"url": "https://api.lookupd.com/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"lookupd": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"lookupd",
"mcp"
]
}
}
}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.
ChatGPT connects only to servers on the internet:
https://api.lookupd.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.
find_capabilityFind MCP servers that provide a capability for a task. Pass a short capability phrase (e.g. "read Linear issues"), not the user's full request. Results are ranked provisionally (no outcome evidence yet) and each includes an install snippet for the given runtime. Lookups are free.
get_entryFull details for one entry: raw server.json, install snippets for the runtime, lookupd metadata. Pass the registry name (e.g. io.github.acme/linear-mcp), or, for a server already in your MCP config, its remote url or its npm/PyPI package; that finds the registry name to use with
healthProbe status of an entry: whether its remote endpoint is up, needs a login (auth_required), is down or dead, with 7-day uptime, median latency, tool count and the last probe. Stdio-only servers are not_probeable.
report_outcomeAfter a task used an MCP server, report once per server whether it worked: servers found via lookupd in this conversation and servers already installed alike. `entry` is the registry name; for an installed server, get it from get_entry with the server's url or package (skip the r
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
The registry name was verified against the domain lookupd.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 283 ms (HTTP 200)
No sign-in needed
Read 4 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
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
Agent-Native Google Calendar - manage events, sync, and public booking
Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
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.
The registry agents call to find the right MCP server, skill or agent for a task. Free to look up. Neutral: lookupd never hosts or proxies tool calls, and rank is never for sale. Rankings are *provisional* until real outcome evidence exists.
This repository holds everything an agent installs:
lookupd on npm: the CLI and the npx lookupd mcp stdio bridge to the lookupd APIskills/find-capability: the skill that teaches an agent the find → approve → install → report loopThe API, crawler and ranking live in a private repository. Data: Official MCP Registry (CC0), mirrored and enriched by lookupd; lookupd is not affiliated with the MCP project.
Claude Code (plugin: skill + MCP tools):
/plugin marketplace add lookupd/lookupd
/plugin install lookupd@lookupd
Any agent that reads skills (skills.sh):
npx skills add lookupd/lookupd
MCP only, any client that launches stdio servers:
claude mcp add lookupd -- npx -y lookupd@latest mcp
.vscode/mcp.json:
{ "servers": { "lookupd": { "command": "npx", "args": ["-y", "lookupd@latest", "mcp"] } } }
.cursor/mcp.json / Claude Desktop:
{ "mcpServers": { "lookupd": { "command": "npx", "args": ["-y", "lookupd@latest", "mcp"] } } }
Remote endpoint, for clients that connect to streamable HTTP directly: https://api.lookupd.com/mcp.
| tool | what it does |
|---|---|
find_capability | { task, runtime?, max_results? } → ranked candidates with paste-ready install snippets |
get_entry | full details for one entry by registry name |
health | registry status and last-seen time (live probes coming) |
report_outcome | structured outcome report; only exposed after lookupd telemetry on |
npx lookupd find "read Linear issues" --runtime claude-code
npx lookupd find "pdf extraction" --json npx lookupd telemetry on|off|status npx lookupd login --key lk_... # optional API key npx lookupd mcp # stdio bridge (what the plugin runs)
Environment: LOOKUPD_API_URL (default https://api.lookupd.com), XDG_CONFIG_HOME. Config lives at ~/.config/lookupd/config.json.
Off by default. When you run lookupd telemetry on, the agent can call report_outcome after using a server it found through lookupd. A report contains only: the entry name, success, a latency bucket, your runtime, a capability tag from a fixed list, and an error class. Never prompts, task text, file paths or output. Lookups themselves are free and unauthenticated; the search phrase is stored truncated to 160 characters as anonymous demand data. Policy: https://lookupd.com/telemetry
pnpm install
pnpm test # vitest: bridge, CLI, API client, config, manifests pnpm build # tsup → dist/cli.js claude plugin validate .
Local end-to-end against a dev API: LOOKUPD_API_URL=http://localhost:3000 npx lookupd find "linear", and in Claude Code /plugin marketplace add /path/to/this/repo.
MIT. See LICENSE.