Agent skill

MCP Gateway Configuration

MCP gateway setup for multi-server integration, security configuration, tool routing, and access control

Apache-2.0Auto-check passedAgent Workflows

Install MCP Gateway Configuration

skills CLI

$ npx skills add Hack23/cia --skill mcp-gateway-configuration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Hack23/cia mcp-gateway-configuration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/mcp-gateway-configuration .claude/skills/mcp-gateway-configuration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "mcp-gateway-configuration" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/mcp-gateway-configuration into .claude/skills/mcp-gateway-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-gateway-configuration", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Hack23/cia/tree/master/.github/skills/mcp-gateway-configuration

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Hack23/cia --skill mcp-gateway-configuration -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Hack23/cia mcp-gateway-configuration --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/mcp-gateway-configuration .agents/skills/mcp-gateway-configuration && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "mcp-gateway-configuration" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/mcp-gateway-configuration into .agents/skills/mcp-gateway-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-gateway-configuration", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Hack23/cia --skill mcp-gateway-configuration -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Hack23/cia mcp-gateway-configuration --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/mcp-gateway-configuration .cursor/skills/mcp-gateway-configuration && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "mcp-gateway-configuration" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/mcp-gateway-configuration into .cursor/skills/mcp-gateway-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-gateway-configuration", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Hack23/cia.git --path .github/skills/mcp-gateway-configuration

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Hack23/cia --skill mcp-gateway-configuration -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Hack23/cia mcp-gateway-configuration --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/mcp-gateway-configuration .gemini/skills/mcp-gateway-configuration && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "mcp-gateway-configuration" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/mcp-gateway-configuration into .gemini/skills/mcp-gateway-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-gateway-configuration", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Hack23/cia mcp-gateway-configuration

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Hack23/cia --skill mcp-gateway-configuration -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/mcp-gateway-configuration .github/skills/mcp-gateway-configuration && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "mcp-gateway-configuration" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/mcp-gateway-configuration into .github/skills/mcp-gateway-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-gateway-configuration", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Hack23/cia --skill mcp-gateway-configuration -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Hack23/cia mcp-gateway-configuration --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/mcp-gateway-configuration .opencode/skills/mcp-gateway-configuration && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "mcp-gateway-configuration" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/mcp-gateway-configuration into .opencode/skills/mcp-gateway-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-gateway-configuration", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: mcp-gateway-configuration
GitHub stars: 239
Token cost: ~1.8k tokens
SKILL.md length: 413 words
Files: 1
Skills in repo: 78
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

MCP gateway setup for multi-server integration, security configuration, tool routing, and access control

Works in 4 steps: Least Privilege — Each server should… → Separation of Concerns — Different… → Fail-Safe Defaults — Tools should… → …
Tasks that involve MCP servers
SKILL.md covers Purpose, When to Use This Skill, MCP Architecture Overview and Configuration Structure, plus 7 more sections
Calls python3 and npx; needs GITHUB_TOKEN and MCP_TOKEN

What it does

MCP Gateway Configuration is an agent skill from Hack23/cia. MCP gateway setup for multi-server integration, security configuration, tool routing, and access control

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering MCP servers and Authorization and RBAC. It works with Model Context Protocol and GitHub. The repository describes itself as: Citizen Intelligence Agency. Open-source intelligence platform analyzing Swedish political activities using AI and data visualization. Tracks politicians, government… The licence is Apache-2.0.

When your agent uses it

Tasks that involve MCP servers
Tasks that involve Authorization and RBAC

Example prompts

“/mcp-gateway-configuration”

Requirements

Python 3
Node.js
A credential in MCP_TOKEN
A credential in GITHUB_TOKEN

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Least Privilege — Each server should only expose tools needed for its purpose
Separation of Concerns — Different servers for different capabilities
Fail-Safe Defaults — Tools should default to read-only when possible
Audit Trail — All tool invocations should be logged

What it can do on your machine

Read from SKILL.md and the folder at commit bbed538. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- python3
- npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- modelcontextprotocol.io
- docs.github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- GITHUB_TOKEN
- MCP_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

MCP Gateway Configuration loads about 1.8k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 413 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~33
When it runs · the whole SKILL.md, loaded when a task matches: ~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Hack23/cia at commit bbed538, republished under its Apache-2.0 licence (© Hack23). 413 words, ~1,833 tokens.

