Sign inSign up

jfeeneydemo3/dubjug-notion-context-kit:1.0.0

Multi-platform
Manifest digest

sha256:7372ee9432691d55c489b111a26307652e176b27980bea330b588381d64731ee

Last pushed

11 days by jfeeneydemo3

Type

Sandbox Kit

Manifest digest

sha256:7372ee9432691d55c489b111a26307652e176b27980bea330b588381d64731ee

yaml
schemaVersion: "3"
displayName: Notion guidance (MCP gateway)
description: Rules for an agent that reaches the hosted Notion MCP server through the sandbox MCP gateway. Carries no network rule, credential or MCP registration.
version: 1.0.0
kind: mixin
capabilities:
    - type: com.docker.sandbox/lifecycle@1
      config:
        install:
            - command: |
                export HOME="${HOME:-/home/agent}"
                export PATH="$HOME/.local/bin:$HOME/.claude/local:/usr/local/share/npm-global/bin:${PATH:-/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin}"
                add_block() {
                  f="$1"
                  mkdir -p "$(dirname "$f")"
                  touch "$f"
                  grep -q 'notion-gateway:start' "$f" && return 0
                  cat >> "$f" <<'NOTION_BLOCK'

                <!-- notion-gateway:start -->
                ## Notion (via the sandbox MCP gateway)

                - Notion tools reach you through the `mcp-gateway` MCP server; their names all start
                  with `notion-` (for example `notion-search`, `notion-fetch`; Codex shows them as
                  `mcp__mcp_gateway__notion_search`). There is no separate `notion` server and no
                  credential in this sandbox. Use only those tools for Notion: never call the Notion
                  API directly and never look for tokens.
                - Read before you write: search or fetch first. Create, update, move, delete or
                  restore Notion content only when the user asked for that change, and say what you
                  changed. Do not use the Notion Calendar (`notion-calendar-*`) or Custom Agent
                  session tools unless the user asks for them.
                - Never call `notion-revoke-auth`.
                - On a 401, a 403 or "not authorized": if a `notion-authorize` tool is offered, call
                  it once and retry; otherwise, or if it still fails, stop and report the exact
                  message so the user can re-authorize Notion on the host.
                <!-- notion-gateway:end -->
                NOTION_BLOCK
                }
                command -v codex >/dev/null 2>&1 || [ -d "$HOME/.codex" ] && add_block "$HOME/.codex/AGENTS.md"
                command -v claude >/dev/null 2>&1 || [ -d "$HOME/.claude" ] && add_block "$HOME/.claude/CLAUDE.md"
                exit 0
              description: Add gateway-era Notion rules to the agent's always-loaded instructions
              env:
                - HOME
                - PATH
              user: agent
    - type: com.docker.sandbox/agent-context@1
      config:
        content: |
            ## Notion

            The Notion MCP server is registered on the host's sandbox MCP gateway and
            authorized there with OAuth. Its tools reach you through the `mcp-gateway`
            MCP server, and all of their names start with `notion-`. There is no
            `notion` entry in your own MCP configuration and no Notion credential in
            this environment.

            - Use only the gateway's `notion-*` tools for Notion. Do not call the
              Notion API directly, and do not look for credentials.
            - Read before you write. Change Notion content (create, update, move,
              delete, restore, comment) only when the user asked for that change, and
              report what you changed. Leave Notion Calendar and Custom Agent session
              tools alone unless asked.
            - Never call `notion-revoke-auth`.
            - On 401, 403 or "not authorized": call `notion-authorize` once and retry if
              the gateway offers it; otherwise, or if it still fails, stop and report
              the exact message so the user can re-authorize Notion on the host.