ClawHub

Notion MCP

v1.0.0

Notion MCP integration with managed authentication. Query databases, create and update pages, manage blocks. Use this skill when users want to interact with...

⭐ 0· 345·3 current·3 all-time
by@byungkyu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
✓
Purpose & Capability
The name/description (Notion MCP via managed authentication) aligns with the runtime instructions: all example calls target Maton endpoints (gateway.maton.ai, ctrl.maton.ai) and require a MATON_API_KEY. The included JSON schemas correspond to the Notion MCP operations described (search, fetch, create/update pages, comments, teams, users, etc.), so the declared capability matches requested resources.
ℹ
Instruction Scope
The SKILL.md instructs the agent to POST user queries and page/content payloads to Maton-managed endpoints and to send the MATON_API_KEY in Authorization headers. That is expected for a managed-proxy integration, but it does mean workspace content, metadata, and actions are transmitted to a third party (Maton). The instructions do not ask for unrelated files, system paths, or other environment variables.
✓
Install Mechanism
No install spec and no code files (instruction-only). Nothing will be written to disk or pulled from external installers by the skill itself, which minimizes installation risk.
✓
Credentials
Only one environment variable is required (MATON_API_KEY), which directly matches the documented authentication method. No unrelated credentials or secret paths are requested. This is proportionate for a managed-proxy Notion integration.
✓
Persistence & Privilege
The skill is not flagged as always:true and has no install actions that change agent/system configuration. It can be invoked autonomously (the platform default), which is normal — there are no additional persistent privileges requested by the skill itself.
Assessment
This skill is coherent for a Notion MCP proxy: it will send Notion queries and content to Maton endpoints and requires a MATON_API_KEY. Before installing or providing a key, verify the Maton service is trustworthy for your data: confirm the maton.ai domains, review Maton's privacy/security policy and the scope of the API key you obtain, store the key securely, and prefer least-privilege (use scoped keys or ephemeral credentials if available). If you prefer not to route data through a third party, use a direct Notion REST API skill instead. Finally, because this is instruction-only (no install), there is low disk/installation risk, but the primary exposure is networked data leaving your environment to Maton.

Like a lobster shell, security has layers — review code before you run it.

latestvk971v26tt8stt7yxy49z1n7g7h826z1p

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🧠 Clawdis
EnvMATON_API_KEY

Comments