@4da/mcp-server
# @4da/mcp-server has moved
The 4DA MCP server now lives in its own repository, with its full history:
**https://github.com/4DA-Systems/4da-mcp-server**
Install it as before; the package name is unchanged:
```bash
claude mcp add 4da -- npx @4da/mcp-server
```
As a Claude Code plugin:
```bash
claude plugin marketplace add 4DA-Systems/4da-mcp-server
claude plugin install 4da@4da
```
This folder stays only so that older links keep resolving. Issues, releases
and contributions go to the new repository.
The server reads this app's database. The schema it relies on is published
from here as [`src-tauri/contract/app-schema.sql`](../src-tauri/contract/app-schema.sql),
generated from the migrations; CI checks every app schema change against the
server's queries before it merges.
TDQS
Scored across 9 tools
Some tools are clearly distinct (vulnerability_scan vs dependency_health vs upgrade_planner), but get_context, what_should_i_know, and agent_memory all deal with context/memory and could cause misselection. check_decision_alignment overlaps with decision_memory's 'check' functionality.
Tool names follow a consistent snake_case pattern, mixing noun_verb and verb_noun forms (vulnerability_scan, dependency_health, upgrade_planner) with a few verb-first names (get_context, check_decision_alignment). The style is consistent, but verb placement varies slightly.
9 tools is appropriate for a developer-assistant server covering security, dependency, and memory features. Each tool seems purposeful and the count is within the ideal 3-15 range.
The security/dependency workflow is well covered (scan, health, plan), and memory tools cover both recording and recalling. Missing actions like clearing memory or comparing dependency versions are minor gaps that agents could work around.