Download SKILL.mdSave it as .claude/skills/mcp-gateway-configuration/SKILL.md (or your agent's skills folder).

name: mcp-gateway-configuration
description: MCP gateway setup for multi-server integration, security configuration, tool routing, and access control
license: Apache-2.0

MCP Gateway Configuration Skill

Purpose

This skill provides guidance for configuring MCP (Model Context Protocol) gateways for the CIA platform. It covers multi-server integration, tool routing, security configuration, and access control to enable secure and efficient AI-assisted development workflows.

When to Use This Skill

Apply this skill when:

✅ Setting up or modifying .github/copilot-mcp-config.json
✅ Adding new MCP servers to the gateway
✅ Configuring tool routing between MCP servers
✅ Setting up access control for MCP tools
✅ Troubleshooting MCP connectivity issues
✅ Reviewing MCP configuration for security
✅ Integrating new data sources via MCP

Do NOT use for:

❌ MCP security hardening (use mcp-gateway-security)
❌ General API gateway configuration (different pattern)
❌ Application-level API design (use service layer patterns)

MCP Architecture Overview

┌─────────────────────────────────────────────┐
│              GitHub Copilot                  │
│          (AI Assistant Client)               │
└──────────────────┬──────────────────────────┘
                   │
                   ▼
┌─────────────────────────────────────────────┐
│           MCP Gateway Layer                  │
│  ┌─────────────────────────────────────┐    │
│  │   copilot-mcp-config.json           │    │
│  │   - Server definitions              │    │
│  │   - Tool routing rules              │    │
│  │   - Access control policies         │    │
│  └─────────────────────────────────────┘    │
└──────┬──────────┬──────────┬────────────────┘
       │          │          │
       ▼          ▼          ▼
┌──────────┐ ┌──────────┐ ┌──────────┐
│ GitHub   │ │ Filesystem│ │ Playwright│
│ MCP      │ │ MCP      │ │ MCP      │
│ Server   │ │ Server   │ │ Server   │
└──────────┘ └──────────┘ └──────────┘

Configuration Structure

Base Configuration (`copilot-mcp-config.json`)

json

{
  "mcpServers": {
    "server-name": {
      "type": "stdio",
      "command": "command-to-run",
      "args": ["arg1", "arg2"],
      "env": {
        "ENV_VAR": "value"
      }
    }
  }
}

Server Type Patterns

stdio Servers (Local Process):

json

{
  "filesystem": {
    "type": "stdio",
    "command": "npx",
    "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/allowed"],
    "env": {}
  }
}

SSE Servers (Remote HTTP):

json

{
  "remote-server": {
    "type": "sse",
    "url": "https://mcp-server.example.com/sse",
    "headers": {
      "Authorization": "Bearer ${MCP_TOKEN}"
    }
  }
}

CIA Platform MCP Servers

Required Servers

Server	Purpose	Tools Provided
github	Repository operations	Issues, PRs, code search, Actions
filesystem	Local file operations	Read, write, search files
playwright	Browser automation	UI testing, screenshots

Configuration Best Practices

1. Minimize Filesystem Access:

json

{
  "filesystem": {
    "type": "stdio",
    "command": "npx",
    "args": [
      "-y", "@modelcontextprotocol/server-filesystem",
      "/home/runner/work/cia/cia"
    ]
  }
}

Only expose the project root — never expose /, /home, or parent directories.

2. Use Environment Variables for Secrets:

json

{
  "github": {
    "type": "stdio",
    "command": "github-mcp-server",
    "env": {
      "GITHUB_TOKEN": "${GITHUB_TOKEN}"
    }
  }
}

Never hardcode tokens in configuration files.

3. Specify Exact Package Versions:

json

{
  "args": ["-y", "@modelcontextprotocol/server-filesystem@1.2.3"]
}

Pin versions to prevent supply chain attacks.

Tool Routing

Routing Principles

Least Privilege — Each server should only expose tools needed for its purpose
Separation of Concerns — Different servers for different capabilities
Fail-Safe Defaults — Tools should default to read-only when possible
Audit Trail — All tool invocations should be logged

Show full SKILL.md (165 more words)Show less

Tool Categories

