Pending: Which MCP servers provide the most value for Opus workflows?
Pending: Local-only servers or also remote/cloud-hosted?
Pending: Auth strategy for servers that need API keys
User Tasks
FR-014: MCP Server Configuration
Summary
Configure MCP servers in .mcp.json to extend Claude Code’s capabilities with web search, filesystem tools, databases, and external APIs.
Problem / Motivation
.mcp.json exists in the project structure but has no servers configured. MCP (Model Context Protocol) servers are the primary way to give Claude Code access to external tools beyond its built-in set. Without MCP servers, skills and agents are limited to shell commands and file operations. Many planned features (briefings, monitoring, research, notifications) would benefit from structured access to web search, HTTP APIs, or a local database.
Proposed Solution
Curate and configure a set of MCP servers that support Opus workflows. Start with high-value, low-risk servers and expand.
Candidate Servers
Server
Capability
Use Cases
filesystem
Structured file operations
Safer than raw bash for file management
fetch / web
HTTP requests, web page fetching
Research, API calls, web scraping
sqlite
Local SQLite database
Job registry, task scheduler, metrics
memory
Persistent key-value store
Cross-session state beyond vault files
github
GitHub API
PR management, issue tracking (FR-023)
Open Questions
1. Server Selection Priority
Question: Which servers to enable first?
Option
Description
A) sqlite + fetch
Enables database-backed features (scheduler, job queue) and web access
B) filesystem + memory
Safer file ops and persistent state
C) All at once
Maximum capability immediately
Recommendation: Option A — sqlite unlocks FR-048/FR-048 (scheduler, job queue), fetch unlocks research and monitoring features.
Phase Overview
Phase
Description
Status
Phase 1
Core servers (sqlite, fetch)
—
Phase 2
GitHub + additional servers
—
Phase 3
Custom MCP server for Opus-specific tools
—
Phase 1: Core Servers —
Goal: Enable sqlite and fetch MCP servers with proper configuration.
File / Feature
Details
Owner
Status
.mcp.json
Configure sqlite + fetch servers
opus
—
SQLite DB setup
Create data/opus.db with initial schema
opus
—
Verify access
Test both servers work from Claude Code
mv
—
Documentation
Document available MCP tools in vault
opus
—
Phase 2: GitHub + Extras —
Goal: Add GitHub and other useful servers.
File / Feature
Details
Owner
Status
GitHub MCP server
Configure with token from .env
opus
—
Additional servers
Evaluate memory, filesystem as needed
mv
—
Test
Manual tests
Test
Expected
Owner
Actual
Last
Query SQLite from Claude Code
Returns data
mv
pending
-
Fetch a web page via MCP
Returns page content
mv
pending
-
List GitHub repos
Returns repo list
mv
pending
-
AI-verified tests
Scenario
Expected behavior
Verification method
…
…
…
E2E tests
Scenario
Assertion
…
…
Integration tests
Component
Coverage
…
…
Unit tests
Component
Tests
Coverage
…
…
…
History
Date
Event
Details
2026-03-12
Created
Identified as gap — .mcp.json exists but unconfigured
References
FR-048 (Task Scheduler) — would use sqlite MCP for persistence
FR-048 (Job Registry) — would use sqlite MCP for job queue
FR-023 (GitHub Integration) — would use github MCP server