Skip to content
Skills Library
AI & agents · Tool integration

dev-mcp-setup

/dev-mcp-setup

Configure MCP servers for the workspace — web search, filesystem, GitHub, Stripe, etc. Use when adding a new integration that needs MCP-level access.

Repository
evo-nexus ↗
Licence
Apache-2.0
Last repository change
12.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.05.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Configure MCP servers for the workspace — web search, filesystem, GitHub, Stripe, etc. Use when adding a new integration that needs MCP-level access.

Original author description

Configure MCP servers for the workspace — web search, filesystem, GitHub, Stripe, etc. Use when adding a new integration that needs MCP-level access.

How it works

  1. Use When
  2. Do Not Use When
  3. EvoNexus Standard MCPs
  4. Workflow
  5. Configuration Example
  6. Diagnostics
  7. Pairs With
Original SKILL.md headings · 69 lines, 346 words
SKILL.md preview
---
name: dev-mcp-setup
description: Configure MCP servers for the workspace — web search, filesystem, GitHub, Stripe, etc. Use when adding a new integration that needs MCP-level access.
---

# Dev MCP Setup

Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.

Configure MCP (Model Context Protocol) servers for the workspace. When a new integration needs access at the MCP layer (rather than via skill-level API calls), this skill walks through the configuration.

## Use When
- Adding a new MCP-backed integration (web search, GitHub, Notion, etc.)
- Diagnosing why an existing MCP server isn't responding
- Setting up a fresh EvoNexus workspace with all standard MCPs

## Do Not Use When
- The integration is API-based (use the appropriate `int-*` skill instead)
- You just need to invoke an existing MCP tool (just use it)

## EvoNexus Standard MCPs

These are typically configured in `~/.claude/settings.json` or `.claude/settings.json`:

| MCP | Purpose | Setup |
|---|---|---|
| google-calendar | Calendar events | OAuth |
| gmail | Email read/send | OAuth |
| linear-server | Linear issues/projects | API key |
| github | GitHub PRs/issues/files | GitHub token |
| canva | Design files | OAuth |
| claude_ai_Notion | Notion pages | OAuth |
| computer-use | Desktop control | local |
| figma | Design files | OAuth |
| plugin_telegram | Telegram bot | bot token |

## Workflow

1. **Identify** which MCP server you need to add
2. **Check current config** — read `.claude/settings.json` (project) or `~/.claude/settings.json` (user)
3. **Add the server entry** with its required env vars or auth
4. **Restart Claude Code** to load the new MCP
5. **Verify** by listing tools — the new MCP's tools should appear with `mcp__<server>__*` prefix
6. **Document** the addition in `workspace/development/research/[C]mcp-setup-{server}-{date}.md`

## Configuration Example

```json
{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_TOKEN": "${GITHUB_TOKEN}"
      }
    }
  }
}
```

## Diagnostics

If an MCP isn't working:
1. Check Claude Code logs for spawn errors
2. Verify env vars are set
3. Test the MCP server independently if possible
4. Check that the MCP package is installed

## Pairs With
- `update-config` (built-in skill for settings.json edits)
- `@scout-explorer` (to find existing MCP configurations)

Versions

The database has no other skills named dev-mcp-setup.

Database snapshot: 13.11.2026 · package version 1d534e3f5b7e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90configure-mcp
    Check and configure MCP servers for project integration. Use when setting up MCP servers, checking MCP status, or adding new servers to a project.
  • 100mcp-setup
    Configure MCP servers and integrations. Use for "setup MCP", "configure server", and "MCP integration".
  • 84github-setup
    Set up GitHub MCP server authentication. Use when user says "setup github", "configure github token", "github mcp setup", or needs help configuring their GitHub Personal Access Token for the GitHub MCP server.
  • 100aws-mcp-setup
    Configure AWS MCP servers for documentation search and API access. Use when setting up AWS MCP, configuring AWS documentation tools, troubleshooting MCP connectivity, or when user mentions aws-mcp, awsdocs, uvx setup, or MCP server configuration.
  • 100aws-mcp-setup
    Configure AWS MCP servers for documentation search and API access. Use when setting up AWS MCP, configuring AWS documentation tools, troubleshooting MCP connectivity, or when user mentions aws-mcp, awsdocs, uvx setup, or MCP server configuration.
  • 100mcporter-setup
    Install MCPorter and configure MCP servers from scratch. Use when setting up MCP integration for the first time, adding new MCP servers, or troubleshooting MCP connectivity. Handles installation, configuration, secrets management, and connection testing.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.