Category	Server	Example Tools
Code Management	github	create_pull_request, push_files
Code Analysis	github	search_code, get_file_contents
File Operations	filesystem	read_file, write_file, search
UI Testing	playwright	navigate, click, screenshot
Issue Management	github	create_issue, list_issues
CI/CD	github	list_workflows, get_job_logs

Access Control Configuration

Server-Level Access Control

json

{
  "mcpServers": {
    "filesystem": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y", "@modelcontextprotocol/server-filesystem",
        "/home/runner/work/cia/cia"
      ],
      "env": {
        "ALLOWED_OPERATIONS": "read,write,search"
      }
    }
  }
}

Directory Restrictions

Allowed directories should follow the principle of least privilege:

✅ /home/runner/work/cia/cia          — Project root
✅ /home/runner/work/cia/cia/src      — Source code
✅ /home/runner/work/cia/cia/.github  — CI/CD configuration

❌ /home/runner                        — Too broad
❌ /etc                                — System configuration
❌ /tmp                                — Temporary files (security risk)

Troubleshooting

Common Issues

Issue	Symptom	Resolution
Server not starting	"Failed to connect" error	Check command path and args
Permission denied	Tool call fails	Verify filesystem paths and permissions
Token expired	Authentication errors	Refresh environment variables
Version mismatch	Unexpected tool behavior	Pin and update package versions
Timeout	Tool call hangs	Check network connectivity for SSE servers

Diagnostic Commands

bash

# Verify MCP config syntax
cat .github/copilot-mcp-config.json | python3 -m json.tool

# Check if MCP server binary is available
which github-mcp-server

# Test filesystem server
npx -y @modelcontextprotocol/server-filesystem --help

# Check environment variables
env | grep -i mcp
env | grep -i github_token

Configuration Validation Checklist

□ JSON syntax is valid
□ All server commands exist and are executable
□ Environment variables are properly referenced (not hardcoded)
□ Filesystem paths follow least privilege
□ Package versions are pinned
□ No secrets in configuration file
□ Configuration is committed to repository
□ Server definitions match documented architecture
□ Access control rules are documented

ISMS Alignment

Configuration Area	ISO 27001	NIST CSF	CIS Controls
Access Control	A.8.3	PR.AC-4	CIS 6.1
Secret Management	A.8.24	PR.DS-1	CIS 3.11
Configuration Mgmt	A.8.9	PR.IP-1	CIS 4.1
Audit Logging	A.8.15	DE.AE-3	CIS 8.2
Change Control	A.8.32	PR.IP-3	CIS 4.2

References

Files

Just SKILL.md in .github/skills/mcp-gateway-configuration of Hack23/cia.

Open the folder on GitHubat commit bbed538

Compare with similar skills

MCP Gateway Configuration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

MCP Gateway Configuration compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
MCP Gateway Configuration this skillHack23/cia	239	—	~1.8k	Automated safety check: Pass	Apache-2.0	yesterday
Project Releaseswimmwatch/cloakbrowser-mcp	161	—	~1.9k	Automated safety check: Pass	MIT	7 days ago
Project Pull Requestswimmwatch/cloakbrowser-mcp	161	—	~1k	Automated safety check: Pass	MIT	7 days ago
Deepwiki MCP Skillholon-run/uxc	116	—	~700	Automated safety check: Pass	MIT	23 days ago
Building MCP Server On CloudflareCommandCodeAI/agent-skills	132	—	~1.5k	Automated safety check: Pass	MIT	7 mo ago
Agentsbutterbase-ai/butterbase-skills	534	1 repos	~1.8k	Automated safety check: Pass	MIT	3 days ago

Similar skills

