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.zipInstalls 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 connectionsKey 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
When to use context-configure
- →Setting up MCP server auth
- →Testing server connectivity
- →Securing API tokens for development
About this skill
For each installed MCP server that requires authentication, guide the user through credential setup.
Process
For each server that needs auth:
-
Explain what credentials are needed:
- "The Atlassian MCP server needs your Jira instance URL and an API token"
- Link to the vendor's token creation page if possible
-
Ask where to store credentials (use
ask_user):- Environment variable (recommended for local dev)
.envfile (gitignored, local only)- Azure Key Vault (enterprise)
- System keychain (macOS Keychain / Windows Credential Manager)
- If an org catalog specifies
credential-storage, default to that
-
Guide setup based on their choice:
- Env var: tell them which variable name to set and the export command
- .env: create or update .env file, ensure it's in .gitignore
- Key Vault: provide az keyvault commands
- Keychain: provide platform-specific instructions
-
Update .mcp.json if the server needs env vars in its config:
"env": { "JIRA_URL": "${JIRA_URL}", "JIRA_TOKEN": "${JIRA_TOKEN}" } -
Test the connection if possible:
- Try to invoke a simple read-only tool from the server
- Report: ✅ Connected or ❌ Auth failed — check credentials
Important
- We NEVER store credentials directly — only configure where they go
- Never echo or log credential values
- Always ensure .env is in .gitignore before writing to it
- Respect org credential storage policy if one exists
Then mark this phase done:
UPDATE todos SET status = 'done' WHERE id = 'ctx-configure';
When all servers are configured, summarise the auth setup and move to Phase 7 (Healthcheck) — do NOT offer to commit here. Committing happens in Phase 10 (Feedback).
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.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| context-configure (this skill) | 0 | 3mo | Review | Beginner |
| 1password | 27 | 3mo | Review | Intermediate |
| security-compliance | 19 | 7mo | Review | Advanced |
| information-security-manager-iso27001 | 11 | 8mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by suuus
View all by suuus →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.
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.
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.
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".
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.
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.