setup

Configure Synapse MCP access for Claude Code via environment variables and .mcp.json.

29|3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/Vincentwei1021/Synapse --skill setup-vincentwei1021
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/Vincentwei1021/Synapse/tree/main/public/synapse-plugin/skills/setup
Command: npx skills add https://github.com/Vincentwei1021/Synapse --skill setup-vincentwei1021

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Synapse connections inside Claude Code often fail or are misconfigured due to missing API keys, incorrect MCP URLs, or project-level configuration not being applied consistently.

Core Features & Use Cases

  • Synapse API key setup: create or verify the correct key and ensure it uses the expected format.
  • MCP configuration via env + .mcp.json: wire Claude Code to Synapse using SYNAPSE_URL and SYNAPSE_API_KEY, leveraging the plugin-bundled .mcp.json with placeholder substitution.
  • Connection verification: confirm tool/role visibility by calling synapse_checkin() and validating required roles (e.g., pre_research, research, experiment, report, admin/pi_agent).

Quick Start

Ask the AI to set SYNAPSE_URL and SYNAPSE_API_KEY in your Claude Code settings, restart Claude Code, and then run synapse_checkin() to verify the MCP connection and required tools are visible.

Frequently Asked Questions about setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure the Synapse MCP connection in Claude Code?

To configure the Synapse MCP connection in Claude Code, set the required environment variables `SYNAPSE_URL` and `SYNAPSE_API_KEY`, leverage the project-level `.mcp.json` for placeholder substitution, and restart Claude Code to apply the configuration.

Why does the Synapse MCP connection fail even when the plugin is installed?

The Synapse MCP connection fails due to missing API keys, incorrect server URLs, or project-level `.mcp.json` configuration not being applied consistently. You must ensure correct placeholder substitution and environment variable precedence.

How do I verify if my Claude Code agent has the required Synapse MCP roles?

Verify Synapse MCP roles by calling the `synapse_checkin()` function in Claude Code. This validates connectivity and confirms that required tools and roles like `pre_research`, `research`, `experiment`, and `admin` are visible.

What is the correct format for a Synapse API key in Claude Code?

The Synapse API key must be created or verified to ensure it uses the expected format, then assigned to the `SYNAPSE_API_KEY` environment variable. The plugin-bundled `.mcp.json` relies on this placeholder substitution to connect successfully.

Does project-level .mcp.json configuration take precedence over environment variables?

Project-level `.mcp.json` configuration applies placeholder substitution using the `SYNAPSE_URL` and `SYNAPSE_API_KEY` environment variables. You must ensure this configuration is applied consistently across your local setup to enable proper MCP server connections.