Oauth Connector Blueprint

    1

    Add OAuth 2.0 to agent connectors the right way — PKCE, token refresh, secure storage, and provider quirks for Google, GitHub, Slack, and more.

    $8

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    About this skill

    The number-one reason agent connectors die in production is authentication done wrong: tokens in plaintext files, no refresh logic (so the integration "randomly" breaks every hour), PKCE skipped, scopes over-requested. This skill gives you a complete, provider-aware OAuth 2.0 blueprint for agent connectors: the authorization-code flow with PKCE, automatic token refresh with rotation, secure token storage, scope-minimization guidance, and the quirks of major providers (Google, GitHub, Slack, Microsoft, Notion, and others) — as copy-paste-ready code plus a security checklist.

    To produce a correct, secure OAuth 2.0 implementation for an agent connector: the full authorization flow, token lifecycle management (acquire → store → refresh → revoke), per-provider configuration, and a threat-model checklist. The output is code plus the reasoning, so the builder understands why each piece exists and does not cargo-cult it into insecurity.

    • When your agent connector needs to act as a user against a third-party API (read their Gmail, post to their Slack, access their Notion).

    • When adding "Sign in with X" to an agent-facing service or MCP server that serves multiple users.

    • When an existing connector's auth "randomly stops working" — usually expired tokens with no refresh; this skill diagnoses and fixes the lifecycle.

    • When reviewing someone else's OAuth implementation for security holes.

    • For machine-to-machine auth (service accounts, API keys) — that is simpler and covered in mcp-server-scaffolder's auth layer; do not use OAuth where an API key suffices.

    • When the provider does not support OAuth 2.0 (some legacy APIs) — the skill will tell you and suggest the provider's actual mechanism.

    • For implementing an OAuth provider (authorization server) — this skill is the client side only.

    • When you need the legal/ToS review of scopes and data handling — the skill covers the engineering; your lawyer covers the rest.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 29 days ago

    Requires

    Scaffolder MCP
    Python

    Permissions

    No special permissions declared or detected

    Listed29 days ago

    What's inside

    Frequently Asked Questions

    Add OAuth 2.0 to agent connectors the right way — PKCE, token refresh, secure storage, and provider quirks for Google, GitHub, Slack, and more.

    This skill uses the open SKILL.md standard. Use it through an MCP-compatible agent connected to Agensi, and check the compatibility information on this page for confirmed agents and required capabilities.

    Connect your AI agent to Agensi through MCP, then ask it to use oauth-connector-blueprint on your task. Your agent loads the latest approved version each time. Paid skills require a purchase or active subscription. Skill files are not available for download; your licence does not allow you to save, copy or export any part of a skill.

    New in Security