caee558e79
Add /ultraresearch-local for structured research combining local codebase analysis with external knowledge via parallel agent swarms. Produces research briefs with triangulation, confidence ratings, and source quality assessment. New command: /ultraresearch-local with modes --quick, --local, --external, --fg. New agents: research-orchestrator (opus), docs-researcher, community-researcher, security-researcher, contrarian-researcher, gemini-bridge (all sonnet). New template: research-brief-template.md. Integration: --research flag in /ultraplan-local accepts pre-built research briefs (up to 3), enriches the interview and exploration phases. Planning orchestrator cross-references brief findings during synthesis. Design principle: Context Engineering — right information to right agent at right time. Research briefs are structured artifacts in the pipeline: ultraresearch → brief → ultraplan --research → plan → ultraexecute. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
137 lines
2.3 KiB
Markdown
137 lines
2.3 KiB
Markdown
# MCP Server Configuration Reference
|
|
|
|
## File Locations
|
|
|
|
| Location | Scope |
|
|
|----------|-------|
|
|
| `~/.claude.json` → mcpServers | Global (all projects) |
|
|
| `.mcp.json` | Project-specific |
|
|
| `.claude/settings.json` → mcpServers | Project-specific |
|
|
|
|
## Basic Structure
|
|
|
|
```json
|
|
{
|
|
"mcpServers": {
|
|
"server-name": {
|
|
"command": "executable",
|
|
"args": ["arg1", "arg2"],
|
|
"env": {
|
|
"KEY": "value"
|
|
}
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
## Server Types
|
|
|
|
### stdio (Standard I/O)
|
|
|
|
Most common type, runs as subprocess:
|
|
|
|
```json
|
|
{
|
|
"mcpServers": {
|
|
"filesystem": {
|
|
"command": "npx",
|
|
"args": ["-y", "@anthropic/mcp-server-filesystem", "/path/to/root"],
|
|
"env": {}
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
### SSE (Server-Sent Events)
|
|
|
|
Connect to remote HTTP server:
|
|
|
|
```json
|
|
{
|
|
"mcpServers": {
|
|
"remote-service": {
|
|
"url": "https://api.example.com/mcp",
|
|
"headers": {
|
|
"Authorization": "Bearer ${API_TOKEN}"
|
|
}
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
## Common Patterns
|
|
|
|
### Filesystem Server
|
|
|
|
```json
|
|
{
|
|
"filesystem": {
|
|
"command": "npx",
|
|
"args": ["-y", "@anthropic/mcp-server-filesystem", "."],
|
|
"env": {}
|
|
}
|
|
}
|
|
```
|
|
|
|
### Database Server
|
|
|
|
```json
|
|
{
|
|
"database": {
|
|
"command": "npx",
|
|
"args": ["-y", "@anthropic/mcp-server-postgres"],
|
|
"env": {
|
|
"DATABASE_URL": "${DATABASE_URL}"
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
### Slack Server
|
|
|
|
```json
|
|
{
|
|
"slack": {
|
|
"command": "npx",
|
|
"args": ["-y", "@anthropic/mcp-server-slack"],
|
|
"env": {
|
|
"SLACK_BOT_TOKEN": "${SLACK_BOT_TOKEN}",
|
|
"SLACK_TEAM_ID": "${SLACK_TEAM_ID}"
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
## Environment Variables
|
|
|
|
**Best practice**: Use `${VAR_NAME}` syntax instead of hardcoded values:
|
|
|
|
```json
|
|
{
|
|
"env": {
|
|
"API_KEY": "${MY_API_KEY}" // Good
|
|
// "API_KEY": "sk-abc123..." // Bad - exposed secret
|
|
}
|
|
}
|
|
```
|
|
|
|
## Security Considerations
|
|
|
|
1. **Never hardcode secrets** in .mcp.json
|
|
2. **Use environment variable references** (`${VAR}`)
|
|
3. **.mcp.json should be gitignored** if it contains any sensitive paths
|
|
4. **Check for secrets** before committing
|
|
|
|
## Global vs Project
|
|
|
|
### When to use global (~/.claude.json)
|
|
|
|
- Servers used across all projects
|
|
- Personal tools (Slack, email)
|
|
- Utility servers (filesystem with safe root)
|
|
|
|
### When to use project (.mcp.json)
|
|
|
|
- Project-specific databases
|
|
- Project APIs
|
|
- Specialized tools for this codebase
|