MCP Integrations

Quick Start: Sequant works fully without any MCP servers, but optional integrations enhance browser testing, library documentation lookup, and complex reasoning capabilities.

Overview

MCP (Model Context Protocol) servers extend Claude’s capabilities with specialized tools. Sequant supports three optional MCP integrations that enhance specific workflows.

Supported MCPs

MCP Server	Skills Enhanced	Purpose
Chrome DevTools	`/test`, `/testgen`, `/loop`	Browser automation for UI testing
Context7	`/exec`, `/fullsolve`	External library documentation lookup
Sequential Thinking	`/fullsolve`	Complex multi-step reasoning

Checking MCP Status

Run the doctor command to see which MCPs are configured:

npx sequant doctor

Example output:

✓ MCP Servers: Some MCPs configured: sequential-thinking
⚠ MCP: chrome-devtools: Not configured (optional, enhances /test, /testgen, /loop)
⚠ MCP: context7: Not configured (optional, enhances /exec, /fullsolve)

Installation

Chrome DevTools MCP

Enables automated browser testing with snapshots, screenshots, and interaction recording.

Follow the setup guide
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS)
Restart Claude Desktop

Without this MCP: The /test skill falls back to generating manual test checklists instead of automated browser tests.

Context7 MCP

Provides up-to-date library documentation during implementation.

npx -y @anthropic/mcp-cli add upstash/context7

Without this MCP: The /exec skill uses codebase search and general knowledge instead of fetching current library docs.

Sequential Thinking MCP

Enables extended reasoning for complex multi-step problems.

Follow the setup guide
Add to your Claude Desktop config
Restart Claude Desktop

Without this MCP: The /fullsolve skill uses standard reasoning without extended thinking chains.

Behavior Without MCPs

Sequant is designed to work without any MCPs. Here’s what changes:

Scenario	With MCP	Without MCP
`/test` command	Automated browser snapshots and interactions	Manual test checklist generated
`/exec` library lookup	Fetches current docs from Context7	Uses codebase patterns and general knowledge
`/fullsolve` reasoning	Extended thinking for complex problems	Standard reasoning approach

Troubleshooting

MCP not detected by doctor command

Symptoms: You installed an MCP but sequant doctor still shows it as not configured.

Solution:

Verify the MCP is in your Claude Desktop config file
Check the server name matches expected patterns (e.g., contains “chrome-devtools”, “context7”, or “sequential-thinking”)
Restart Claude Desktop after config changes

Skills fail with MCP errors

Symptoms: Error messages about missing MCP tools when running skills.

Solution:

Run sequant doctor to check MCP status
If MCP is optional for your use case, the skill should fall back gracefully
If you need MCP functionality, install following the guides above

Claude Desktop config location

Platform	Config Path
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json`
Linux	`~/.config/claude/claude_desktop_config.json`

Generated for Issue #15 on 2025-01-10