stored in its own SQLite database at `~/.meridian/meridian.db`. A Next.js dashboard and a TypeScript MCPserver sit alongside the daemon. (Capture source: historically screenpipe's SQLite DB; since the Bucket
Load Guides from `packages/ /` (e.g. `packages/malta/`, `packages/us-ca/`) — each file is self-contained markdown.
- Hosted MCPserver for live, accountant-reviewed data: https://www.openaccountants.com/api/mcp
- The website with the Tax Library
Claude Code (claude.ai/code) when working with code in this repository.
## Project Overview
MCPserver exposing Korea's MOLIT (국토교통부) real estate transaction API to Claude Desktop. The server wraps
Hook scripts (`ai-sdlc-plugin/hooks/*.js`) use Node built-in `node --test`. Orchestrator + MCPserver use Vitest.
- `@ai-sdlc/dogfood` tests (`dogfood/src/runner/exports.test.ts`) import from `dist/runner/index.js` to validate the built
CLAUDE.md
tfmcp is a Rust-based MCPserver for Terraform operations using the RMCP SDK.
## Quick Reference
```bash
# Quality checks (run before commits)
cargo fmt --all && RUSTFLAGS="-Dwarnings" cargo clippy
missing parentheses are.
- Only the generated `ResourceTest` suites under `test/anthropic/resources/**` need the mock server (port 4010, or `TEST_API_BASE_URL`); `APIConnectionError`s there mean the mock isn't running
every contributor gets the same rulebook.
## Repo at a glance
- **TS server** (`src/`) - the MCPserver. Wraps the UE bridge over WebSocket, exposes 26 category tools with 1966+ actions
checker**: `ty` is configured for static type checking
```bash
uv run ty check -- nextcloud_mcp_server
```
### Code Quality
- **Before committing or pushing, invoke the `pre-push-review` skill**:
- Runs `ruff
Claude Code. It contains 5 plugins that provide AWS development expertise through skills and MCPserver integrations.
## Architecture
```
.claude-plugin/marketplace.json # Plugin marketplace definition (versions, MCPservers)
plugins/
├── aws-common
input frame: `[status_line] segments = [...]` in `cli.toml` picks and orders `model`, `server`, `cwd`, `git`, `context`, `tokens`, `scratchpad`, `mcp` (all shown by default). Rendered locally from `ui::status_line` — no extra
taskdog-ui**: CLI (Click + Rich) and TUI (Textual), depends on core + client.
- **taskdog-mcp**: MCPserver for Claude Desktop (depends on client).
**Communication**: CLI/TUI/MCP reach all data through the HTTP
what to type.
## Changing the connectors
The top bar shows the MCPservers **this machine's Claude Code** is connected to (`claude mcp list`). To add one: `claude mcp
else, when you see ANY task management scenario:
1. STOP and check if Archon MCPserver is available
2. Use Archon task management as PRIMARY system
3. Refrain from using
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.