CO

context-configure

Guide the user through authentication setup and connection testing for MCP servers.

Install

mkdir -p .claude/skills/context-configure && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15230" && unzip -o skill.zip -d .claude/skills/context-configure && rm skill.zip

Installs to .claude/skills/context-configure

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Guide the user through authentication setup for each MCP server, test connections
81 charsno explicit “when” trigger
Beginner

Key capabilities

  • →Explain required credentials for each MCP server
  • →Ask where to store credentials (env var, .env file, Azure Key Vault, system keychain)
  • →Guide credential setup based on user's storage choice
  • →Update `.mcp.json` with environment variables if needed
  • →Test the connection to the MCP server
  • →Summarize authentication setup for all configured servers

How it works

The skill guides the user through credential setup for each MCP server, offering storage options and providing instructions for each choice, then tests the connection.

Inputs & outputs

You give it
User's choice for credential storage and server authentication details
You get back
Configured MCP server authentication and a connection test report

When to use context-configure

  • →Setting up MCP server auth
  • →Testing server connectivity
  • →Securing API tokens for development

About this skill

Configure auth only for MCP servers already present in .mcp.json.

Steps

  1. Read .mcp.json. If missing, report that no installed MCP servers can be configured and stop.
  2. Determine which servers need auth from known requirements, existing env placeholders, or vendor docs. Skip no-auth servers; if none remain, report that and stop.
  3. Explain needed credential names and token-source links when known; otherwise point to vendor docs.
  4. Ask with ask_user where to store credentials. Default to org policy when present; otherwise prefer shell env vars. If unavailable, ask for another option.
  5. Configure references only: export commands, gitignored .env placeholders, Key Vault/keychain commands, and .mcp.json entries like "JIRA_TOKEN": "${JIRA_TOKEN}".
  6. Test one lightweight read-only operation per configured server. On failure, report auth failed, ask whether to retry setup once or leave it for healthcheck, and do not mark it connected.
  7. Summarize configured, skipped, and failed servers. Standalone runs stop there. If context-wizard invoked this skill and its todo exists, mark it done and continue to context-healthcheck.

Examples

  • "Set up Jira MCP auth" -> ask storage, add env refs, test read-only.
  • "401 after setup" -> offer one retry or healthcheck handoff.

Error handling and safety

Never store or echo secrets. Before editing .env, confirm .gitignore excludes .env and .env.*; add those ignore rules first if missing.

When not to use it

  • →When not configuring authentication for MCP servers
  • →When not testing connections to MCP servers

Limitations

  • →The skill never stores credentials directly
  • →The skill does not echo or log credential values
  • →The skill requires `.env` files to be in `.gitignore` before writing to them

How it compares

It provides a structured, interactive process for securing and configuring MCP server credentials, unlike manual configuration that lacks guided storage options and connection testing.

Compared to similar skills

context-configure side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
context-configure (this skill)06moReviewBeginner
1password276moReviewIntermediate
security-compliance1911moReviewAdvanced
information-security-manager-iso270011111moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

1password

openclaw

Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.

2799

security-compliance

davila7

Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.

1981

information-security-manager-iso27001

davila7

Senior Information Security Manager specializing in ISO 27001 and ISO 27002 implementation for HealthTech and MedTech companies. Provides ISMS implementation, cybersecurity risk assessment, security controls management, and compliance oversight. Use for ISMS design, security risk assessments, control implementation, and ISO 27001 certification activities.

1169

cursor-sso-integration

jeremylongshore

Configure SSO and enterprise authentication in Cursor. Triggers on "cursor sso", "cursor saml", "cursor oauth", "enterprise cursor auth", "cursor okta". Use when working with cursor sso integration functionality. Trigger with phrases like "cursor sso integration", "cursor integration", "cursor".

433

springboot-security

affaan-m

Spring Security best practices for authn/authz, validation, CSRF, secrets, headers, rate limiting, and dependency security in Java Spring Boot services.

529

auth-patterns

davepoon

This skill should be used when the user asks about "authentication in Next.js", "NextAuth", "Auth.js", "middleware auth", "protected routes", "session management", "JWT", "login flow", or needs guidance on implementing authentication and authorization in Next.js applications.

720

Search skills

Search the agent skills registry