Project Release
swimmwatch/cloakbrowser-mcp
Prepare, publish, verify, or recover a cloakbrowser-mcp release only when the user explicitly requests release work.
161 GitHub stars~1.9k tokensUpdated 7 days ago
Agent WorkflowsAuto-check passed
Project Pull Request
swimmwatch/cloakbrowser-mcp
Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work.
161 GitHub stars~1k tokensUpdated 7 days ago
DevelopmentAuto-check passed
Deepwiki MCP Skill
holon-run/uxc
Ask questions and read documentation about any GitHub repository using DeepWiki MCP.
116 GitHub stars~700 tokensUpdated 23 days ago
Agent WorkflowsAuto-check passed
Building MCP Server On Cloudflare
CommandCodeAI/agent-skills
Builds remote MCP (Model Context Protocol) servers on Cloudflare Workers with tools, OAuth authentication, and production deployment.
132 GitHub stars~1.5k tokensUpdated 7 mo ago
Agent WorkflowsAuto-check passed
Agents
butterbase-ai/butterbase-skills
A skill your agent uses when designing, deploying, or debugging a Butterbase Agent (declarative LLM/tool graph), registering an MCP server for tool use, or wiring access controls and rate limits.
534 GitHub starsUsed in 1 repo~1.8k tokens
Agent WorkflowsAuto-check passed
Fastmcp Server
davila7/claude-code-templates
Complete guide for building MCP servers with FastMCP 3.0 - tools, resources, authentication, providers, middleware, and deployment.
32k GitHub stars~1.9k tokensUpdated today
Agent WorkflowsAuto-check passed

Questions about MCP Gateway Configuration

What does MCP Gateway Configuration do?

MCP gateway setup for multi-server integration, security configuration, tool routing, and access control. MCP Gateway Configuration is an agent skill from Hack23/cia.

When should I use MCP Gateway Configuration?

MCP Gateway Configuration fits situations like: tasks that involve MCP servers; tasks that involve Authorization and RBAC.

How do I install MCP Gateway Configuration in Claude Code?

Run `npx skills add Hack23/cia --skill mcp-gateway-configuration -a claude-code`. Or copy the skill folder (.github/skills/mcp-gateway-configuration in Hack23/cia) into .claude/skills/mcp-gateway-configuration in your project. Claude Code loads it when a task matches its description.

How do I install MCP Gateway Configuration in Codex?

Run `npx skills add Hack23/cia --skill mcp-gateway-configuration -a codex`. Or copy the skill folder (.github/skills/mcp-gateway-configuration in Hack23/cia) into .agents/skills/mcp-gateway-configuration in your project. Codex loads it when a task matches its description.

Can I use MCP Gateway Configuration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Hack23/cia --skill mcp-gateway-configuration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcp-gateway-configuration, .gemini/skills/mcp-gateway-configuration, .github/skills/mcp-gateway-configuration and .opencode/skills/mcp-gateway-configuration in your project.

What does MCP Gateway Configuration need to run?

Going by SKILL.md and its folder, MCP Gateway Configuration needs the command-line tools its instructions call (python3 and npx) and credentials named GITHUB_TOKEN and MCP_TOKEN. Our summary lists: Python 3; Node.js; A credential in MCP_TOKEN; A credential in GITHUB_TOKEN.

Does MCP Gateway Configuration access the network?

SKILL.md names 2 domains. As links in the text: modelcontextprotocol.io and docs.github.com. This is read from the text; nothing was executed.

Is MCP Gateway Configuration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does MCP Gateway Configuration use?

MCP Gateway Configuration is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does MCP Gateway Configuration use?

About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to MCP Gateway Configuration?

Skills that share tags, products or a category with MCP Gateway Configuration: Project Release (swimmwatch/cloakbrowser-mcp, 161 stars), Project Pull Request (swimmwatch/cloakbrowser-mcp, 161 stars), Deepwiki MCP Skill (holon-run/uxc, 116 stars) and Building MCP Server On Cloudflare (CommandCodeAI/agent-skills, 132 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains MCP Gateway Configuration?

Hack23 (a GitHub organization) maintains it in Hack23/cia, which has 239 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 7, 2026.

Source: Hack23/cia on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install MCP Gateway Configuration

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

MCP Gateway Configuration Skill

Purpose

When to Use This Skill

MCP Architecture Overview

Configuration Structure

Base Configuration (copilot-mcp-config.json)

Server Type Patterns

CIA Platform MCP Servers

Required Servers

Configuration Best Practices

Tool Routing

Routing Principles

Tool Categories

Access Control Configuration

Server-Level Access Control

Directory Restrictions

Troubleshooting

Common Issues

Diagnostic Commands

Configuration Validation Checklist

ISMS Alignment

References

Files

Compare with similar skills

Similar skills

More from Hack23/cia

Related

Questions about MCP Gateway Configuration

Base Configuration (`copilot-mcp-config.json`)